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

Tech-Archive recommends: Fix windows errors by optimizing your registry

I don't understand, though -- *what* became unmapped? I haven't
touched IIS on my machine to date, which is running a vanilla
installation of Windows XP Professional and Visual Studio .NET 2005.
Do I need to create a virtual directory for each and every project I
want to test?

I thought VS.NET 2005 came with its own internal IIS-Lite webserver,
which is why you can debug a project without configuring IIS, and which
is why you also see a dynamic port number when you debug a script
without actually deploying it. Is that belief mistaken?


-= Tek Boy =-


Alvin Bruney [MVP] wrote:
hmmm, you are best served by inspecting the IIS virtual directory to see if
it *somehow became unmapped. If it is, just create a new virtual directory
pointed to the application. And watch out for the little elves that change
things when no one is looking :-)

--
________________________
Warm regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
Professional VSTO.NET - Wrox/Wiley
The O.W.C. Black Book with .NET
www.lulu.com/owc, Amazon
Blog: http://www.msmvps.com/blogs/alvin
-------------------------------------------------------


<deathtospam@xxxxxxxxx> wrote in message
news:1163111193.739754.239210@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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: VS2008 HTTP 403 Help!!
    ... Juan T. Llibre, asp.net MVP ... asp.net faq: http://asp.net.do/faq/ ... That error is caused by a virtual directory not being configured as an application in IIS. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: VS.NET 2005 and the "allowDefinition=MachineToApplication" error
    ... Juan T. Llibre, asp.net MVP ... No, it's not, but the same rules apply for the internal web server as for IIS. ... If you need to use 'MachineToApplication' sections, you must create a virtual directory. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: "An error occurred accessing your Windows SharePoint Services site files"
    ... This really sounds like a Visual Studio .NET or ASP.NET problem. ... Start IIS and see if you can browse ... > FrontPage 2002 Server Extensions, or some vestigial junk from SharePoint, ... > to create a new web site in FrontPage 2003. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: IIS Virtual Directory Woes
    ... When I am in a WAP project settings and switch over to the IIS setting, ... cannot save without being prompted to create the virtual directory. ... If I created it ahead of time, Visual Studio ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: How do I use copy web site
    ... This really isn't a .NET or Visual Studio issue, ... having your web server (IIS) set up and moving the files into position. ... My web site is located in F:/MyTest ... I have added a virtual directory called MT that points to the physical ...
    (microsoft.public.dotnet.framework.aspnet)