Bug 13283 - Make MSBuild project handlers more flexible
Summary: Make MSBuild project handlers more flexible
Status: RESOLVED FIXED
Alias: None
Product: Xamarin Studio
Classification: Desktop
Component: Project Model ()
Version: Trunk
Hardware: PC Mac OS
: --- normal
Target Milestone: master
Assignee: Lluis Sanchez
URL:
Depends on:
Blocks:
 
Reported: 2013-07-16 20:54 UTC by Mikayla Hutchinson [MSFT]
Modified: 2017-09-26 12:56 UTC (History)
2 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] 2013-07-16 20:54:40 UTC
The MSBuild project handler system is currently very inflexible. It's possible to subclass MSBuildProjectHandler but there's no way to override it and get visibility into the serialization system - pretty much all you can do is to reimplement it.

This would be really nice since it would allow moving some of the serialization hacks out of the project system and into specialized handlers. But it would be even better as part of a comprehensive overhaul of MSBuild support - e.g direct access to the MSBuild document and the MSBuild evaluator, support for flavor GUIDs on non DotNetProjects, etc, support composing flavor GUIDs instead of brokenly mapping them to a single inheritance system.
Comment 1 Marius Ungureanu 2017-09-26 12:56:49 UTC
Marking as fixed. The old code is gone, the new model has serialization capabilities exposed.