5 ms·
OTOH, an ASP.NET web app written in 2008 and not touched since then would probably still run happily now if you bumped its version up to .NET 4 or 4.5. C# has
by rpeden 8y ago
OTOH, an ASP.NET web app written in 2008 and not touched since then would probably still run happily now if you bumped its version up to .NET 4 or 4.5.
C# has had Linq and lambdas since 2007 so there's a decent chance the code would be decently pleasant to work with, too.
Some devs might find 2008 Web Forms apps a bit crufty in 2018 but if you squint and pretend your .aspx is inside a render method issued of a separate file, the mental model isn't all that different from a SPA.
- cm2187 8y agoWith .net core the writing is on the wall that the full .net framework will go the way of .net 1.1 (the .net team highlighted that it is too burdensome to maintain both frameworks in parallel). I am not sure that the new Microsoft has the same commitment to support legacy code than the Microsoft of the last 20 years.
- oldmanhorton 8y agoThey've made it clear that .NET Framework will be supported for many, many years. It just won't be getting as many new features. The point of the discussion here is about depreciating and removing and breaking existing tech, which will almost certainly not happen with .NET anything. Note that even VBScript still gets security updates. It's unimaginable that anything targeting .NET Framework will break (short of a bug) for at least a decade, and probably much longer.