Upgrading and Versioning

Assembly Versions
Sometimes deploying a web part with a higher version number will cause some problems.
In the slution’s Manifest.xml (might need to edit and merge), add these – it will re-direct the version “1.0.0.” to the current assemly version.



The other thing is $SharePoint.Project.AssemblyFullName$


Basically, when you package your WSP SharePoint will automatically swap out this value for the fully-qualified Assembly Reference for the current project state. This means it will swap out the full Assembly name, version number, culture and Public Key Token.

Feature Versions

Each feature can be given a specific version number. If you don’t, it’s 0.0.0.0.

new sets of XML elements, starting from <UpgradeActions>

<VersionRange> Can specify BeginVersion and EndVersion
<AddContentTypeField> Add a field to an existing content type
<ApplyElementManifest> apply a specific element manifest when the upgrade process kicks off
<MapFile>
<CustomUpgradeAction>

Example:



 

Advertisements
Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: