
Start from pre-configured Project Templates # NET Framework workloads when you need to which will continue to receive enhancements and new features with each ServiceStack release courtesy of being derived from the same shared code-base which will enable seamless migrations to. This is to say that ASP.NET Core 2.1 LTS is still a fantastic rock-solid platform to run your. NET Core and runs everywhere ServiceStack does including within classic ASP.NET MVC Controllers which wasn't a design goal but was a natural consequence of developing clean libraries without external dependencies or reliance on external tooling. This includes our own innovations that we continue to invest in like #Script (fka ServiceStack Templates) naturally support. Future proofed and continually developed #

NET Standard 2.0 which is supported natively on ASP.NET Core 2.1. NET Framework, we're not, our supported packages have standardized to multi-target both. Whilst Microsoft is stopping new development of ASP.NET Core on. Unlike Microsoft web frameworks, ServiceStack is a single code-base which supports running on multiple platforms so your ServiceStack Services can enjoy near perfect source-code compatibility when and if you choose to move to. NET Framework, we'd still recommend using the newer ASP.NET Core 2.1 over classic ASP.NET System.Web projects as it's cleaner, lighter, more flexible and future proof.

ASP.NET Core - still our top recommendation for. NET Core's major version release train and build upon a stable LTS platform. NET Core immediately or if you want to get off. NET Framework has effectively been put on product life support, ASP.NET Core 2.1 LTS is still a great rock-solid platform to build on if you're unable to jump directly to. Whilst this announcement sends a clear message that new development on. NET Framework - which should come as great news to the 1/3 of our Customers who are still creating new ASP.NET Core on FX Project Templates.


NET Core from commencing, we're happy to see ASP.NET Core 2.1 LTS will enjoy the same indefinite level of support as the rest of the. Whilst we disagreed against this decision which would've put out a large class of the existing ecosystems from participating in the new ASP.NET Core development model and many from staged migrations to. The last important Microsoft announcement concerning the future of ASP.NET Core 2.1 was that it would stop supporting new versions of ASP.NET Core on the.
