SharePoint By Gaurav Goyal

Back in SharePoint 2007, asmx web services were quite prevalent, thanks to the WSPBuilder tool, and it’s templates.   They are useful for executing actions between multiple web applications and can be used by client applications, as well.  Furthermore, InfoPath forms, deployed to SharePoint, could also use these asmx web services. Unfortunately, Visual Studio 2010 did not come with a template for SharePoint web services.  So, today I will be writing about how we can create asmx web services for SharePoint 2010.  All you will need is SharePoint 2010. First, start a new Empty SharePoint 2010 project.  I will call this SPASMXService . Make sure to deploy it as a farm solution. First, you need to close this project by right clicking on the project and then selecting ‘unload project’. Then, right click on the project again, and select, ‘Edit SPASMXService’. Under < SandboxedSolution > False </ SandboxedSolution > type in: < TokenReplacementFi...

We sometimes get this error when deploying SharePoint 2010 solutions from Visual Studio 2010: Error occurred in deployment step ‘Retract Solution’: The language-neutral solution package was not found. To resolve this error user Powershell : Run Powershell. Ensure you have Sharepoint Powershell commands enabled For that run following command Add-PSSnapin Microsoft.SharePoint.Powershell   run following command (Replace mysolution.wsp with your solution name) (get-spsolution mysolution.wsp).Delete()

Download Approval Workflow Source Code and Example. I have developed an Approval Workflow that can be deployed on SharePoint 2010 and can be associated to any list or library; it has been developed using Visual Studio 2010. This workflow creates approval tasks for the person who is responsible for the approval, you might think this similar to a usual SharePoint approval workflow, so here we are, to add the touch of spice to this solution, I want to throw some light on the task form, here I am using an InfoPath form when you go and edit this task. This opens up a hell lot of options to play with as InfoPath form is completely customizable. So you can modify the solution and the form as per your needs and requirements very easily. Open property window of State Machine Workflow & add the following values to the properties : Receiver Assembly  = Microsoft.Office.Workflow.Feature, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c Receiver Class ...