VS.NET 2005 and the "allowDefinition='MachineToApplication'" error

A day or two ago, I wrote a quick ASPX page with a CS codebehind using
Visual Studio .NET 2005 -- it worked, I saved it and closed the
project. Today, I came back to the project, reopened the solution, and
was greeted with the following error:

========================================================================
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.
========================================================================

I did some searching on Google, and all of the solutions to this
problem involved tweaking IIS. The thing is, I didn't have to touch
IIS when I wrote, compiled and ran the ASPX the first time around --
why would I have to do it during a subsequent visit?

If anybody has any suggestions on how to resolve this problem, I would
greatly like to hear them. Thanks in advance!


-= Tek Boy =-

.

Relevant Pages

  • Re: newbie question
    ... > Now do I need Visual Studio .NET, ... Visual Studio.Net provides you with all the latest debugging and compiling ... > that work like CGI or IIS extensions? ... compiled DLLs with ASPX page templates. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Different folders for aspx and codebehind files
    ... Thanks for replying. ... files the way I want in Visual Studio, but the problem is that VS.net ... This codebehind attribute only allows you to ... I know several organizations that split ASPX ...
    (microsoft.public.dotnet.framework.aspnet)
  • VS.NET 2005 and the "allowDefinition=MachineToApplication" error
    ... I wrote a quick ASPX page with a CS codebehind using ... Visual Studio .NET 2005 -- it worked, I saved it and closed the ... problem involved tweaking IIS. ...
    (microsoft.public.vsnet.general)
  • RE: Session not available in Visual Studio IDE
    ... To ASPX page in a code section or in the CodeBehind? ... > after I've added a property to my web page I can't open it in Visual Studio ... > Designer anymore. ...
    (microsoft.public.dotnet.framework.aspnet)
  • RE: How do I reference a second class than the codebehind page?
    ... should break out any of these "comon" methods into its own class and have ... I have my .aspx page and its .cs codebehind page that Visual Studio ... > want to use it in the codebehind page. ...
    (microsoft.public.dotnet.framework.aspnet)
Loading