Bug 1289 - More robust project format handling
Summary: More robust project format handling
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: PC Windows
: Low enhancement
Target Milestone: ---
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2011-10-05 20:17 UTC by Mikayla Hutchinson [MSFT]
Modified: 2015-07-03 12:51 UTC (History)
3 users (show)

Tags:
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:
Status:
RESOLVED FIXED

Description Mikayla Hutchinson [MSFT] 2011-10-05 20:17:24 UTC
If we're going to continue to support multiple project formats, we need more robust project format handling.

Currently we support VS2005, VS2008, VS2010, MD1. However, they're all supported via common serialization systems which aren't robust enough to deal with all the differences between the formats. And we implicitly support a lot of stuff by assuming that the serialization system can handle it, but often that isn't really the case. It's also currently impossible for project types to directly influence how they are serialized to/from MSBuild, they can only make data available to the serializer in an abstract way. 

Each project type should have to explicitly support
* each format it can load from
* each pair of formats it can migrate between
* each format it can save to
and each of these should have a handler specific to the project type.

In most cases these would be simple subclasses of default handlers, which would use generic serialization systems. But they should be explicitly opt-in, and it should be possible to override their low-level behaviours.
Comment 1 Marius Ungureanu 2013-11-23 10:34:23 UTC
Isn't this fixed now?
Comment 2 Mikayla Hutchinson [MSFT] 2013-11-23 15:18:54 UTC
Nope.
Comment 3 Lluis Sanchez 2015-07-03 12:51:02 UTC
The new project model provides all kind of hooks to customize the serialization of projects.