3 ms·
From my understanding, that's not really a migratable stack. Depending on what you're doing in 4.8 (aspx, wpf, aka windows only type stuff) there's not a direct
by jcon321 5y ago
From my understanding, that's not really a migratable stack. Depending on what you're doing in 4.8 (aspx, wpf, aka windows only type stuff) there's not a direct migration. It's more of a re-write.
- jbergens 5y agoI think you are only kind of right. aspx is over 10 years old, you should have switched to .NET MVC already and then the difference to .NET Core is small. We rewrote some things at an earlier company and there mostly general things like auth and where to get querystring variables and similar that had changed. If we look at WCF to REST (or gRPC) it is also mainly easy since it is some general configurations and infrastructure things that have changed but most of the business logic will work. So you have to rewrite but it might be quite easy. And doing this once every decade is not that strange. Also remember that most of the old things still work. You can stay on those tech stacks for another couple of years if you feel that is better for your organization.
- electroly 5y agoWPF wasn't left behind. It's still supported in .NET 6, you don't have to rewrite anything. Windows Forms, too. Can you be more specific what you mean by aspx? ASP.NET is, of course, still supported. https://docs.microsoft.com/en-us/dotnet/core/porting/net-framework-tech-unavailable https://docs.microsoft.com/en-us/dotnet/core/porting/net-fra...
- hackerfromthefu 5y agoAspx is the file extension of Web Forms pages, which have no direct migration path to .net core/6.
- electroly 5y agoAh, of course. Thank you!