Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
No .NET Core version on NuGet
See original GitHub issueI feel like there should be builds of the dotnet-core branch on NuGet and AppVeyor separate from the original ones.
Issue Analytics
- State:
- Created 4 years ago
- Comments:14 (6 by maintainers)
Top Results From Across the Web
Do .NET Core SDK / Runtime and NuGet Package ...
2 · No... · The honest answer is: it depends, and it can depend on quite a number of things, such as whether...
Read more >NuGet Package Version Reference
The highest version including the not stable versions. Available in Visual Studio version 16.6, NuGet version 5.6, .NET Core SDK version 3.1.300.
Read more >Installing NuGet client tools
Guidance on installing client tools, the dotnet and nuget command-line interfaces (CLI), and the Package Manager for Visual Studio.
Read more >Recommendation needed for using NuGet packages ...
Net 6, uses NuGet packages with 7.X.X version, since the "Manage Packages for Solution" does not block NuGet packages updates from 6.X.X to...
Read more >NuGet Package Manager attempting to add .NET 5.0 ...
Is it possible that NuGet to block updating .Net Core 3.1 packages to 5.X.X versions? Based on your answer, we know that .Net...
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 Free
Top 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
Latest nuget package has both .Net FX 3.5 and .NET Core 2.0 packages. @bigworld12 ended up just modifying my MSBuild script so I can still use the nugspec.
Alright, i will look into this over the weekend. If I can just use dotnet pack, then the build scripts can be simplified and that should fix any concerns I have with releasing a .NET Core package along side the .NET Framework package.