Bug 14328 - Solutions in Workspace which contain shared project double up on edit
Summary: Solutions in Workspace which contain shared project double up on edit
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Lluis Sanchez
Depends on:
Reported: 2013-08-29 12:34 UTC by Ian
Modified: 2017-01-11 18:01 UTC (History)
2 users (show)

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

doubled up solutions in workspace (111.45 KB, image/png)
2013-08-29 12:34 UTC, Ian

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 or GitHub 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 Ian 2013-08-29 12:34:12 UTC
Created attachment 4745 [details]
doubled up solutions in workspace

Create a workspace
Add solutions
create a common .csproj
have all solutions refer to it, "Common.csproj"
Make a structural change (ad a reference for example) to any project
X Studio doubles up everything as  per screen shot
Comment 1 Jatin 2015-12-03 05:05:55 UTC
I have checked this issue with stable builds but unable to reproduce this issue at my end. 

Please have a look at my screencast: http://www.screencast.com/t/3yJ2l4Sd 

Please confirm that is this correct way to verify this issue or need to perform anything else to check this issue?
Comment 2 Lluis Sanchez 2017-01-11 18:01:51 UTC