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 1427 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
VisualStudio appears to make no distinction between the two when opening a solution while MonoDevelop will mark the project using the 'Debug|x86' configuration as not built if the 'Debug' configuration is active. The same applies to Release and other configuration.
I'm not sure what you mean. Can you give a more specific example with a sample project?
Created attachment 689 [details]
The attached solution demonstrates the issue. Note that after opening it in MonoDevelop the WindowsFormsApplication1 project will be disabled.
There are 6 configurations in the solution:
"Debug" aka "Debug|Any CPU"
"Release" aka "Release|Any CPU"
MonoDevelop defaults to using the "Debug" configuration as the active configuration. VS defaults to the "Debug|Mixed Platforms" configuration.
The default solution configuration isn't specified anywhere, so MD's using the first configuration. Apparently VS is "guessing" a better one.
IMO, automatically creating and updating "Mixed Platforms" configurations would be good. It would solve this problem: http://bugzilla.xamarin.com/show_bug.cgi?id=1309#c6
Interestingly, the VS solution picker combo box only seems to show the configuration names "Release" and "Debug", and doesn't show the platforms.
It would appear that VisualStudio doesn't take platform into account when determining whether a project is eligible for compilation. I think the x86 is relevant only in managed C++ projects anyway, so MonoDevelop should definitely ignore the platform in situations like this.
Marek, that's incorrect. VS handles platforms and solution configurations exactly the same way MD does, it just chooses a different solution configuration by default.