-
Notifications
You must be signed in to change notification settings - Fork 41
Ext.NET End of Life #1879
Comments
That is sad news. I liked Ext.NET. But I understand your decision to move on. |
Bad news. I've been working with ext.net for more than 10 years. It is possible that you will release the last nuget package, with a .net8 compatible version, before the end of the project. |
Unfortunately, no further public releases will be made. It should be relatively straightforward to upgrade Ext.NET v7 to .NET 8 with the source code project for use within your own organization and product. |
The latest 7.4.0 Nuget package(s) should work OK with .NET 8. I've been able to upgrade a .NET 6 solution that uses Ext.NET Core to target .NET 8 without any problems. |
Hello! I am migrating a old application from a Customer to a new server hosted in Azure Cloud. But the application doesn´t runs correctly with Ext.Net version 2.1.1 if the Application is behind a Application Gateway or a Nginx Reverse Proxy. The Application only works perfectly with Ext.Net version 2.5.3. Is there a free version of Ext.Net 2.5.3? I am asking this to try to maintain this old application online where a new application is developed. |
Hello @asmialoski. The entire release history of Ext.NET Legacy is available in the Archives. As well, every release is also available in NuGet. Hope this helps. |
Hello, is there a chance to get the forum back online? I know, there is a limited time available to check the content. At the moment there is a internat server error 500. |
Sadly, Ext.NET has reached end-of-life and is no longer available. 😢
FAQ
Q. Will my app using Ext.NET stop working?
Your app will not stop working.
The Ext.NET assemblies will continue to work, essentially forever, with your existing license key. Purchasing the source code is not required to continue using Ext.NET within your application.
If required, you will even be able to start new projects with Ext.NET as the NuGet packages will not (cannot) be removed from NuGet.
Q. What will happen to the speed.ext.net CDN service?
The CDN services through
speed.ext.net
will remain online for at least one year until Dec 15, 2024, although we will try and leave online indefinitely. There is essentially no cost to operating the CDN, so as long as we are in control of theext.net
domain name, we should be able to leave the CDN running.That said, if you are using the
renderStyles="CDN"
and/orrenderScripts="CDN"
settings in your<ext:ResourceManager>
, it would be best to remove those two settings and just use the defaults.Q. Can I get the Examples Explorer source code?
The Examples Explorers are open-source and the source code is available on GitHub within the following projects:
https://github.com/extnet/examples.ext.net
https://github.com/extnet/examples5.ext.net
Each version is available within a separate branch.
Q. Are the packages available thru Nuget and/or .NET CLI going to be removed?
The NuGet packages cannot be removed. They will live on forever. Authors can hide the packages so they are not publicly searchable, but not remove from NuGet. We do not plan to hide the packages.
Q. Is it possible to get a copy of the forum content for future reference?
Our plan is to maintain the forums online until December 15, 2024. Sharing the database is not possible, at least not with all the private user information saved within. We are looking into options to share a static version of the forums, although this seems unlikely.
At the moment, I'm just not sure what we will do with the forums, but our absolute intention is to keep them online and publicly available, ideally forever.
The text was updated successfully, but these errors were encountered: