Developing SharePoint applications that use browser-enabled InfoPath forms requires a lot of interactions with the Web Services and it's usually done via DataSources properties of the InfoPath. You store all your connections to the Web Service into the DataSources and uses properties name to communicate. The tricky situation of DataSources is in deployment. When you compile and publish InfoPath form it includes the connection settings that you configured locally, and the InfoPath form wont wor...

As you know SharePoint 2010 provides you "sandboxed solutions" to run your code in the restricted environment (for testing or other purposes) that doesn't affect the production farm functionality. Such functionality is achieved that your solution is compiled against the subset of Microsoft.SharePoint namespace, and Visual Studio will trim intellisense of available method. However the compilation happening against the full Microsoft.SharePoint.dll The recommendation for the c...

Question: >> How can I convert List Template to a Feature Answer: The way to achieve this to use use Visual Studio Extentions for WSS to extract List Resources and then deploy them either via VSeWSS or via STSDEV Guideline http://dotnetdeveloper.co.uk/blogs/sharepoint/archive/2009/02/18/deploying-custom-lists-with-stsdev.aspx Tool http://www.microsoft.com/downloads/details.aspx?familyid=FB9D4B85-DA2A-432E-91FB-D505199C49F6&displaylang=en#filelist  

Question: >> How can I deploy SPD Workflow from Dev to prod Answer: Unfortunatelly, SharePoint designer workflows are not portable by default. There are several OOB activities that come with SharePoint itself that are used by SharePoint Designer Workflow. These activities when serialized to XOML (the temporary file is generated by SPD when you create new WorkFlow), store GUIDS to lists itself instead of ‘pointers’ to list, or any other indirection or that matter. And here is th...

Be careful when you try to import sub-site to be your root site, especially when you have publishing sites. STSADM import/export doesn't work doesn’t work too well when you export a sub-site and import it to the top level site in a site collection. When you get you resulted root site you Template Settings page (Site Settings-> Page Layout), and Site Setting -> Create Page are corrupted. Data at the root level is invalid. Line 1, position 1. at System.Xml.XmlTextReaderImpl.Throw(Exce...

Sometimes you have a already created site but wanted to know the site definition of that site, or gets the name of the site definition from which the site template that was used to create the site is derived. There are several steps to get that template First method Navigate to the “Central Administration –> Application Management –> Site Collection List” and choose the site you are trying to find the template for Write down site "Title” and “Database name” values ...

SharePoint provides you two approaches to design and deploy WorkFlows - via SharePoint Designer(SPD) and using Visual Studio. But you should be aware that deployment of WorkFlows has some differences in the security model that might cause you permissions issues. SharePoint has its own security model to resolve the user's windows identity for all activities. It uses either IIS application pool user or the WSS Timer user for scheduled tasks. Such behavior is the same for both Visual Studio and ...