Bug 20827 - Add .net 4.5.1 profile
Summary: Add .net 4.5.1 profile
Alias: None
Product: Tools
Classification: Mono
Component: xbuild ()
Version: unspecified
Hardware: All All
: --- normal
Target Milestone: ---
Assignee: Marek Safar
Depends on:
Reported: 2014-06-23 17:34 UTC by Dylan Borg
Modified: 2014-06-25 11:31 UTC (History)
4 users (show)

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 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.

Related Links:

Description Dylan Borg 2014-06-23 17:34:23 UTC
In order to support ASP.NET vnext components like EF 7 a .net 4.5.1 profile must be added just for versioning purposes.
Comment 1 Marek Safar 2014-06-24 03:54:41 UTC
What is not working from 4.5.1 profile for you? 4.5.1 is same as our 4.5 profile.
Comment 2 Dylan Borg 2014-06-24 04:56:10 UTC
I do know that they are the same, But NuGet does not. I.e if a package says that it wants net451 it will not work on mono as mono advertises up to net45 but really has net451.
Comment 3 Marek Safar 2014-06-24 05:11:53 UTC
How can I reproduce your "will not work on mono" ? I tried with XS/MD to add 4.5.1 packages and it works with master and mono 3.6
Comment 4 Dylan Borg 2014-06-24 05:25:49 UTC
My case involves ASP.NET vNext. They may be using standard nuget code and not the modified code in XS/MD. The packages will work if forced in, however in ASP.NET vNext you cannot force stuff without hacking the packages.
Comment 5 Marek Safar 2014-06-24 07:36:56 UTC
XS/MD does not really have any modification in this area and it works for me with nuget.org, unless you provide steps to reproduce the issue there is not much we can do.
Comment 6 Dylan Borg 2014-06-24 08:51:30 UTC
If you you use the sqlite packages with asp.net vnext on mono, the sqlite packages will not be brought into the project as they expect .net 4.5.1 to be available as a profile. What is needed is to have a /usr/lib/mono/4.5.1 folder that links to /usr/lib/mono/4.5 and support in the runtime and xbuild to support 4.5.1 functionality as a profile itself. If nothing can be done convince Microsoft to target .net 4.5 instead. I tried but they said its something that mono must fix.
Comment 7 Mikayla Hutchinson [MSFT] 2014-06-24 12:00:21 UTC
I think you may be confusing runtime profiles and MSBuild profiles.
Comment 8 Dylan Borg 2014-06-24 15:17:40 UTC
It may be. I have filed an issue for ASP.NET vNext maybe they redirect make 4.5.1 and 4.5 equal for teh mono case while resolving assemblies.
Comment 9 Mikayla Hutchinson [MSFT] 2014-06-24 18:01:47 UTC
I imagine what you want is one of these:

Technically those should point to reference assemblies.

.NET 4.5.1 actually replaces the .NET 4.5 *runtime* assemblies, so MS keeps "reference assemblies" with the old API that can be used at build time.
Comment 10 Dylan Borg 2014-06-25 08:00:58 UTC
I agree on the xbuild-framework for 4.5.1
Comment 11 Marek Safar 2014-06-25 11:31:36 UTC
Fixed in master