Please help. I had originally started a thread here: http://social.msdn.microsoft.com/Forums/en-US/6cc7147c-c00a-4f74-9482-ffb1c82e93c5/howto-get-vs2013update2-to-not-look-in-sub-folders-when-compiling-mvc-apps?forum=vssetup
The support folks said this would be best answered here, for which I moved in the original post and some follow up posts.
I have a MVC app, that before VS2013/Update-2 would NOT look into sub folders when building. But since Update 2, it now looks into sub folders when building, and if it finds files like "web.config" in a backup folder, that was not attached to the project/solution, it throws an error like this:
1>C:\Devel\MyMvcApp\backup-folder-not-attached-to-the-project\web.config(9): error ASPCONFIG: Section or group name 'entityFramework' is already defined. Updates to this may only occur at the configuration level where it is defined.
I am running VS2013/Update-2 in safe mode.
======================
I have more news regarding this issue.
Also since Update 2, the VS2013 compiler is looking for CSHTML files in folder NOT-ATTACHED to the project, where before Update 2, it did not. In this case, it seems to be because the sub-folder have "View" in it like this:
1>c:\Devel\MyMvcApp\backup-folder-not-attached-to-the-project\Views\Home\MyView.cshtml(124): error CS1729: 'MyNamespace.MyClass' does not contain a constructor that takes 5 arguments
I have other folders with CSHTML files like that one above, where the Update 2 is not seeing them. The only difference is that one above is under "backup-folder-not-attached-to-the-project\Views" and the others are not.
=============================
I have more information. I tried renaming my backup\view to be backup\views/bak and VS2013\Update-2 still found it, as if it were attached to the project, and tried to compile it. This implies, it is still seeing the other CSHTML files I have in backup-sub folder, but just isn't getting any errors.
This is nutty. I need to have a backup of my app under the same project folder so we can manage our deployments. Why is VS2013/Update-2 seeing them? How can I make this stop?