Hacker News Reader

Comment by wolco | Hacker News Reader

I'm trying to find a use case for this. A .NET to php decompiler may be more useful at this point in time.

To me it seems similar to running Ruby on the JVM (JRuby). Perhaps you like php but have a lot of .net code to interop with. I bet writing business logic in C# and web tier code in php could possibly be a satisfying experience.

A dotNet asp.net (Webforms, etc) to PHP compiler would be more useful.

Now that asp.net is end of life, these sad people are looking for ways to migrate their aging asp and asp.net code base to elsewhere. The only supported option is the incompatible new asp.net core on dotNet core - out of the jungle into the jungle.

Microsoft has been steadfast that it will support the .net 4.x for foreseeable future and improvements and newer versions will come, given that 4.7 is on the way, I see no grounds for the claim webforms are being deprecated, the guidance has been MVC is the recommended solution, but WebForms were always supported.

It would be helpful if you can provide some source for this.

What would be great would be a decompiler that could port .net windows application code to http://gtk.php.net

> asp.net is end of life

Even Silverlight is not officially dead until 2021 so I'm not sure I'm clear on your terminology (vs. https://support.microsoft.com/help/17455 ).

Just for fun I dug up the "Mainstream Support End Date" for ASP.NET on .NET 4.5.2: 10/9/2018.

Starting from https://www.asp.net/support

Many parts of ASP.NET are a part of the Microsoft .NET Framework, these include ASP.NET Web Forms, Controls, Modules, Handlers and more. For more information see .NET Platform Support.

Then at https://www.microsoft.com/net/support

The Support Lifecycle information for all versions of .NET Framework can be seen on the Microsoft Product Lifecycle site.

Then at https://support.microsoft.com/en-us/lifecycle/search?alpha=....

For more information, please visit the .NET Framework Support Lifecycle Policy FAQ.

Then at https://support.microsoft.com/help/17455

Support for .NET 4.5.2 follows the lifecycle policy of the parent operating system. It is supported as a Windows component on the latest required operating system update for Windows Vista SP2, Windows 7 SP1, Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows 8.1 Update, Windows Server 2012, and Windows Server 2012 R2.

Then at https://support.microsoft.com/en-us/lifecycle/search?alpha=W...

Products Released: Windows Server 2012 R2 Standard

Lifecycle Start Date: 11/25/2013

Mainstream Support End Date: 10/9/2018

Extended Support End Date: 10/10/2023

Service Pack Support End Date: [empty]

Notes: Mainstream and Extended support for this product has been extended to provide customers with the standard lifecycle transition timeline. For up to 6 years of additional support beyond Extended Support, please see the Premium Assurance website.

.NET 4.7 shipped earlier this year and includes Web Forms support. Looking at the support lifecycle page, I can see how the order of answers calling out .NET 4.5.2 at the top might be confusing. The last answer on that page ( What is the Lifecycle Policy for the different versions of the .NET Framework?) is the one I think you want - it indicates that .NET Framework 4.7 ships with Windows Server 2016 and Windows 10 CU (1703), which pushes you out to 2022 (minimum, every release keeps resetting the clock) for Mainstream Support.

[disclaimer: Microsoft employee, .NET Foundation staff]

Reply on news.ycombinator.com