Visual Studio 2015: an equivalent project is already in the project collection

When you try to add existing projects to a Visual Studio 2015 solution, VS gives the following error message. I confirmed that I have not yet added a link to the project that I am trying to add. Are there any settings or a cache file that I need to delete or clear somewhere?

An equivalent project (a project with the same global properties and a version of tools) is already present in the project collection, and path is "D: \ My \ Path \ MyProject.csproj". To load the equivalent into this project collection, first upload this project.

+10
visual-studio visual-studio-2015 solution csproj
source share
11 answers

Not sure if this could happen, but it seems that adding dependent projects in the reverse order allowed me to add all my projects back. Therefore, first add all the child projects, and then add the parent projects on which they depend. The order that they added back to the solution may have caused peeling.

0
source share

Just "Clean Solution" worked for me.

+13
source share

This happened to me after I was busy with project files using an external editor. I was able to solve the problem by exiting VS and also killing VsHub.exe.

It seems that VsHub.exe caches part of the project and gets confused or not synchronized with VS.

+6
source share

I called this via code.

This fixed it for me:

Microsoft.Build.Evaluation.ProjectCollection.GlobalProjectCollection.LoadedProjects.FirstOrDefault(d => d.FullPath == projectFilePath) ?? Microsoft.Build.Evaluation.Project.FromFile(projectFilePath, new ProjectOptions()) 
+1
source share

It happened to me after the blues screen. It seemed to fix this:

  • Enter the VS2015 cmd prompt.
  • Run "devenv / resetuserdata"
0
source share

Rebooting Windows fixed this issue for me. After rebooting, Visual Studio does not display such a strange error message.

0
source share

In my case, I saw this error when I did the following:

I enabled / imported 3.vcxproj inside 2.vcxproj and 2.vcxproj was included in 1.vcxproj.

The path to 3.vcxproj inside 2.vcxproj was wrong and this gave me the error above.

The path is fixed and the error has disappeared. Not sure how filters are related.

0
source share

I often get this when switching branches using git. I found that if I “touch ZFSin.vcxproj.filters” - (project filter file), I can then right-click on the project that failed to load and “reload”. Neither Clean project, nor reboot VS2017. (Touch is a command that simply updates the timestamps in a file).

0
source share

I had this problem when the solution used environment variables in project paths and other paths. I think he expected to find %var1%\proj.vcxproj and %var2%\proj.vcxproj , but %var1% and %var2% had the same value.

0
source share

In my case, the project only had the x64 platform configuration, not the Win32 platform configuration. Oddly enough, the solution had a Win32 platform configuration, and for some reason Win32 was the current platform configuration.

After switching to x64, I was able to download the project again without any problems. I also deleted the configuration of the Win32 platform just to be sure.

0
source share

All Articles