Bug 13453 - Xamarin forces csproj platform from AnyCPU to x86 upon load, and ignores attempts to change it back
Summary: Xamarin forces csproj platform from AnyCPU to x86 upon load, and ignores atte...
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: General ()
Version: 4.0.10
Hardware: PC Windows
: --- normal
Target Milestone: master
Assignee: Bugzilla
Depends on:
Reported: 2013-07-25 00:52 UTC by Matt Hargett
Modified: 2016-10-18 15:27 UTC (History)
3 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 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 Matt Hargett 2013-07-25 00:52:27 UTC
-load MonoGame's Xamarin solution in 4.0.10
-compile the WindowsGL project
-do a git diff and notice that somehow AnyCPU has changed to x86 in the MonoGame.Framework.WindowsGL.csproj
-open the WindowsGL project's options, change x86 back to AnyCPU, click OK, File->Save All
-do a git diff and notice it didn't change back
Comment 1 Mikayla Hutchinson [MSFT] 2013-07-25 11:43:10 UTC
What is the diff?
Comment 2 iain 2016-10-18 15:27:45 UTC
We have not received the requested information. If you are still experiencing this issue please provide all the requested information and re-open the bug report. Thanks