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.
Currently if I try to link any Portable Library which is not "Profile1" to a MonoTouch library or appication project, then I get the warning reported within the UI that the PCL is incompatible - e.g.:
- "Incompatible Target Framework (.NETPortable 4.0 Profile4 Profile)"
or (in my case):
- "Incompatible Target Framework (.NETPortable 4.0 Profile104 Profile)"
At build time this then results in the MonoTouch project refusing to build - it simply doesn't pull in the namespaces from the portable class library project.
I've tried tweaking the MonoDevelop source, but am having problems building/testing on the Mac (I'm trying!). I think the problem is to do with: https://github.com/mono/monodevelop/blob/master/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/PortableDotNetProject.cs
If you need some sample Profile104 projects then see the vnext branch of https://github.com/slodge/MvvmCross/ but note that you also need this patch (http://slodge.blogspot.co.uk/2012/09/a-helper-on-getting-monotouch-building.html)
Is there any way I can get the additional profiles (especially Profile104) supported?
Note: I don't need "proper PCL support" - I just need MonoDevelop and MonoTouch to try to build the relevant projects against MonoTouch.
There's no reason I can think of to prevent other profiles from being built since our current support is basically a giant hack. Should we just remove the build time restriction to Profile1 projects so this scenario is supported too?
Please do :)
Also, is there any way this can be done within a hack - i.e. is there any way I can just edit some .targets or other files within an installation to make it work?
You can reference the compiled dll directly, instead of using a project reference.
But I use automated refactoring a lot - so I really want to use proper project linking.
I'm now supporting this using the cool Conditional Build file tweak suggested by JonPepper - see http://slodge.blogspot.co.uk/2012/10/a-temporary-solution-for-profile1-only.html
P.S. I am trying to log these PCLs error to help make MT and MD better - I'm not just trying to be a pain - honest!
fixed in git master
*** Bug 260998 has been marked as a duplicate of this bug. ***
Seen from the domain http://volichat.com
Page where seen: http://volichat.com/random-chat-rooms
Marked for reference. Resolved as fixed @bugzilla.