.NET Policy / AJAX script permissions

Guys,

I have developed an asp.net2 website. I am hosting it inside a company application, in a HTML viewer attribute on a form. I don't know exactly what the HTML viewer is, I just throw in a URL and it displays the page.

Anyway. I have deployed the site onto a server and have IIS all set-up and running. The site loads fine in IE6 locally. It also loads fine in IE6 on all clients.

When I try to run this in my HTML viewer attribute in my internal app, it loads the page fine, but then I get an error on any click event. ANY click on the page, even in whitespace throws the IE Script Error...

"An error has occured in the script on this page." "Access Denied" Do you want to continue running scripts on this page.

If I click Yes, functionality works as required, I just get this error with every single click. The error gives a line number 5960 in my main.aspx, but even when rendered its only 247 lines...


Thinking about this more.... this is probably Ajax related. My first page that the user visits has 4 hyperlinks on and nothing else, this page works fine. But those hyperlinks direct to pages that host Ajax TabControls....

Can anybody suggest what this could be? I'm thinking its .net permissions related from my internal application trying to access something, but I dont know what

Thanks in advance,
Bob

EDIT - Thinking some more.... I have the AjaxControlToolkit.dll sat in the bin of the website, with this line in my home.aspx
<%@ Register Assembly="AjaxControlToolkit" Namespace="AjaxControlToolkit" TagPrefix="cc1" %>
Would it make a difference if I dropped the dll into the GAC? If I did, how would I tell my app to look for it there with the tag prefix "cc1">

HTML Viewers are 'stripped down' versions of IE. It's like an IE shell with bare-minimum basics.

The line 5960 is from the dynamically created AJAX script file, it's probably encountering something that it cannot support or that does not exist (because the viewer doesn't have everything the full fledged browser does).

You can confirm that this is the case by creating a simple page in your app with some simple javascript in it and then attempting to view it in that application. Increasing levels of complexity may eventually introduce that same problem but I'm quite sure that it's the existence of the framework (which is referenced) which is causing those script errors. In a way it does make sense because you're attempting to view a rich application in a stripped down browser, but at the same time it's a company thing for you, it seems, which is going to be a severe limitation.

If it turns out that it's AJAX's presence causing this, then you'll probably need to redo all the rich bits yourself without the framework.