Bug 16757 - XS does not cleanly roundtrip VS2013 sln files
Summary: XS does not cleanly roundtrip VS2013 sln files
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Visual Studio Compatibility ()
Version: unspecified
Hardware: PC Mac OS
: --- normal
Target Milestone: Roslyn
Assignee: Bugzilla
Depends on:
Reported: 2013-12-12 15:41 UTC by Mikayla Hutchinson [MSFT]
Modified: 2015-11-27 06:53 UTC (History)
5 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 Mikayla Hutchinson [MSFT] 2013-12-12 15:41:08 UTC
XS does not cleanly roundtrip sln files created by VS2013 since it 1:1 maps the header comment and the format version.
Comment 1 Lluis Sanchez 2015-04-09 14:06:44 UTC
It will be fixed in XS 6.0.
Comment 2 Akhilesh kumar 2015-11-27 06:53:06 UTC
Hi Lluis,

I am trying to verify this issue but I am not sure what I have to check to
verify this issue.

I have tried below steps:
1. Created Android application in VS
2. Now open same solution in XS with .sln file of the project

I am successfully able to build app in both XS(Stable and Roslyn) which was created in VS.

Could you please provide me a small test case or test steps? So that I can
verify this issue with Roslyn(6.0.x) build.