section registered as allowDefinition='MachineToApplication' beyond application level

Question

I am getting this error when I create a new folder, and upload files to it. I have an existing site that's built, but I don't want to add this to the site, but rather have it be an application all by itself. Any ideas?

This problem still manifests in VS2012. I have opened a bug report with Microsoft. Anyone experiencing the issue please upvote the bug report https://connect.microsoft.com/VisualStudio/feedback/details/779737/error-allowdefinition-machinetoapplication-beyond-application-level — Eric J., Feb 21 '13 at 22:15

score 33 · Answer 1 · edited May 23 '17 at 10:28

33

This is indeed the first scenario to check. However, the most frustrating scenario in which this error occurs is after a build/publish under a different build configuration (i.e. build under Release, and then trying to build under Debug and getting this error). You should perform Clean operation on the Release mode.

See this answer which points to further details: Error: allowDefinition='MachineToApplication' beyond application level

edited May 23 '17 at 10:28

Community

1
1

answered May 31 '11 at 06:07

Ofer Zelig

17,068
9
59
93

I inherited a project that has the same issue. I don't know if it happens because they have different versions of the config file per environment and it creates the web.config on the fly at compile time or what but if I change build modes I always have to do a Clean Solution in order for the build to be successful. – Nick Bork Feb 06 '14 at 16:23

score 10 · Accepted Answer · answered Nov 11 '09 at 02:29

10

I just had this problem not too long ago. Go into IIS, select the folder you created and go to properties. You will see "application name" greyed out, click the "create" button and save it. You will be able to run your separate application in it.

answered Nov 11 '09 at 02:29

Jeremy Morgan

3,314
23
23

score 1 · Answer 3 · edited Sep 28 '12 at 15:17

1

I just solved such errors after hours of trying, I had the same scenario resolved by simply deleting any back up files your solution may have created moving your application from one version of visual studio to the other and the problem is resolved

edited Sep 28 '12 at 15:17

gnat

6,213
108
53
73

answered Aug 30 '12 at 15:19

ayenco

11
1

score 1 · Answer 4 · answered Jan 15 '13 at 07:35

1

I faced this issue many times. Different solutions worked in different occasions. Following are the solutions.

Create an IIS application for your web site.
Clean the solution and rebuilt again.
Delete the obj folder and rebuilt again.

answered Jan 15 '13 at 07:35

Jomy John

6,308
4
28
32

score 1 · Answer 5 · answered Jan 19 '13 at 13:47

1

Open IIS click right click on the folder and Click "Convert to Application"

answered Jan 19 '13 at 13:47

Atif

278
1
3
16

In 2012 R2, I did not see this option when I right clicked. However, it did show in the Actions pane, when the offending directory was highlighted. – Nathan Hartley Feb 20 '14 at 17:01

score 1 · Answer 6 · answered Jan 15 '14 at 10:20

well i've just resolved this error. just go to your project/website folder (not the published one). search web.config in the whole folder if it found more than once, you know which to delete. otherwise if only one web.config is found. make sure its has the rights to be Read. and the final problem if everything is fine, then make a new project in visual studio and remove all the components then add existing project by right clicking it, build,debug. Voila!!!

score 0 · Answer 7 · answered Mar 11 '13 at 14:52

I had this problem when I moved my application from Window XP to Windows 7. The error is primarily because you did not convert your folder into Application.

The mistake that I was making was, when I selected the folder in IIS and right clicked, I choose "Add Application". This should be "Convert to Application". The resolved my problem.

You want to remove the application from your folder then do the process again and select "Convert to Application".

score 0 · Answer 8 · answered May 16 '13 at 09:11

0

The project folder you are accessing might be the incorrect one Which result in finding two webconfig file for a project. So try to open the correct website.

answered May 16 '13 at 09:11

Salil Gupta

1

score 0 · Answer 9 · answered Jun 28 '13 at 21:13

0

For what it's worth, while in development, I got this same error when using "Open Website" on a project that I created using "New Project". If I instead open with "Open Project", the error goes away.

answered Jun 28 '13 at 21:13

Scott

2,456
3
32
54

score 0 · Answer 10 · answered Sep 30 '13 at 22:29

I just faced this today...Here is my fix and understanding of it.

Right click on your webproject and 'unload' it.
Edit your projects .csproj file (I assume .vs.proj in vb)
Look for 'true'
Change it to false.
Save your .csproj
Right Click on the .csproj and reload it.

Hopefully fixes your problem.

It's my understanding that the error you are getting is 'real', in my case in my web.config was causing the error, because this should actually be set on our server, not by the application.

For some reason, reading Phil Haacks post help me to figure this out...I hope this helps others, I was unable to find a solution that met our needs while looking.

score 0 · Answer 11 · answered Oct 10 '14 at 05:09

If you are getting this error in Visual Studio, Scott Michell has explained it very well.

Basically you are opening the parent folder of the site. In this case web.conf is in subfolder which does not allow certain tags and hence this error. To resolve, simply reopen the site and select the root folder. The error should disappear.

If the error is IIS related, then creating Application for the folder might help.

score 0 · Answer 12 · answered Sep 21 '15 at 12:47

0

Open IIS
Select the Application Pool 3.Select pool where application hosted 4.Click on "Advanced Settings" 5.Change the "Managed Pipe Line Mode" to "Integrated"

answered Sep 21 '15 at 12:47

Shijo Joseph

1
2

score 0 · Answer 13 · edited Apr 13 '16 at 20:13

0

If your web application is running in the SharePoint hive, remember to copy your application to the correct hive (14 or 15) and server (FE or App) and then create the virtual directory in the SharePoint 80 "_layouts" subfolder.

edited Apr 13 '16 at 20:13

sjokkogutten

2,005
2
21
24

answered Apr 13 '16 at 19:25

Dave

1

section registered as allowDefinition='MachineToApplication' beyond application level

13 Answers13

Linked