Errors when trying to compile and run my VS2005 / ASP.NET 2.0 website in VS2008 / ASP.NET 3.5.
HI,
I get the following errors when trying to compile and run my VS2005 / ASP.NET 2.0 website in VS2008 / ASP.NET 3.5.
It is an error to use a section registered as allowDefinition='MachineToApplication'beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS. C:\Users\Admin\Documents\Visual Studio 2008\WebSites\smk7\Backup\smk7\web.config 95
I thought it had something to do with not creating a virtual directory called 'smk7'and then registering it as an application in IIS 7, but after I did this it still did not work. I also noticed that two sample websites I made from scratch in .NET 3.5 did not appear as virtual directories or applications anywhere in IIS 7. Can anyone help me with these issues? Maybe there are multiple versions of IIS on my machine? I am running Windows Vista Ultimate.
The errors are sent in the next posting.
Re: Errors when trying to compile and run my VS2005 / ASP.NET 2.0 website in VS2008 / ASP.NET 3.5.
Description: The requested page cannot be accessed because the related configuration data for the page is invalid.
Error Code: 0x80070005
Notification: BeginRequest
Module: IIS Web Core
Requested URL: http://localhost:80/smk7
Physical Path: C:\Users\Admin\Documents\Visual Studio 2008\WebSites\smk7
Logon User: Not yet determined
Logon Method: Not yet determined
Handler: Not yet determined
Config Error: Cannot read configuration file
Config File: \\?\C:\Users\Admin\Documents\Visual Studio 2008\WebSites\smk7\web.config
-1: 0:
More Information... This error occurs when there is a problem reading the configuration file for the Web server or Web application. In some cases, the event logs may contain more information about what caused this error.
Are you running VS during conversion as admin?
Re: Yeah!
Yes, I am logged in using admin. Do I have to use "Run As Administrator"just like I had to do in VS2005?
Re: Try running VS as administrator
Yes, try running VS as administrator since even logging on as admin does not necessarily mean you run elevated.
Re: Thanks