You work for a software company that sells Web Parts to customers. You designed the first version of a Web Part
named Weather 1.0. The company has already sold several hundred licenses of the Web Part. You designed a
new solution package for Weather 2.0. Some customers who are already using Weather 1.0 will install Weather
2.0 in the same Web application as Weather 1.0. You need to design your package so that the functionality of
Weather 1.0 will not be affected by the installation of Weather 2.0 in the same Web application.
Which approach should you recommend?
A.
Use the same assembly name and namespace for Weather 2.0 that you used for Weather 1.0.
Create a new .web part file. Increment the version number in the .web part file.
B.
Use the same assembly name and namespace, but increment the version number of the assembly package.
Use the same .web part file that you used for Weather 1.0.
C.
Use the same assembly name and namespace, but increment the version number of the assembly package.
Configure assembly binding redirection from version 1.0 of the assembly to version 2.0.
Use the same .web part file that you used for Weather 1.0.
D.
Use the same assembly name and namespace, but increment the version number of the assembly package.
Create a new .web part file.
http://msdn.microsoft.com/en-us/library/cc768621(v=office.14).aspx
http://blogs.msdn.com/b/andrasg/archive/2011/07/19/the-good-solution-for-versioning-sharepoint-2010-webparts.aspx