I am trying to develop my first ASP.Net web application and in my solution I have two projects. A Web Application
and Class Library (Package)
. When I build the ASP.Net 4.5 version of this application I put my Entity Framework 6
entities into a class library, so I am doing that in the ASP.Net 5
version. The problem is when I install EntityFramework.Commands
to the class library I get the error:
The dependency EntityFramework.Command 7.0.0-rc1-final in Project DBEntities does not support framework .NetPlatform, Version = 5.4
My understanding from this SO question is that dotnet5.4
is the new .Net 5 which is supposed to be supported by EF7.
Here is my project.json
file:
{
"version": "1.0.0-*",
"description": "FFInfo.DAL Class Library",
"authors": [ "Mathew" ],
"tags": [ "" ],
"projectUrl": "",
"licenseUrl": "",
"frameworks": {
"dotnet5.4": {
"dependencies": {
"Microsoft.CSharp": "4.0.1-beta-23516",
"System.Collections": "4.0.11-beta-23516",
"System.Linq": "4.0.1-beta-23516",
"System.Runtime": "4.0.21-beta-23516",
"System.Threading": "4.0.11-beta-23516"
}
}
},
"dependencies": {
"EntityFramework.Commands": "7.0.0-rc1-final",
"EntityFramework.MicrosoftSqlServer": "7.0.0-rc1-final"
}
}
Did I install the wrong package, is EF7 changed so much that I am building out the class wrong, or am I missing something in my json file?
EDIT: New project.json file based off suggestions
{
"version": "1.0.0-*",
"description": "FFInfo.DAL Class Library",
"authors": [ "Mathew" ],
"tags": [ "" ],
"projectUrl": "",
"licenseUrl": "",
"frameworks": {
"dotnet5.4": {
"dependencies": {
"Microsoft.AspNet.Hosting.Abstractions": "1.0.0-*",
"Microsoft.Dnx.Runtime": "1.0.0-*",
"Microsoft.Extensions.CommandLineUtils.Sources": {
"version": "1.0.0-*",
"type": "build"
},
"Microsoft.Extensions.PlatformAbstractions": "1.0.0-*",
"System.Console": "4.0.0-*",
"System.IO.FileSystem": "4.0.1-*"
}
},
"netcore50": {
"bin": {
"assembly": "lib\\netcore50\\_._"
}
},
"dependencies": {
"EntityFramework.Commands": "7.0.0-rc1-final",
"EntityFramework.MicrosoftSqlServer": "7.0.0-rc1-final"
}
}
}
I suppose that the reason of your problem have pure technical nature. The announcement declares renaming of dnx451 to net451 and dnxcore50 to dotnet5.4, but one recommend to use such renaming only for class libraries (which you publich on NuGet for example to share with other). If I understand you correctly, that you develop application which uses class libraries and thus you should use
dnxcore50
instead ofdotnet5.4
. Thus you need just rename the string "dotnet5.4" to the string"dnxcore50" in the file
project.json` to fix the problem.Independent from the above recommendation I want to add my understanding of your problem, why you get the error about EntityFramework.Command 7.0.0-rc1-final.
I understand the renaming of frameworks as the step in direction to future changes which plan Microsoft. On the other side all names of frameworks will be interpreted just as different names. I suggest you to compare the information about the dependencies displayed on the page https://www.nuget.org/packages/EntityFramework.Commands/7.0.0-rc1-final from the corresponding information from https://www.nuget.org/packages/EntityFramework.MicrosoftSqlServer/7.0.0-rc1-final. The dependencies of
EntityFramework.MicrosoftSqlServer
(which have no problems with the usage ofdotnet5.4
) looks like on the pictureI marked read the part responsible for
dotnet5.4
. On the other side the dependencies ofEntityFramework.Commands
looks like on the picture below:where there are no ".NETPlatform 5.4" section which corresponds the new name
dotnet5.4
.I suppose that it's a bug in the part of
project.json
ofEntityFramework.Commands
:I suppose that one have to change
netcore50
todotnet5.4
in the lines to support new framework namedotnet5.4
correctly. One chould replace the content of"netcore50"
to the copy fromdnxcore50
(see the lines):Probably one should event increase some version numbers of the dlls referenced above, but you still will be not able to use
EntityFramework.Commands
under"dotnet5.4"
till the new fixed version will be published.UPDATED: I posed the issue to the EntityFramework developer team. I'll include the response from Microsoft on the issue after I'll get it.