Anith Gopal

Everybody is talking about clouds these days but really the choice to move to the cloud is not an all-or-nothing proposition. With different types of cloud offerings, you have flexible options about which services to obtain in the cloud and which to keep on site.

1: using (SPSite site = new SPSite( "http://ms10:200/sites/200" )) 2: { 3: using (SPWeb web = site.OpenWeb()) 4: { 5: SPList lib1 = (SPDocumentLibrary)web.Lists[ "Documents" ]; 6: SPList lib2 = (SPDocumentLibrary)web.Lists[ "Site Collection Documents" ]; 7: byte [] fileBytes = null ; 8: string destUrl = null ; 9: SPFile destFile = null ; 10: foreach (SPListItem item1 in lib1.Items) 11: { 12: fileBytes = item1.File.OpenBinary(); 13: destUrl = lib2.RootFolder.Url + "/" + item1.File.Name; 14: destFile = lib2.RootFolder.Files.Add(destUrl, fileBytes, true /*overwrite*/ ); 15:   16: fileBytes = null ; 17: destUrl = null ; 18: destFile = null ; 19: } 20:   21: lib1 = null ; 22: lib2 = null ; 23: } 24: } 25: MessageBox.Show( "Done!" );

The requirement to write this code was, After export/import, workflow modification for approvers was failing. Approvers were not able to perform the Approval workflow operations and then we tested that if we create a new Tasks list and modify the existing Approval workflow association then everything starts working so we needed a code which can do this operation for whole site collection. Following code snippet will create a Tasks list with name “MS Tasks” and associate it with a Parallel Approval workflow in a “Pages” library in root site as well as in all the sub sites.

It’s a new beginning to writing my thoughts/ideas on MSDN Blog. Wish this will help you.

After a long journey, the work I did along with others has finally paid off.   The VS2010 Guidance is now available on codeplex.  I worked on the developer (database) portions.  I hope everyone enjoys the hard work. Reference: http://vs2010quickref.codeplex.com/

Capacite-se com os novos materiais do Innovation Lab Download! Novos temas estão disponíveis para download através do Innovation Lab. Aproveite para instalar a aplicação e ter acesso aos documentos e vídeos, clicando aqui , ou acesse a página do Download Center e baixe os documentos diretamente. Não deixe de aproveitar o material especial de Compatibilidade com o Windows 7 e já fique preparado para o Dev Excellence Award que será lançado no começo de 2010.

Here’s the source to the BrowserFlow sample I showed at PDC 2009 .  This sample requires the Silverlight 4 Beta which you can find here .   The sample uses the combination of the WebBrowser Control and HTMLBrush to display an interactive Ad that also plays well with the Silverlight animation system.  Click the image below to run the sample (note that it needs to be installed to run).         The demo shows the following new Silverlight 4 features:   ·          WebBrowser Control ·          HTMLBrush  

The ‘F’ in F# stands for fun . However, there are some details in F# that might lead to bugs, surprises, and/or un-fun. This post is to highlight a couple of random ‘gotchas’ when exploring some corners of the F# language.

Tim Heuer and Scott Barnes have established a more community focused way of tracking Silverlight 4 feature requests.  You can find their feature tracker here: Silverlight Feedback Forum .   Other than a few items that our outside our control (iPhone, bundling), you’re likely to see at least a few of the top items in the next version of Silverlight.

I am sitting in the VMworld session “TA3880 – Head-To-Head Comparison: VMware vSphere and ESX vs. Hyper-V and XenServer”.  It is interesting to listen to VMware’s perspective on this. One point that they have raised – which I have heard before – is that VMware ESX has better scalability than Hyper-V because they run their drivers in the hypervisor, while we run our drivers in the parent partition.  VMware usually then continues to say that they tried this approach (drivers in the parent partition, or the “service console” to use VMware nomenclature) with older versions of ESX and it caused scalability issues that were resolved by moving the drivers and emulated devices into the hypervisor

Since working on a clinical outcomes review system a couple of years ago, I’ve been aware of the gap between simple hand-coded workflows and the full-blown workflow tools. Stateless embodies the idea that a state machine can use closures to implement workflow without taking on persistence responsibilities

You can grab it from here: http://www.microsoft.com/downloads/details.aspx?familyid=48359dd2-1c3d-4506-ae0a-232d0314ccf6 To recap, the new features of this release are: Support for physical computers with up to 8 physical processors Support for using up to 1TB of physical memory (virtual machines can use up to 64GB each) Support for clustering Support for live migration Support for CPU Core Parking Core Parking allows Windows and Hyper-V to consolidate processing onto the fewest number of possible processor cores, and suspends inactive processor cores. Support for Second Level Address Translation (SLAT) in CPUs On Intel processors this is called “ EPT ” while AMD calls it “ NPT ”