In Focus

SharePoint Deployment Process In Dev Environment

In this article I will try to explain the SharePoint deployment process in develoment environment.

Document Information

Use the following procedure to deploy your project in the develoment environment.

  1. Pull the Code from TFS.
  2. Open the project. After opening the solution file you may get an error as in the following.

ERROR: The Site URL property of the project does not contain a valid URL.

To fix this error In Solution Explorer click on the SharePoint project and press the F4 key.

Figure 1: SharePoint

You will get a properties window as in the following on right side. Set the Site URL of your project like:


Figure 2: SiteURL

To deploy the SharePoint project, In the Solution Explorer right-click on the SharePoint UI project and select Deploy as as in the following.

Figure 3: SharePoint project

When you are deploying the project you may get various types of errors as in the following

  • A deployment or retraction is already under way for the solution and only one deployment or retraction at a time is supported.

Issue: when we are deploying the solutions in SharePoint, sometimes we encounter the issue that the solution will not be deployed and the error would be ”A deployment or retraction is already under way for the solution and only one deployment or retraction at a time is supported”.

Cause: After analysis I was able to understand that, the reason behind the issue is the timer job is created for the deployment but not running, you will be unable to redeploy or retract the solution due to that.

Solution: please use the following procedure to resolve the issue.

  • Go to Central Admin -> System Settings -> Manage Farm Solutions.
  • Cancel the deployment for your present solution. It may show the status failed or deploying, which means deployment is not successful.
  • Now again try to redeploy the solution.

Admin SVC must be running to create deployment timer job.

So I found the solution for this.

Use the following procedure to resolve this error:

Go to "Control Panel -> Administrative tools -> Services", select SharePoint 2010 Administration and start it. Check the figure below.

Figure 4: Service

After this you able to add solution in your SharePoint successfully.

Error occurred in deployment step Add Solution': A timeout has occurred when invoking commands in the SharePoint host process.


Error occurred in deployment step 'Activate Features': A timeout has occurred when invoking commands in SharePoint host process.

This issue occurs due to hardware support. We don't know the exact solution for this but the workaround is manual deployment using a shell script.

  1. if(!(Get-PSSnapin Microsoft.SharePoint.PowerShell -ea 0))  
  2. {  
  3. Add-PSSnapin Microsoft.SharePoint.PowerShell  
  4. }  
  7. $varSiteUrl = ""  
  9. write-host "`nupdating wsp" -foregroundcolor Green   
  10. Update-SPSolution –Identity "WKH.MR.OvidMD.wsp" –LiteralPath "C:\Narasimha\Projects\Code   
  11. \Trunk\SharePointUI\Source\SharePointUI\bin\Debug\CNR.XXXYY.wsp" –GACDeployment  
  12. write-host "`nupdated wsp" -foregroundcolor Green  
  14. #Disable-SPFeature –Identity "SharePointUI_BinaryContentList" –url $varSiteUrl -Force  
  15. #Disable-SPFeature –Identity "SharePointUI_Calculators" –url $varSiteUrl -Force  
  16. #Disable-SPFeature –Identity "SharePointUI_ContentUniverseConfiguration" –url $varSiteUrl -   
  17. Force  
  18. #Disable-SPFeature –Identity "SharePointUI_JavaScriptContentFeature" –url $varSiteUrl -Force  
  19. #Disable-SPFeature –Identity "SharePointUI_Navigational Refiners" –url $varSiteUrl -Force  
  20. #Disable-SPFeature –Identity "SharePointUI_Navigational Refiners Schema" Schema –url   
  21. $varSiteUrl -Force  
  22. #Disable-SPFeature –Identity "SharePointUI_NonAuthenticateduserConfiguration" –url   
  23. $varSiteUrl -Force  
  24. #Disable-SPFeature –Identity "SharePointUI_PageTopics" –url $varSiteUrl -Force  
  25. #Disable-SPFeature –Identity "SharePointUI_Core" –url $varSiteUrl -Force  
  26. #Disable-SPFeature –Identity "SharePointUI_Core Schema" –url $varSiteUrl -Force  
  28. Enable-SPFeature –Identity "SharePointUI_Core Schema" –url $varSiteUrl -Force  
  29. Enable-SPFeature –Identity "SharePointUI_Core" –url $varSiteUrl -Force  
  30. Enable-SPFeature –Identity "SharePointUI_Navigational Refiners Schema" Schema –url   
  31. $varSiteUrl -Force  
  32. Enable-SPFeature –Identity "SharePointUI_Navigational Refiners" –url $varSiteUrl -Force  
  33. Enable-SPFeature –Identity "SharePointUI_BinaryContentList" –url $varSiteUrl -Force  
  34. Enable-SPFeature –Identity "SharePointUI_Calculators" –url $varSiteUrl -Force  
  35. Enable-SPFeature –Identity "SharePointUI_ContentUniverseConfiguration" –url $varSiteUrl -   
  36. Force  
  37. Enable-SPFeature –Identity "SharePointUI_JavaScriptContentFeature" –url $varSiteUrl -Force  
  38. Enable-SPFeature –Identity "SharePointUI_NonAuthenticateduserConfiguration" –url $varSiteUrl   
  39. -Force  
  40. Enable-SPFeature –Identity "SharePointUI_PageTopics" –url $varSiteUrl -Force
Copy the script and paste it into the SharePoint 2010 Management Shell and set the .wsp path and run the script and wait until it completes.

Figure 5: Management Shell

Check Project and App pools of your site in IIS

Now you can run the application in a browser with the URL

Another Way to Deployg the project

Each time we may not use the preceding procedure, each time we may get the time out errors. So the best practice is.

When you make any changes in the businees logic (.aspx.cs or .ascx.cs) of SharePoint UI project, there is no need to deploy the entire project. The following procedure must be followed.
  • Placing the SharePoint UI DLL into a shared assembly
    Build the SharePoint UI project and open the Visual Studio command prompt in administrative mode. Enter the command as in the following:
    gacutil /i path (path of SharepointUI.dll)

When you make any changes in the UI design (.aspx or .ascx) of the SharePoint UI project, place those changes directly into IIS.

When you make any changes in the dependency projects like Search, Common and and so on.

Figure 6: Search and Command

Build the specific project and directly copy the DLL and place it in IIS. Use the following procedure. For example I made some changes in the Search project.

Build the project and right-click on that project and select Open Folder in Windows Explorer.

Figure 7: Open Folder

Copy the Searh.dll from the bin folder.

Figure 8: Bin Folder

Place the Search.dll directly into the xxxyyy site in IIS. Expand the xxxyy site the select the bin folder and explore it.

Figure 9: Search.dll

Then replace the Search.dll and Search.pdb.