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
GitHub or Developer Community 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.
If a project in solution created with VisualStudio is configured to use the .NET Client profile, MonoDevelop should map it to the standard Mono 4.0 one (or alternatively provide the 'client' profile)
Mapping to "full" .NET would be incorrect.
MD supports framework profiles - it works on .NET - but Mono doesn't have this one.
I agree with Marek that this would be a nice feature. If .NET Client Profile is not installed, MonoDevelop should fallback on the full framework.
As it is right now, for a .NET Client Profile assembly, I need to have a separate project file when building the assembly on Mac or Linux.
On the other hand, if MonoDevelop would fallback on the full .NET Framework when the client profile is not installed, I would be able to reuse the same project file on all platforms, making cross-platform maintenance considerably easier.
Probably this could be implemented as a generic solution to fall back to the "full" framework, when loading a project that targets an unknown profile of a known framework.
It's not trivial, we can't just fall back at load time, because it would then be saved out with the full framework. We need to create some kind of placeholder framework definition on demand and use that.
It should definitely emit some kid of warning - not sure whether it should be at build time, at load time, in the solution tree, etc
*** Bug 9906 has been marked as a duplicate of this bug. ***
4.0 client profile added in mono/c25957f1a42acf08eeaa94ae4a11806c8f0434a3
*** Bug 19704 has been marked as a duplicate of this bug. ***