I am having a devil of a time getting a couple of VB 2003 web apps that have been converted to VB 2005 to run on the remote server I use ... I am able to debug/run them on my local development machine. The problem seems to be centered around the web.config files for these apps. They each contain <compilation> elements with embedded <compilers> and <compiler ...> child elements. The <compiler ...> element has a number of attributes including compilerOptions. When I run each app from the server I get the following message:
Parser Error Message: The current trust level does not allow use of the 'compilerOptions' attribute
I have been in touch with the server folks (where I had been running the VB 2003 version w/.Net 1.0 without difficulty) and they claim that they have converted me over to .Net 2.0 and I have the proper permissions, etc. ... yet this problem persists. Can someone suggest what may be going on here and how I might extricate myself from this situation
Another curious aspect of this: one of the apps has a squiggly blue line under the <compilation> element which when I hover over it says somehting to the effect that <compilers> is not a valid child element of <compilation>. What in the world is THAT all about ... and why would the 2003-to-2005 conversion wizard create an invalid web.config file ! The other app does not have this squiggly line but it also has <compilers> as a child element of <compilation> ... it also has an <assemblies> element [which the other app does not] ... and three <add assembly ... > directives each of which involves Crystal.Decisions! I don't have a clue what that's all about.
I think I am close to getting these apps running but I could sure use some help (or references to help) for how to deal with these problems.
trust level does not allow use of the 'compilerOptions' attribute