Dahlsim
asked on
How to Update a Custom Webpart using WSPBuilder and Visual Studio 2008
I have a Custom Webpart I've deployed to a Sharepoint server using Visual Studio 2008 and the WSPBuilder Visual Studio Add-in. After deploying the webpart I've added to a custom sharepoint application page and all is fine.
The Webpart is deployed as a FEATURE on the Sharepoint Server but now I'm not clear on how the UPDATE process is supposed to proceed as I modify and update the Webpart.
I tried the WSPBuilder "Upgrade" submenu but that produces an error as in the attached code snippet.
So if "Upgrade" is not the way to "Update" a custom webpart that has already been deployed then what is the correct way to do this? Do I have to Uninstall and Reinstall the custom webpart everytime in Sharepoint or is there another way?
If so then what happens to the page that has the custom webpart? Do you have to remove the old version of the webpart and re-install it?
I've done quite a bit of reading but it seems everyone covers the first time installation and there is litlte about updating the custom Sharepoint webpart.
The Webpart is deployed as a FEATURE on the Sharepoint Server but now I'm not clear on how the UPDATE process is supposed to proceed as I modify and update the Webpart.
I tried the WSPBuilder "Upgrade" submenu but that produces an error as in the attached code snippet.
So if "Upgrade" is not the way to "Update" a custom webpart that has already been deployed then what is the correct way to do this? Do I have to Uninstall and Reinstall the custom webpart everytime in Sharepoint or is there another way?
If so then what happens to the page that has the custom webpart? Do you have to remove the old version of the webpart and re-install it?
I've done quite a bit of reading but it seems everyone covers the first time installation and there is litlte about updating the custom Sharepoint webpart.
WSPBuilder
Version: 0.9.8.1029
Created by Carsten Keutmann
GPL License 2007
Building the solution - please wait
More than one LincolnUserInfo.dll assembly found!
First found C:\Morris\DotNetProjects\LincolnUserInfo\LincolnUserInfo\bin\Debug\LincolnUserInfo.dll
Second found C:\Morris\DotNetProjects\LincolnUserInfo\LincolnUserInfo\bin\Debug\solution\LincolnUserInfo.dll
Saving the Manifest.xml file
Creating the WSP file
Cleanup
Install and deploying LincolnUserInfo.wsp
Unable to deploy solution
Inner exception(1): An object of the type Microsoft.SharePoint.Administration.SPSolution named "lincolnuserinfo.wsp" already exists under the parent Microsoft.SharePoint.Administration.SPFarm named "LPCDev_SP_Config". Rename your object or delete the existing object.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm looking for a little more direction on the what the process is for UPDATING an Existing Custom Webpart as well as documentation on WSPBuilder Visual Studio Addin (Visual Studio 2008). I've followed links that all seem to come up short of being actual documentation.
Is there a Sharepoint expert that could shed a little more light on the process of UPDATING an already deployed Sharepoint Custom WebPart using WSBuilder and perhaps when the menu commands like "UPGRADE" should be used?
If there is a link to clear documentation specifically on the WSPBuilder Visual Studio Plugin that would explain the general purpose and usage of the menu items that would also be nice since all my searches so far don't lead me to such
Is there a Sharepoint expert that could shed a little more light on the process of UPDATING an already deployed Sharepoint Custom WebPart using WSBuilder and perhaps when the menu commands like "UPGRADE" should be used?
If there is a link to clear documentation specifically on the WSPBuilder Visual Studio Plugin that would explain the general purpose and usage of the menu items that would also be nice since all my searches so far don't lead me to such
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Tested and worked. Easier still is to just choose the "copy binaries" option from the Solution's context menu.
ASKER
So about the other part of my question, what should I expect for pages that already host the webpart.
Will they continue to work withe new version once the webpart is redeployed or I need to remove and add back the webpart to pages that were using it?