Bug 36815 - a project with the same global properties is already present
Summary: a project with the same global properties is already present
Status: RESOLVED DUPLICATE of bug 38071
Alias: None
Product: Visual Studio Extensions
Classification: Xamarin
Component: General ()
Version: 4.0.0 (C6)
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2015-12-10 10:32 UTC by softlion
Modified: 2016-01-26 20:23 UTC (History)
4 users (show)

Is this bug a regression?: ---
Last known good build:

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description softlion 2015-12-10 10:32:20 UTC
When unloading then reloading an ios app project, visual studio 2015 complains that is already exists

Microsoft Visual Studio
An equivalent project (a project with the same global properties and tools version) is already present in the project collection, with the path "C:\Users\me\Repos\ac\Ac.Touch\Ac.Touch.csproj". To load an equivalent into this project collection, unload this project first.
Comment 1 Brendan Zagaeski (Xamarin Team, assistant) 2016-01-26 20:23:00 UTC
Thanks for the report.

I was able to replicate this problem, so I gathered detailed statistics on the behavior from several different versions of XamarinVS and used those as the starting point for a new bug report on the issue.

I will accordingly mark this bug as a duplicate of that new bug.

*** This bug has been marked as a duplicate of bug 38071 ***