Sharepoint 2010 – How to deploy custom Webparts
February 5th, 2010
I have found many post in the web about how easy is to develop and debug custom Visual Webpart, here are a couple of great references
- http://blogs.msdn.com/bethmassi/archive/2010/01/28/creating-a-sharepoint-visual-web-part-using-visual-studio-2010.aspx
- http://www.helloitsliam.com/archive/2009/10/20/sharepoint-2010-–-create-a-visual-web-part.aspx
- http://blogs.pointbridge.com/Blogs/nielsen_travis/Pages/Post.aspx?_ID=32
The problem is that there is not much talking about how to deploy the packaged Webpart on a different server. I run into this issue following the last post mentioned above because I am trying to deploy a custom Webpart to analyze the Claims inside a Token in a Claims based Authentication Sharepoint Web Application.
I finally came across this post (http://dotnet.sys-con.com/node/1208275) which details the deployment process as follows and is a recommended reading BWT. I am considering that you have a .WSP Webpart packaged by Visual Studio 2010 Beta.
- Add-SPSolution c:\code\SharePointProject2\bin\debug\SharePointProject2.wsp
- Install-SPSolution –Identity SharePointProject2.wsp –WebApplication http://sp2010 -GACDeployment
I will complement that post adding the final steps you should run to actually be able to see that webpart on your web application!
When adding a web part while editing a sharepoint page you might find that not all available webparts are show. This might happen if your Site Collection has not enabled all features and is also necessary for activating custom webparts. You should do the following as a Site Collection administrator,
- Site Actions
- Site Settings
- Manage Site Features
- Site Collection Features
Hope this helps!
Leave a Reply