Welcome to AspAdvice Sign in | Join | Help

Replace "Framework" scripts in ASP.NET Ajax

A user reported at newsgroups there being an issue in Safari 1.3.2 with ASP.NET Ajax's release mode scripts. He said that release script wouldn't parse and suspects it relates to the compression (script being on one line) as with debug script it works just fine. He also said that on later Safari versions it works in both modes.

In cases like this you can:

- take a copy of the built-in script files needing replaced functionality
- put them say on some folder on your application
- fix what needs to be fixed in the files.

Then just give Path to them in ScriptManager to get them in use (give also the Name despite that documentation says you'd need only Name or Path)

<asp:ScriptManager ID="ScriptManager1" runat="server">
        <Scripts>
            <asp:ScriptReference Name="MicrosoftAjax.js" Path="[directory to look for]/MicrosoftAjax.js" />
            <asp:ScriptReference Name="MicrosoftAjaxWebForms.js" Path="[directory to look for]/MicrosoftAjaxWebForms.js" />
        </Scripts>
    </asp:ScriptManager>

(You can also set ScriptPath of the ScriptManager in case you want to do it for all files at once)

This changes things so that these are looked from the location given in the path, not by loading from script resources, and it lets you modify them at will. Very easy fixing in case needed.

Note: Bertrand has great post covering the same ground:

How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0
http://weblogs.asp.net/bleroy/archive/2007/01/31/how-to-work-around-the-quot-access-denied-quot-cross-domain-frame-issue-in-asp-net-ajax-1-0.aspx

Relevant documentation entries:

ScriptReference
http://ajax.asp.net/docs/mref/T_System_Web_UI_ScriptReference.aspx

Path property
http://ajax.asp.net/docs/mref/P_System_Web_UI_ScriptReference_Path.aspx

 

 

Published Friday, February 16, 2007 12:18 AM by joteke
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

# re: Replace &quot;Framework&quot; scripts in ASP.NET Ajax

Parser bugs in Safari 1.3 will be the least of your problems. We shouldn't give users the false hope that doing that will make Ajax work with Safari 1.3. There are too many things that are not working on this browser, which is why we couldn't support it.
Friday, February 16, 2007 12:26 AM by Bertrand Le Roy

# Calling for exact list of browsers supported in ASP.NET Ajax 1.0

Bertrand commented to my previous post about the Safari support. That got me thinking, has anyone seen

Friday, February 16, 2007 2:18 AM by Joteke's Blog

# re: Replace &quot;Framework&quot; scripts in ASP.NET Ajax

Love your work dude! Had an issue with my site running through a VPN and this solved it!!
Tuesday, January 27, 2009 12:39 AM by Rv

Leave a Comment

(required) 
required 
(required) 
Enter the code you see below