3 ms·
Was part of an ASP->ASP.net conversion project whose project plan amounted to: “load it up in Visual Studio, switch from ASP VB to VB.net, edit until all red un
by sokoloff 7y ago
Was part of an ASP->ASP.net conversion project whose project plan amounted to: “load it up in Visual Studio, switch from ASP VB to VB.net, edit until all red underlines are removed from the codebase. Should take 6-12 weeks.”
3 years later, we were almost done.
- thrower123 7y agoI am dreading this transition when it becomes necessary for .NET Framework -> .NET Core. On the surface, it's not too different, but then you look deeper, and here is a dependency that changed completely between it's old Framework version and the new Core one, there's a place that we're using Linq-to-SQL instead of EF, there's an SDK that we use that is never going to be updated to a Core version, etc.
- gwbas1c 7y agoI believe it's coming in .Net 5, if I understand the roadmap correctly. At least it's not a 100% new language skinned to look like the old one!
- stronglikedan 7y agoHaha just be glad the original ASP wasn't created by ASPRunner, and all you have is the source code, like the project I'm currently rewriting.