.NET standard release plan
See original GitHub issueHi
I’m considering using Spring.Messaging.Nms
in several projects for my company. The main obstacle that prevents me from taking it right now is the lack of the release of a version compatible with the .NET standard. I would like to know what is the current status of porting Spring.Messaging.Nms
to .net standard and what are the release plans?
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:23 (3 by maintainers)
Top Results From Across the Web
.NET and .NET Core official support policy - Dot.net
A new major release of .NET is published every year in November, enabling developers, the community, and businesses to plan their roadmaps.
Read more >NET Standard
NET Standard will be released, but .NET 5, .NET 6, and all future versions will continue to support .NET Standard 2.1 and earlier....
Read more >roadmap.md - dotnet/core
.NET 6.0, LTS (Long Term Support) release. Approximately every 1-2 months or as needed. ;.NET 7.0, STS (Standard Term Support) release. Approximately every...
Read more >Understanding the .NET ecosystem: The introduction of . ...
In this article, previously part of my new book, we look at .NET Standard, look at why it was created, and discuss its...
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 >
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
On top of earlier progress:
I have spent considerable amount of my time (including part of my recent summer holiday) to get things working on .NET Core / NET5, all the permissions and setups done (collaboration with past maintainers), fighting the build system etc. Please do not expect me start fixing everything you might find, but everyone as consumer of the framework should provide pull requests to push things forward. Now publishing new versions should at least be (a lot) simpler.
There’s always option to sponsor, if you want to show gratitude of the past work, this will not bind me to future work 😉
Let’s consider this issue fixed!
@markpollack, @sbohlen and @lahma, @gjarzab , Is there anything we could help you with? Please release pre-release packages.
We are heavily invested in Spring.net for multiple products, It is high time we migrate to .net standard to do anything like Dockerization, getting rid of system.web, lighter application, faster performance, fewer allocations, Browser link.
@terrajobst, @simulacrux are also interested
Someone has created pre-release package here - https://www.nuget.org/packages/D3S.Spring.Core/3.0.3-pre