This has nothing to do directly with this blog post, but just wanted to say that Scott Hanselman is probably the best that could have happened to .NET of all things. Better than Linq and async/await together. He's an amazing speaker and his blog is a great resource for everything around .NET. Can highly recommend to watch and follow this guy!
Agreed. He and Scott Guthrie used to make an amazing 1-2 punch when they were both working in the ASP.NET area of Microsoft.
Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
21–30 of 36 posts
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#22Earlier quoted context omitted.
They did get WordPress at least sort of running on it. That wasn't possible with the first releases of hhvm, so it says something.
'Sort of running' and stable enough to deploy into production are different things. I really want this to work but I am a little nervous about committing to it.
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#23Earlier quoted context omitted.
'Sort of running' and stable enough to deploy into production are different things. I really want this to work but I am a little nervous about committing to it.
It was running with modifications at the time, but now runs unmodified. I suggest to get in touch with the team to discuss your specific case at info at iolevel dot com.
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#24I'm trying to find a use case for this. A .NET to php decompiler may be more useful at this point in time.
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.
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#25Most recent HN discussion dug into the tech and also the rationale behind transitioning in either direction: https://news.ycombinator.com/item?id=13753445 (404 points/164 comments/Feb 2017)
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#26I'm trying to find a use case for this. A .NET to php decompiler may be more useful at this point in time.
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.
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.
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#27I'm trying to find a use case for this. A .NET to php decompiler may be more useful at this point in time.
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.
It would be helpful if you can provide some source for this.
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#28Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#29Earlier quoted context omitted.
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.
> 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, M…
[disclaimer: Microsoft employee, .NET Foundation staff]
Re: Peachpie – Open Source PHP Compiler to .NET and WordPress under ASP.NET Core
#30I'm trying to find a use case for this. A .NET to php decompiler may be more useful at this point in time.
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.