Skip to content
This repository was archived by the owner on Oct 19, 2022. It is now read-only.

Conversation

@JSkimming
Copy link
Contributor

It is possible to build ASP.NET Core applications that target the .NET 4.5 framework. Since this package only targets .NET Standard 1.6 it cannot be imported into ASP.NET Core projects that do so. This results in the following build error:

error: Package Stormpath.AspNetCore 0.3.2 is not compatible with net461 (.NETFramework,Version=v4.6.1). Package Stormpath.AspNetCore 0.3.2 supports: netstandard1.6 (.NETStandard,Version=v1.6)
error: One or more packages are incompatible with .NETFramework,Version=v4.6.1.

This is a very simple change and is risk free, while broadening the appeal of solution.

It is possible to build ASP.NET Core applications that target the .NET
4.5 framework. Because this package only targets .NET Standard 1.6 it
cannot be imported into ASP.NET Core projects that do so. This is a very
simple change and is risk free, while broadening the appeal of solution.
@nbarbettini
Copy link
Member

Hey @JSkimming, thanks for the PR!

I didn't realize anyone was building ASP.NET Core applications on desktop .NET. I'm curious, what's the reasoning there?

@JSkimming
Copy link
Contributor Author

Hi @nbarbettini, there's several reasons, we have two.

  1. Many third party packages have yet to be upgraded, therefore if we want to use then, we need to target .NET 4.5 ( desktop as you describe it)
  2. We have some of our own legacy libraries for which we have yet to upgrade. (It's almost the same as pint 1)

So we want to use the latest ASP.NET in our new applications, but still need to target .NET 4.5.

@nbarbettini nbarbettini merged commit cbffb45 into stormpath:master Jun 30, 2016
@JSkimming JSkimming deleted the target-dotnet451 branch June 30, 2016 22:48
@JSkimming
Copy link
Contributor Author

👍 :shipit:

@JSkimming
Copy link
Contributor Author

Hi @nbarbettini,

Can you push an update to NuGet with this change? A minor (0.4.0) or patch increment (0.3.3) would seem appropriate. It's not really changing the API.

@nbarbettini
Copy link
Member

Sorry for the delay @JSkimming, yesterday was a holiday here in the US. 🎉

Published as v0.3.3: https://www.nuget.org/packages/Stormpath.AspNetCore/0.3.3

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants