So we recently came across an issue where Visual Studio 2005 and 2008 Designers were not respecting assembly binding redirection.
We have a file which is now version 2 and stored in the GAC. So the assembly version is 18.104.22.168. We have some existing customers using version 1 so we want to be able to use Assembly Binding Redirection to point them to the new version of the assembly.
For more information on configuring this, check out Configuring Assembly Binding Redirection.
The web page has code like:
<tc:TestContacts ID="QuickContacts1" runat="server"> <tc:AContact Name="Test Tester" Email="email@example.com" Phone="(999) 555-1212" /> <tc:AContact Email="firstname.lastname@example.org" Name="Mr. A. Nonymous" Phone="(999) 555-1234" /> </tc:TestContacts>
We also have a Register Assembly line at the top that points to the 22.214.171.124 version of the file. And we have an entry in our web.config that looks like this:
<runtime> <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="Tester1" publicKeyToken="6ace53ab3256c766"/> <bindingRedirect oldVersion="126.96.36.199-188.8.131.52" newVersion="184.108.40.206"/> </dependentAssembly> </assemblyBinding> </runtime>
We could have done this in a policy file and got the same results. So now we open this file in Design view inside Visual Studio and change a property of the TestContacts control. For instance, adding an AccessKey. Switching back to the Source view, we will now see:
<tc:TestContacts ID="QuickContacts1" runat="server"> <samples.aspnet.cs.controls.acontact Name="Test Tester" Email="email@example.com" Phone="(999) 555-1212" /> <samples.aspnet.cs.controls.acontact Email="firstname.lastname@example.org" Name="Mr. A. Nonymous" Phone="(999) 555-1234" /> </tc:TestContacts>
This breaks the site and it no longer works.
Note: Assembly Binding Redirection works find in other scenarios, it just doesn’t work right inside the Designer.
There are two ways to resolve this issue.
- Don’t use Assembly Binding Redirection at all and just leave the 220.127.116.11 version of the file in the GAC. You will see a lot of .NET files do this, there are versions for .NET 1.0, 1.1, 2.0, etc all inside the GAC at the same time.
- Change the existing files so that the Register Assembly line at the top of the web page points to the 18.104.22.168 version of the file.
Keep in mind that this is only a problem if you are actively changing the older files already, if you don’t touch the file it will be fine since this issue is only with the Designer. So since you are already updating the file, it is trivial to update this line also.
We are looking into this issue also, so there may be another resolution posted in the future.