Solved

How to Update a Custom Webpart using WSPBuilder and Visual Studio 2008

Posted on 2010-08-20
5
1,670 Views
Last Modified: 2012-05-10
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.
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.

Open in new window

0
Comment
Question by:Dahlsim
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
5 Comments
 
LVL 10

Assisted Solution

by:krunal_shah
krunal_shah earned 150 total points
ID: 33491238
yes you first have to Uninstall the webpart ( you can do it from wspbuilder menu also) and then Deploy it again.
0
 

Author Comment

by:Dahlsim
ID: 33494201
Thanks for the reply.  

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?
0
 

Author Comment

by:Dahlsim
ID: 33502185
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
0
 

Accepted Solution

by:
Dahlsim earned 0 total points
ID: 33504235
For anyone else who might hit this question looking for help on upgrading custom webparts in this iteration of sharepoint (MOSS 2007) here's a thread I found helpful.

http://social.msdn.microsoft.com/Forums/en/sharepointdevelopment/thread/75507886-a5d3-4787-be93-7ad42719b4ce 

Looks like it's possible to upgrade more easily if you avoid changing the assembly version?   Still interested if any experts out there have comments but I'll be giving this a test...
0
 

Author Comment

by:Dahlsim
ID: 33508641
Tested and worked.   Easier still is to just choose the "copy binaries" option from the Solution's context menu.
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

For SharePoint sites, particularly public-facing ones, there are times when adding JavaScript, Meta Tags, CSS Styles or other content to the page <head> section is more practical than modifying master pages.  For instance, you could add the jQuery l…
Pimping Sharepoint 2007 without Server-Side Code Part 1 One of my biggest frustrations with Sharepoint 2007 in the corporate world is that while good-intentioned managers lock down the more interesting capabilities of Sharepoint programming in…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an antispam), the admini…
Finding and deleting duplicate (picture) files can be a time consuming task. My wife and I, our three kids and their families all share one dilemma: Managing our pictures. Between desktops, laptops, phones, tablets, and cameras; over the last decade…

734 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question