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.
Answers:
Thank you for visiting the Q&A section on Magenaut. Please note that all the answers may not help you solve the issue immediately. So please treat them as advisements. If you found the post helpful (or not), leave a comment & I’ll get back to you as soon as possible.
Method 1
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.
Method 2
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.
Method 3
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
- properties
- if transformed (apply to all configurations)
- properties
- Build Action: None
- Copy to Output directory: Do not copy
- properties
Method 4
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:
- Open IIS and navigate to the appropriate folder
- Right-click on the folder, select properties
- Under Application Settings, and beside Application name, click Create
- Apply and close
If this does not fix your problem, there may be another configuration error, either with IIS or your application.
Method 5
In IIS, go to the folder that the app runs under, right click it, go to properties.
On the Directory tab, look for “Application settings”. Click the create button.
All methods was sourced from stackoverflow.com or stackexchange.com, is licensed under cc by-sa 2.5, cc by-sa 3.0 and cc by-sa 4.0