Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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 for Bug 14056 on
Developer Community or GitHub if you have new
information to add and do not yet see a matching new report.
If the latest results still closely match this report, you can use the
In special cases on GitHub you might also want the comments:
GitHub Markdown with public comments
After upgrading to the newest studio, when ever I try to open a Workspace with multiple solutions, I get an initifine number of dialogs appear. See image.
The only way to cancel is to force the Studio to stop via Activity Monitor. This bug has rendered Studio no longer working for any workspace.
Created attachment 4656 [details]
I found the cause.
All my solutions use a common Common.csproj project, this project has components. Components are not project specific, so when the workspace opens, it for some reason tries to edit Common.csproj, so that causes other solutions in the Workspace to say the error in the attached image.
Projects should not share the Component of the app they are in as if they are in another app too, it fails with this error.
For now I manually pulled the .dlls out to a special folder then manually pointed the Component there and it now works.
Created attachment 4737 [details]
What solution to bug looks like
So essentially the problem is that you load a workspace with the same project included twice in the same solution. One project "fixes" itself on load because it has incorrect solution-dependent values, and saves itself. This causes the other instance of the project to to reload, and it now has incorrect values, fixes itself, etc.
Not sure of an easy general fix for this.
a workspace has many solutions, each is a different app.
However, each solution contains a set of common projects (themes, localization,
It is when there is a shared common.csproj (not .sln) that there is an issue.