locked
PCL Profile151 (.NET 4.6): Is it possible on Mac? RRS feed

  • Question

  • User117070 posted

    Hi

    Is it possible to use PCLs with .NET 4.6 target on Mac? Recently, one of our PCL's target profile was changed to 151, and I get a warning by the references saying "Framework not installed: .NETPortable,Version=v4.6,Profile=Profile151". Have checked the /Library/Frameworks/Mono.framework/Versions/4.0.3/lib/mono/xbuild-frameworks/.NETPortable folder (so my Mono version is 4.0.3), and it really does not contain v4.6 folder, only v4.0 and v4.5 So I suppose Mono 4.0.3 does not support PCLs with .NET 4.6 target yet. If so, I could not find any future plans for this. Do anyone has information about this? Is there a way to hack this? Eg is it possible to install Profile151 into /Library/Frameworks/Mono.framework/External? Would copying the Microsoft dll-s from a Windows machine's PCL Profile folder do the trick?

    Thanks and regards, Norbert Virth

    Monday, August 31, 2015 10:07 AM

Answers

  • User35201 posted

    I believe upcoming mono's may add support for 4.6. I currently don't know the status. Have you tried the Alpha channel? Mono 4.2 appears to be offered there as of the 31st.

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Tuesday, September 1, 2015 3:40 PM

All replies

  • User35201 posted

    I believe upcoming mono's may add support for 4.6. I currently don't know the status. Have you tried the Alpha channel? Mono 4.2 appears to be offered there as of the 31st.

    • Marked as answer by Anonymous Thursday, June 3, 2021 12:00 AM
    Tuesday, September 1, 2015 3:40 PM
  • User117070 posted

    Hi @ChrisHamons

    Yes, I've tried the alpha channel, still no "v4.6" folder inside of the ".NETPortable" :(

    Tuesday, September 1, 2015 5:28 PM
  • User28 posted

    The versioning is confusing, PCL 4.6 doesn't actually have anything to do with .NET 4.6, it enables .NET 4.5.1 (which is a pretty minimal API bump from 4.5) and Windows 8.1 Store/Phone. Is there a particular reason you're using the PCL 4.6 profiles?

    We're currently working on adding .NET 4.6 APIs and PCL5 support, which enables .NET 4.6 and .NET Core. Unfortunately PCL5 involves fitting lots of complex parts together (including NuGet 3) so it'll take a while.

    Thursday, November 5, 2015 12:41 AM
  • User117070 posted

    This issue of mine has been solved in the meantime. I was mostly just a dispatcher in this, the project involved is multiplatform; another teammate (on another platform) started these transformations, I can't now remember why PCL 4.6 came into picture :) Even the solution of the problem wasn't mine, so I don't know how it got fixed; but somehow it got.

    I asked this question in the Cross Platform forum as well, if somebody would be interesting in the future: https://forums.xamarin.com/discussion/comment/162673#Comment_162673

    Thursday, November 5, 2015 6:43 PM
  • User239753 posted

    @mhutch said: We're currently working on adding .NET 4.6 APIs and PCL5 support, which enables .NET 4.6 and .NET Core. Unfortunately PCL5 involves fitting lots of complex parts together (including NuGet 3) so it'll take a while.

    Hows the progress of this going? Any estimate time of completion.

    Thank you

    Friday, February 3, 2017 9:39 AM
  • User35201 posted

    I'll let @mhutch answer in detail when they get a chance but I know XS 6.2 has NuGet 3.

    So at least part of that is done if you swap to the builds in Alpha/Beta channel (Cycle 9).

    Friday, February 3, 2017 4:07 PM
  • User28 posted

    @cfl777 we shipped this a while back, it's in current stable

    Friday, February 3, 2017 6:58 PM