Bug 1427 - MD should default to "Debug|Mixed Platforms" configuration if it exists
Summary: MD should default to "Debug|Mixed Platforms" configuration if it exists
Status: CONFIRMED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Visual Studio Compatibility ()
Version: 2.8
Hardware: PC All
: Low enhancement
Target Milestone: ---
Assignee: Bugzilla
URL:
Depends on:
Blocks:
 
Reported: 2011-10-11 16:51 UTC by Marek Habersack
Modified: 2017-08-04 22:30 UTC (History)
4 users (show)

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


Attachments
WindowsFormsApplication1.tar.bz2 (5.81 KB, application/octet-stream)
2011-10-13 10:43 UTC, Marek Habersack
Details


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 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 original description:

  • Export the original title and description: Developer Community HTML or GitHub Markdown
  • Copy the title and description into the new report. Adjust them to be up-to-date if needed.
  • Add your new information.

In special cases on GitHub you might also want the comments: GitHub Markdown with public comments

Related Links:
Status:
CONFIRMED

Description Marek Habersack 2011-10-11 16:51:54 UTC
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.
Comment 1 Lluis Sanchez 2011-10-13 06:04:58 UTC
I'm not sure what you mean. Can you give a more specific example with a sample project?
Comment 2 Marek Habersack 2011-10-13 10:43:40 UTC
Created attachment 689 [details]
WindowsFormsApplication1.tar.bz2

The attached solution demonstrates the issue. Note that after opening it in MonoDevelop the WindowsFormsApplication1 project will be disabled.
Comment 3 Mikayla Hutchinson [MSFT] 2011-10-13 10:59:28 UTC
There are 6 configurations in the solution:
"Debug" aka "Debug|Any CPU"
"Debug|Mixed Platforms"
"Debug|x86"
"Release" aka "Release|Any CPU"
"Release|Mixed Platforms"
"Release|x86"

MonoDevelop defaults to using the "Debug" configuration as the active configuration. VS defaults to the "Debug|Mixed Platforms" configuration.
Comment 4 Mikayla Hutchinson [MSFT] 2011-10-13 11:04:46 UTC
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
Comment 5 Mikayla Hutchinson [MSFT] 2011-10-13 11:20:34 UTC
Interestingly, the VS solution picker combo box only seems to show the configuration names "Release" and "Debug", and doesn't show  the platforms.
Comment 6 Marek Habersack 2011-10-13 15:34:50 UTC
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.
Comment 7 Mikayla Hutchinson [MSFT] 2011-10-13 15:45:48 UTC
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.