Is it possible to use Microsoft.Aspnet.Identity.Core with .net 4.0
up vote
0
down vote
favorite
When I attempt to install Microsoft.Aspnet.Identity.Core version 2.2 with my .net 4.0 project I get the following error:
Could not install package 'Microsoft.AspNet.Identity.Core 2.2.2'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
I understand that it requires .net 4.5+.
Is there an older version of Microsoft.Aspnet.Identity.Core that works with .net 4.0?
More generally, where is the best place to check what version of .net a specific nuget package supports?
asp.net asp.net-mvc-4 asp.net-identity
add a comment |
up vote
0
down vote
favorite
When I attempt to install Microsoft.Aspnet.Identity.Core version 2.2 with my .net 4.0 project I get the following error:
Could not install package 'Microsoft.AspNet.Identity.Core 2.2.2'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
I understand that it requires .net 4.5+.
Is there an older version of Microsoft.Aspnet.Identity.Core that works with .net 4.0?
More generally, where is the best place to check what version of .net a specific nuget package supports?
asp.net asp.net-mvc-4 asp.net-identity
Why don't you upgrade the project target to v4.5 or lastest version?
– Tân Nguyễn
Nov 19 at 17:11
@TânNguyễn there is a cost associated with that, I'm hoping to see if there is another way before I go down that road.
– theycallmemorty
Nov 19 at 17:50
I'm sorry, I don't know how to check the target framework version on Nuget site. But if I were you, I will create a new project for testing, just install one by one to test for compatibility. There are 14 packages at all, so I think the time to test each package is shorter than the time waiting an answer here.
– Tân Nguyễn
Nov 19 at 18:14
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When I attempt to install Microsoft.Aspnet.Identity.Core version 2.2 with my .net 4.0 project I get the following error:
Could not install package 'Microsoft.AspNet.Identity.Core 2.2.2'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
I understand that it requires .net 4.5+.
Is there an older version of Microsoft.Aspnet.Identity.Core that works with .net 4.0?
More generally, where is the best place to check what version of .net a specific nuget package supports?
asp.net asp.net-mvc-4 asp.net-identity
When I attempt to install Microsoft.Aspnet.Identity.Core version 2.2 with my .net 4.0 project I get the following error:
Could not install package 'Microsoft.AspNet.Identity.Core 2.2.2'. You are trying to install this package into a project that targets '.NETFramework,Version=v4.0', but the package does not contain any assembly references or content files that are compatible with that framework. For more information, contact the package author.
I understand that it requires .net 4.5+.
Is there an older version of Microsoft.Aspnet.Identity.Core that works with .net 4.0?
More generally, where is the best place to check what version of .net a specific nuget package supports?
asp.net asp.net-mvc-4 asp.net-identity
asp.net asp.net-mvc-4 asp.net-identity
asked Nov 19 at 17:00
theycallmemorty
7,155114266
7,155114266
Why don't you upgrade the project target to v4.5 or lastest version?
– Tân Nguyễn
Nov 19 at 17:11
@TânNguyễn there is a cost associated with that, I'm hoping to see if there is another way before I go down that road.
– theycallmemorty
Nov 19 at 17:50
I'm sorry, I don't know how to check the target framework version on Nuget site. But if I were you, I will create a new project for testing, just install one by one to test for compatibility. There are 14 packages at all, so I think the time to test each package is shorter than the time waiting an answer here.
– Tân Nguyễn
Nov 19 at 18:14
add a comment |
Why don't you upgrade the project target to v4.5 or lastest version?
– Tân Nguyễn
Nov 19 at 17:11
@TânNguyễn there is a cost associated with that, I'm hoping to see if there is another way before I go down that road.
– theycallmemorty
Nov 19 at 17:50
I'm sorry, I don't know how to check the target framework version on Nuget site. But if I were you, I will create a new project for testing, just install one by one to test for compatibility. There are 14 packages at all, so I think the time to test each package is shorter than the time waiting an answer here.
– Tân Nguyễn
Nov 19 at 18:14
Why don't you upgrade the project target to v4.5 or lastest version?
– Tân Nguyễn
Nov 19 at 17:11
Why don't you upgrade the project target to v4.5 or lastest version?
– Tân Nguyễn
Nov 19 at 17:11
@TânNguyễn there is a cost associated with that, I'm hoping to see if there is another way before I go down that road.
– theycallmemorty
Nov 19 at 17:50
@TânNguyễn there is a cost associated with that, I'm hoping to see if there is another way before I go down that road.
– theycallmemorty
Nov 19 at 17:50
I'm sorry, I don't know how to check the target framework version on Nuget site. But if I were you, I will create a new project for testing, just install one by one to test for compatibility. There are 14 packages at all, so I think the time to test each package is shorter than the time waiting an answer here.
– Tân Nguyễn
Nov 19 at 18:14
I'm sorry, I don't know how to check the target framework version on Nuget site. But if I were you, I will create a new project for testing, just install one by one to test for compatibility. There are 14 packages at all, so I think the time to test each package is shorter than the time waiting an answer here.
– Tân Nguyễn
Nov 19 at 18:14
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53379418%2fis-it-possible-to-use-microsoft-aspnet-identity-core-with-net-4-0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Why don't you upgrade the project target to v4.5 or lastest version?
– Tân Nguyễn
Nov 19 at 17:11
@TânNguyễn there is a cost associated with that, I'm hoping to see if there is another way before I go down that road.
– theycallmemorty
Nov 19 at 17:50
I'm sorry, I don't know how to check the target framework version on Nuget site. But if I were you, I will create a new project for testing, just install one by one to test for compatibility. There are 14 packages at all, so I think the time to test each package is shorter than the time waiting an answer here.
– Tân Nguyễn
Nov 19 at 18:14