netcore support
See original GitHub issueSteps to reproduce
- create a dotnet project
dotnet new console -n test
- enter the project
cd test
- add nuget package
dotnet add package DotSpatial.Projections --version 2.0.0-rc1
- exec build
dotnet build
DotSpatial version: 2c2302778278e61a01143b1ea6c8126a3ae8198e
Expected behaviour
compatibility on net standard
Actual behaviour
warn : Package 'DotSpatial.Projections 2.0.0-rc1' was restored using '.NETFramework,Version=v4.6.1' instead of the project target framework '.NETCoreApp,Version=v2.1'. This package may not be fully compatible with your project.
Feature description
Currently I copied DotSpatial.Projections sources to another repository to adapt for use with dotnet. I wondering if DotSpatial.Projections could enabled to generate only a Net Standard dll so that it can be used even from NET Framework referencing assemblies directly using packages from DotSpatial instead to build my own.
You can try NET standard version by adding following packages to a net framework project
Install-Package netcore-proj -Version 1.0.0-CI00004 -Source https://www.myget.org/F/devel0/api/v3/index.json
Follows major changes to the DotSpatial.Projections:
- removed Properties folder
- changed csproj to generate netstandard and embed resource
datums.xml.ds
. Note that I used different name to avoid upgrade hint on myget same package name that already exists. - handle resource name respect framework mangling used
Issue Analytics
- State:
- Created 5 years ago
- Reactions:4
- Comments:8 (2 by maintainers)
Top Results From Across the Web
.NET and .NET Core official support policy - Dot.net
But the actual end of support day is the closest Patch Tuesday starting that date, which is November 12, 2024. ASP.NET Core 2.1...
Read more >Contact Us
We're here to help! If you have technical issues or questions about your account, contact support. Contact information. See our office locations ...
Read more >Netcore Solutions Pvt. Ltd.: Support
Netcore Solutions Pvt. Ltd. · How can we help you today? · Knowledge base · Community forums.
Read more >Microsoft Announces End of Support Date for .NET Core 3.1
Microsoft announced today that .NET Core 3.1, a predecessor to .NET 5 and 6, will reach its end of support on December 13,...
Read more >.NET Core Support Overview - Telerik UI for WPF
Telerik UI for WPF comes with support for .NET Core 3.1, .NET 5 and .NET 6. There is are sets of DLLs built...
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
Currently working on .net 6 release.
I know, but the problem for me is that there are some package deployment actions that I can’t verify, would be better if someone that have hands on this project nuget packages makes a working copy transition test with: