Server Error when publishing Web App w/ VS 2010 LightSwitch

I'm using web deploy to trying to publish a simple/basic LightSwtich app but seem to be getting stuck with server errors.

The web app seems to deploy/publish without any problem but when I go to it via the browser (on my Winhost site), I get compiler version errors. I have ASP.net set to 4.0 on the site. Which should be identical to the basic little web app I'm building. The funny thing is, the web app runs fine locally...but once it's published, I run into errors.

I've followed the step by step instructions in the article/blog that another member has posted/written on here: Hosting LightSwitch Applications on Winhost...but I'm not sure why I'm getting these errors. I figure it's a small setting I'm overlooking but don't know what it could be.


This is the error:
The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the element of the Web.config file.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Configuration.ConfigurationErrorsException: The value for the 'compilerVersion' attribute in the provider options must be 'v4.0' or later if you are compiling for version 4.0 or later of the .NET Framework. To compile this Web application for version 3.5 or earlier of the .NET Framework, remove the 'targetFramework' attribute from the element of the Web.config file.

 

I just wanted to update this thread. Not sure what has changed exactly but I'm not longer seeing the compilerversion error after publishing the LS app.

After publishing, I did see another/different error in regards to permissions. After searching the forum I stumbled across a post pointing to this KB article.

http://support.Winhost.com/KB/a657/changing-the-default-aspnet-trust-level.aspx

The solutions in this kn article did the trick.

 

Nice. Thanks for following up.