Last post Sep 01, 2013 11:43 PM by chetan.sarode
Aug 31, 2013 10:23 PM|AnotherDayAnotherDollar|LINK
I have just upgraded my Microsoft Visual Studio 2010 C#.NET application and Azure project to Visual Studio 2012. My project includes the Ajax Control Toolkit and I am using the Masked Edit extender for a number of textboxes and also the Calendar control
for date input. As part of this, I upgraded to the latest version (v22.214.171.1245) of the Ajax Control Toolkit using NuGet.
Everything is working fine locally, both running the project in debug mode and using the Azure Compute emulator. However, when I deploy my project to Windows Azure, the Masked Edit extender and Calendar controls completely refuse to work - it is as if they
are not there. No error messages are displayed.
In order to to fix this, I have tried the following:
1) Ensure the "Copy Local" property of the AjaxControlToolkit assembly is set to True
2) Changed the ServiceConfiguration.Cloud.csfg to set the Azure Server OS to Windows Server 2012 using the osFamily="3" attribute of the ServiceConfiguration tag.
3) Opened the <application>.Azure.cspkg file using winzip to ensure that it contains the correct version of AjaxControlToolkit.dll for deployment to my Azure instance (it does).
None of these resolved the problem.
It would be interesting to know if anyone else has experienced this problem and if there is any possibility of a fix.
Sep 01, 2013 04:52 AM|stmarti|LINK
I see here two possible problem which are independent each other.
a) The ajaxcontrol toolkit releases are usually tied to a specific .net version. So the latest built only for .net 4.5. If your azure role is configured with an os family which is not .net 4.5, you have problem. The solution is to
downgrade the toolkit to a prev version (see my post after the accepted answer)
b) Your dev machine timezone is "ahead" in time to the azure vm. In this case when you deploy to azure, "webresource.axd?xxxx" style scripts won't be output in the rendered html until some time. Example: azure vm is in GMT UTC, your time zone is +1Hour.
After deployment in the first hour you won't get scripts (asp.net try caching the scripts, but cannot set some time in the "future"), after one hour elapsed, your site starts working.
This is one of the most idiot bug in asp.net, and seems ms cannot fix it.
The fix is to set your dev machine in gtm utc, rebuild and redeploy to azure.
Sep 01, 2013 09:25 PM|AnotherDayAnotherDollar|LINK
I finally managed to resolve this.
The problem was that I had altered the section in my pages containing the following code:
<asp:ScriptManager id="ScriptManager1" runat="server">
<asp:ToolkitScriptManager id="ScriptManager1" runat="server">
This had stopped the ajax control toolkit extenders working properly.
As soon as I changed these back, then everything started working as it should.
Thanks for your speedy response to my enquiry.
Sep 01, 2013 11:43 PM|chetan.sarode|LINK