How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Dhivya — Tue, 18 Aug 2009 10:28:29 GMT

Thank u so much..

you saved my day...

i had two 'sys' undefined errors after patching the file...please make sure that you have placed all the JS files which you downloaded into the '~/Javascript/System.Web.Extensions/1.0.61025.0/MicrosoftAjax.js' path.

and i have added the following:

<asp:ScriptManager ID="ScriptManager1" runat="server">

<asp:ScriptReference Name="MicrosoftAjax.js" Path="~/Javascript/System.Web.Extensions/1.0.61025.0/MicrosoftAjax.js" />

</Scripts>

</asp:ScriptManager>

then it worked well without errors.

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

marco hokke — Mon, 27 Jul 2009 14:56:38 GMT

Thanks for this post. Together with Delay's Blog (which pointed me to yours) and Damian Mehers' (which pointed me to the location of the MicrosoftAjax.js) I managed to get our .Net 2.0 ASP.Net with the Ajax Toolkit working properly in an iFrame on our company's site.

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Fred — Tue, 16 Jun 2009 09:57:27 GMT

Here you can find a very easy fix for it.

forums.asp.net/.../1216682.aspx

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Hunter — Thu, 04 Jun 2009 15:06:04 GMT

can u take off access denied on this computer?

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Vlad — Tue, 19 May 2009 12:56:57 GMT

Bertrand Le Roy THANKS!!!!!

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Bertrand Le Roy — Wed, 06 May 2009 17:42:05 GMT

@jgdean: having static script references is the way to go. The script profiler that is available on CodePlex/aspnet can help you determine the set of scripts you need for any given page.

I'd also encourage you to upgrade to 3.5 SP1 if you can.

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

jgdean — Wed, 06 May 2009 15:18:57 GMT

Thanks Bertrand for the fix. We are running .NET 2.0 using VS2008 and using the Toolkit as well. I referenced the altered MicrosoftAjax.js per instructions above, and I still needed to let the scriptmanager reference the Toolkit. As a result, the Scriptmanager version in the "/ScriptResource.axd?..." was being called first and the fix was not applied, even though I can see the altered version of MicrosoftAjax.js being referenced after the scriptmanager version in the source code. So I was left with trying to create static references to the toolkit code or apply a "monkey-patch". I struggled to find a version of the .NET20 Toolkit .sln that would compile in VS2008 so ended up with the patch. It works but it's not pretty. Is there a newer version of the system.web.extensions than 1.0.61025.0 that already has this fix in place for .NET2.0? Or maybe I am not referencing the toolkit correctly?

Thanks again, without your post I would be lost!

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Bertrand Le Roy — Wed, 29 Apr 2009 23:19:39 GMT

@Augusto: did you deploy the patched MicrosoftAjax.js file to the dev server? Did you check the script was getting downloaded using Firebug or Fiddler? Did you check you were getting no syntax errors?

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Augusto — Wed, 29 Apr 2009 23:05:03 GMT

I've referenced the altered script like this:

<asp:ScriptManager ID="ScriptManager1" runat="server" EnablePartialRendering="true" EnablePageMethods="true">

<asp:ScriptReference

Name="MicrosoftAjax.js" ScriptMode="Auto"

Path="~/scripts/AJAX/System.Web.Extensions/1.0.61025.0/MicrosoftAjax.js"/>

</Scripts>

</asp:ScriptManager>

The scriptManager tag is in a masterpage, and I've aplied the correction to the MicrosoftAjax.js as described above. Also, I downloaded the newer version of ajaxControlToolkit WITH the 'Common.js' already aplied.

I can run the code without any error on my javascript, but when I deploy it to our development server, I get the 'Sys is undefined' error at ScriptResource.axd, and the a 'Type is undefined' error, even if I use the original version or the altered version of the script.

Can you point me where could be a file/installation defining this?

re: How to work around the access denied cross-domain frame issue in ASP.NET Ajax 1.0

Bertrand Le Roy — Tue, 28 Apr 2009 17:44:39 GMT

@Joe: could be several things. You might have patched only the debug version and not the release one (that would explain that it works on the dev box and not the server), you might have omitted to copy your patched files over, the error might come from your own code, something I haven't thought of or a combination of the above.