Geeks With Blogs

Tangible Thoughts SharePoint, MOSS? and all the other questions

I am not really sure if I've posted anything on this topic before. I feel like I have, but if so I couldnt find the post in the archive.

So I am risking a second post. However I did asked a similar question up on the sharepoint newsgroup some time back.

Over the past few months my team has been building an intranet application based on SharePoint. We've basically being rolling out our own custom WebParts.

Whats very odd about managing a WebPart development project is that, versioning is a pain.

To increment the version of a webpart library there are several locations where a version string needs to be changed.


  • assemblyinfo.cs (i feel like I have blogged this topic before)
  • webpart dwp file
  • web.config file

So wanting to simplify the process for the team, I built a mini versioning system that took care of all of this.

All that needed to be done was run a command line tool and say something like increment or set <version> (e.g. vwl.exe -newbuild)

But all is not well in portal town. If a webpart has been added to a webpart page, and then the version is changed, the page throws an error when it tries to load.

Why? because the Tagprefixs on the aspx page still point to older version of the dll.

The resulting situation (if you change the WebPart version) is very messy.

Was wondering if there were any known Bestpractices around this.


Posted on Friday, February 13, 2004 5:54 PM SharePoint | Back to top

Comments on this post: WebPart versioning

# re: WebPart versioning

# re: WebPart versioning
Requesting Gravatar...
Left by Tariq on Feb 15, 2004 3:56 AM

# re: WebPart versioning
Requesting Gravatar...
Using bindingRedirect addresses foward compatibility with the assumption that the interface contract is intact ... however semantic contracts could still cause breakage (especially for 3rd party webparts) ... one is icons changing or changing meaning between versions, in this case bindingRedirect might cause old site to still render the new webPart, but it's display might be incorrect or inconsistent with new sites using the same webPart ... Versioning seems like a complex issue in SPS ... I wish there was better guidance thant this excerpt from the SDK ---> "SharePoint site administrators decide how to apply versioning policy to Web Parts. By default, no versioning policy is in place, which means that each Web Part assembly reference requires the exact version."
Left by manakhan on Oct 19, 2004 10:08 PM

Your comment:
 (will show your gravatar)

Copyright © Tariq | Powered by: