Replied 12 December 2018, 12:42 am EST
Microsoft included 3 new features in Web Forms in the July 2015 release of <a href="https://crbtech.in/programmes/dot-net-training-programme">.NET</a> Framework 4.6. So clearly, they still intend to support it and even add to it on occasion. It’s a mature framework, so it’s to be expected that the updates wouldn’t be as large and significant as they were in the early days. But, at the same time, 4 versions of .NET Framework have been released since then (4.6.1 – 4.7.1) without any new features specifically for Web Forms. Instead, the energy has been largely behind ASP.NET Core, MVC, and Web API. It seems fairly clear to me that those are where the excitement is in ASP.NET now.
If I had to predict, I’d say that ASP.NET Web Forms will stay largely what it is today and be supported by the .NET Framework for at least several major future releases. However, it should be noted that the .NET Framework is also gradually be eclipsed by .NET Core, the cross-platform, rewritten version of .NET. So, even from that perspective, it looks like Web Forms could be waning.
When you think about building a new application or updating an existing one into a more modern technology, it’s usually a good idea to jump in fairly close to the cutting edge. Technology moves so fast these days that jumping in very far back will often result in earlier obsolescence. For that reason, we recommend that our customer create their new applications in ASP.NET Core.
You also have to think about how you will support a new software application. Typically, this involves an internal team of developers–developers who want to work on the latest technologies, and because they have been in short supply these last couple of decades, require a certain amount of wooing to attract and retain the best ones.