Jump to Content
The opinions expressed herein are my own personal opinions and do not represent
my employer's view in any way.
newtelligence dasBlog 2.2.8279.16125
Email Me (Tim Gaunt)
© 2013 Tim Gaunt.
Being a fair way into an application that relies heavily on Atlas I wasn’t best pleased to hear that Microsoft had done the usual comedy act of renaming the framework which would mean we’d have to update a plethora of controls.
Today we bit the bullet and along with a few other changes we already had planned made the switch. It wasn’t as bad as I was expecting tbh but it wasn’t without issues. The first issue we ran into was with Visual Studio’s Intellisense which has gone haywire, the recommended solution is to switch quickly between Design Time and HTML View –something that we can’t do as we’re using nested MasterPages which Visual Studio doesn’t support.
The next issue we ran into was the fact that our onKeyPress TextBox has now stopped working as planned but we’re looking into that.
The main issue that we ran into this morning however was on putting the site onto the server as we were faced with the following:
Line 97: <assemblies>
Line 98: <add assembly="Microsoft.Web.Extensions, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"/>
Line 99: <add assembly="Microsoft.Web.Extensions.Design, Version=1.0.61025.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35"/>Line 100: <add assembly="System.Design, Version=18.104.22.168, Culture=neutral, PublicKeyToken=B03F5F7F11D50A3A"/>Line 101: <add assembly="System.Windows.Forms, Version=22.214.171.124, Culture=neutral, PublicKeyToken=B77A5C561934E089"/>
WRN: Assembly binding logging is turned OFF.To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.Note: There is some performance penalty associated with assembly bind failure logging.To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
The official take on this from the Microsoft guys is somewhat comical (http://forums.asp.net/thread/1455060.aspx):
Hi guys - yeah the problem you're having is because you installed on a machine w/o VS. All of our machines have VS, so we didn't catch this problem. On a machine w/ VS, Microsoft.Web.Extensions.Design.dll gets dropped.
Probably the best workaround for this is to go get that file from a machine with VS and either install it (gacutil -f Microsoft.Web.Extensions.Design.dll) or try dropping it into the bin directory, which I believe should also work but I haven't tried it.
I've been talking with the AJAX team about this, so we're on top of it. Sorry for the confusion.
Not an ideal fix but at least it works! For those of you wondering where you can find the DLL, look in: %Program Files%\Microsoft ASP.NET\ASP.NET 2.0 AJAX Extensions\v1.0.61025
Don't forget to follow me on Twitter.