Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
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
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.
Monodevelop does not support client profiles (which could easily be supported by adding more runtime.xml files defining which assemblies make up a particular runtime).
Client profiles are (as far as I understand) just a filter to the IDE as to which assemblies are available.
Absent the support for client profiles MD should behave by ingoring the client profile property, but instead the FrameworkMoniker.cs (not exact name - sorry not in front of me at this time) is using the client profile value to compare.
Again - logic should be - in the absence of client profile support (easily done by adding more runtime.xml files) we should be ignoring client profiles altogether.
Current behaviour is that 99% of all code in codeplex that has come from VS2010 (which stamps projects as ClientProfile - a subset of Dot.Net 4.0 with only things found on non-server environments) will fail to load into MD.
The following makes sense to me - Either support it, or ignore the property.
For reference: http://msdn.microsoft.com/en-us/library/bb398202.aspx
Its late and I have not included actual property names from the xml in .csproj files... sorry.
MD supports framework profiles, there just aren't any installed.