Visual WebGui deployment issues

I made a test Visual WebGui app and locally it’s running fine. I upload it to my site, made sure to have all the gizmox references set to “copy local” and set the directory as a web application but it yields the following error:

HTTP Error 500.23 - Internal Server Error An ASP.NET setting has been detected that does not apply in Integrated managed pipeline mode.

When this gave me issues I tried to roll to Classic and got a different error:

HTTP Error 404.0 - Not Found The resource you are looking for has been removed, had its name changed, or is temporarily unavailable.

I contacted Discountasp.net and they told me if I ran it on classic mode I'd have to define the MIME type myself, but I'm not sure what settings to use. Not only that, but I would rather make it work in Integrated mode anyways. I think I read of quite a few developers running their VWG projects at Discountasp.net without any issue under integrated so I guess the issue is in my project or configuration, I just can’t guess what may be wrong on it that would make it fail in the host but run locally.

The app link is http://foundersfal.web705.discountasp.net/test/index.wgx, in case the error message is more descriptive to anyone. Right now I have it set up to run integrated mode.

Any help will be highly appreciated.

 

You will need to connect to our IIS 7 server using IIS 7 Manager. Refer to this kb article for the instructions.

http://kb.discountasp.net/KB/a400/how-to-connect-to-windows-2008iis-7-using-microsoft.aspx

Once connected go to the HTTP Features and click on MIME Types to define your own MIME type.

 

I managed to get it to work under classic mode by changing the extension this morning (found steps to do that on Visual WebGui's site) but the extension seems to not be the issue running under integrated mode.

I can leave it there and just work in classic mode but would love to be able to just make it work under Integrated now as I can see eventually things changing and classic support being discontinued.

Another question while at it: if I decided in the future not to go through the hurdle of reconfiguring the extension in the project, what MIME type should I assign to the .wgx extension?

 

I don't think its a mime type problem but a mapping problem. If you're running in classic mode you'll probably need to map the .wgx extension to the asp.net ISAPI. This can be done through the IIS 7 Manager. From the previous thread use the KB article to configure your IIS 7 Manager to connect to our IIS 7 go to HTTP Features and click on Application Mapping.