support dotnet core
See original GitHub issuePlease add support for .net core!
Here are the errors you get if you attempt to add this package to a dotnet core app
Errors in Project.xproj
Package System.Spatial 5.6.4 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package System.Spatial 5.6.4 supports:
- net40 (.NETFramework,Version=v4.0)
- portable-net40+sl5+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile328)
- portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
- sl4 (Silverlight,Version=v4.0)
Package Microsoft.Data.Services.Client 5.6.4 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package Microsoft.Data.Services.Client 5.6.4 supports:
- net40 (.NETFramework,Version=v4.0)
- portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
- sl4 (Silverlight,Version=v4.0)
Package Microsoft.Data.OData 5.6.4 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package Microsoft.Data.OData 5.6.4 supports:
- net40 (.NETFramework,Version=v4.0)
- portable-net40+sl5+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile328)
- portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
- sl4 (Silverlight,Version=v4.0)
Package Microsoft.Data.Edm 5.6.4 is not compatible with netcoreapp1.0 (.NETCoreApp,Version=v1.0). Package Microsoft.Data.Edm 5.6.4 supports:
- net40 (.NETFramework,Version=v4.0)
- portable-net40+sl5+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile328)
- portable-net45+win8+wp8+wpa81 (.NETPortable,Version=v0.0,Profile=Profile259)
- sl4 (Silverlight,Version=v4.0)
One or more packages are incompatible with .NETCoreApp,Version=v1.0.
Maybe this project needs to be split into separate packages for blob/queue/table functionality to aid the process. It seems unfortunate that I only want to work with queues and blobs and I am failing on dependencies like System.Spatial, Microsoft.Data.Edm, etc…
Issue Analytics
- State:
- Created 7 years ago
- Reactions:2
- Comments:12 (3 by maintainers)
Top Results From Across the Web
.NET and .NET Core official support policy
Long Term Support (LTS). LTS releases are supported for three years after the initial release. · Standard Term Support (STS). STS releases are...
Read more >Microsoft .NET - endoflife.date
NET Core 3.1, these releases will happen every November and every other release will be LTS. LTS releases are supported for three years...
Read more >Microsoft Announces End of Support Date for .NET Core 3.1
Microsoft released .NET Core 3.1 in December 2019, and it is a long-term supported (LTS) release, which explains why it's getting three years...
Read more >Microsoft to End Support for .NET Core 3.1 in December 2022
The long-term-support (LTS) version 3.1 of Microsoft .NET Core Framework is slated to go out of support on December 13th, 2022.
Read more >microsoft-support.md - dotnet/core
Support is provided for: .NET SDK, .NET Runtimes, ASP.NET Core, and EF Core. Support has two key benefits: Patches are provided (for free)...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
gregjhogan They do … it’s just some of the supporting packages that don’t explicitly support the
netcoreapp1.0
TFM. Those packages do work. You need to add animports
statement to your TFM …WRT splitting the lib, they’ve already said ‘no’ to that request: https://github.com/Azure/azure-storage-net/issues/97#issuecomment-191012939
[EDIT] and make sure you’re using
7.1.3-preview
for .NET Core apps. https://www.nuget.org/packages/WindowsAzure.Storage/7.1.3-previewSome good news regarding netstandard friendly OData package:
As a result of our collaboration with CoreFx team, we have updated our library (v8.1) to use the latest Netstandard friendly ODataLib packages to eliminate the need to import or add additional TFs.
Thanks for your patience and help while we are working on the remaining issues with ODataLib.
-Elham