Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

MSBuild error while compiling ASP.NET website

Tags:

asp.net

I get the following error when I try to compile an asp.net site using a custom build script.

error ASPCONFIG: 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.

Although the description is in detail I do not understand what it means exactly. I have not configured IIS to host this website and I don't think I will be able to as I am running Vista Home Basic version. So the website cannot be built using custom scripts?Please reply as I want to test this feature.

like image 303
kjayakum Avatar asked Feb 06 '09 18:02

kjayakum


4 Answers

I had this SAME EXACT problem and finally discovered a rogue Web.config was placed in my obj folder ... do yourself a favor and do a search in all the sub-directories for a web.config file. I deleted it and all was back to normal.

like image 200
Jason Wicker Avatar answered Nov 17 '22 04:11

Jason Wicker


The rogue web.config file in the obj folder is most likely to be caused when you do a Publish Web Site. So just clean it up after you've done the publish.

like image 44
Daniel O Avatar answered Nov 17 '22 03:11

Daniel O


if this happens after the virtual-directory is already created do the following:

  • right-click on web.config
    • properties
      • Build Action: Content
      • Copy to Output directory: Do not copy
  • if transformed (apply to all configurations)
    • properties
      • Build Action: None
      • Copy to Output directory: Do not copy
like image 5
mg3 Avatar answered Nov 17 '22 04:11

mg3


It is likely that your web.config file is placed in a directory that is not the root of the application. On most versions of IIS, you can convert any folder on your web site to an application root:

  1. Open IIS and navigate to the appropriate folder
  2. Right-click on the folder, select properties
  3. Under Application Settings, and beside Application name, click Create
  4. Apply and close

If this does not fix your problem, there may be another configuration error, either with IIS or your application.

like image 4
Karmic Coder Avatar answered Nov 17 '22 02:11

Karmic Coder