I have tried to deploy my application (which works fine in VS2008, webdev server and IE8) to my local IIS6 web server.  I have followed the instructions on the wiki for deploying to IIS6 (although I have kept the default .wgx file extension rather than change it to ashx - my app stops working completely if I do this, but that is another matter!).

When I browse to the explicit startup form (i.e. http://localhost/myapp/MainForm.wgx), I get a blank page with a "Done, with errors" type message in the status bar.  IE8 says the javascript error is:

Webpage error details

User Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; InfoPath.2; MS-RTC LM 8)
Timestamp: Fri, 9 Apr 2010 12:00:03 UTC

Message: Expected ';'
Line: 107
Char: 254
Code: 0
URI: http://localhost/myapp/Route/1.96.1/ie/en-US/Default/Resources.Gizmox.WebGUI.Forms.Form.js.wgx

Accessing the same URL in FireFox 3.6 gets me in - although none of my graphics files in Resources\Images and Resources\Icons are recognised.  However, my client uses IE, so if this is an IE specific bug, I have a BIG problem.  I don't understand why it would work in IE8 in the IDE but not when deployed.

I am using VWG 6.3.11 and I have double checked the IIS settings and the deployed DLLs and my web.config and all appear OK.

There are a variety of issues here.  Can anyone help?

Hi Palli

I don't appear to have UrlScan installed (judging by the lack of a urlscan.ini file or log file directory on my machine).  Sorry, the IIS on my local machine is 5.1, not 6.0 as specified in the first post.  Does this make a difference?

Thanks.

Hello NR,

One more thing:
Please try removing all browser cache of the browser you are using to access this IIS5.1 deployment.
Next, please incrementing the PrivateVersion configuration value via the deployed Web.config file of your appication.
After removing cache, please try again to access your application and see if you still have the JavaScript error.

Regards,

Ori Cohen
Support Manager, the Visual WebGui team