With MOSS, it seemed like most web part developers tended to avoid changing the version of their DLL, because it lead to numerous headaches as you had to update the .webpart file. You also had to update any page that you might have the web part on as well so that it would load the new version. What’s nice about SharePoint 2010 is that your manifest file in your solution package can now deploy binding redirects to your web.config. For example, this means you can have any reference to version 188.8.131.52 redirect to use version 184.108.40.206. Binding redirects are nothing new to .NET, it’s just that SharePoint is now taking advantage of this feature. In fact, SharePoint uses this feature itself to redirect any calls to its DLLs from version 220.127.116.11 to 18.104.22.168. Here is an example of what that might look like.
<Assembly DeploymentTarget="GlobalAssemblyCache" Location="MyWebParts.dll">
<BindingRedirect OldVersion ="22.214.171.124" />
<SafeControl Assembly="MyWebParts, Version=126.96.36.199, Culture=neutral" Namespace="MyWebParts" TypeName="*" Safe="True" />
I really like this new feature and I think it will make it much easier for developers to version their assemblies.