ASP pages don't load in browser (Runtime error, Config error)
- Expression Web 2 .aspx pages load fine in my development server but generate an error message when viewed after publishing. The error message is a generic "runtime error" about custom error pages, but my host gave me the error behind it. They believe the problem is because I use Expression Web 2 with .net 3.5 on my local computer but they only support .net 2.0. Here is the error message they supplied:
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Unrecognized attribute 'type'.
Source Error:
Line 3:
Line 4: <configSections>
Line 5: <sectionGroup name="system.web.extensions" type="System.Web.Configuration.SystemWebExtensionsSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
Line 6: <sectionGroup name="scripting" type="System.Web.Configuration.ScriptingSectionGroup, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35">
Line 7: <section name="scriptResourceHandler" type="System.Web.Configuration.ScriptingScriptResourceHandlerSection, System.Web.Extensions, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31BF3856AD364E35" requirePermission="false" allowDefinition="MachineToApplication"/>
I know very little about web.config pages other than how to generate one in Expression Web 2 for .net 2.0 and 3.5, and that the file needs to be in the root folder. Is there some way to get aspx pages to work without the server installing .net 3.5 which they are not willing to do. They claim it is not stable.- Changed Typechrismiss Tuesday, September 29, 2009 4:43 PM
All Replies
- I talked to Microsoft today (paid support) and I got a real hard answer. Unless I am able to program a new web.config page, the local computer and the remote server BOTH must have .net framework 3.5 installed or .aspx pages will not display.
- The host installed .net 3.5 today and it DID NOT correct the problem.
