ASP.NET Web Forms may be legacy technology, but it's still extremely stable. If you just need need someone to keep things running, or minor adjustments here and there, we can certainly lend a hand.
Want to convert your legacy application to the latest .NET technology? We can do that, too; either all at once or piecemeal to keep things running smoothly.
We can ensure your application follows the latest in application security best practices, make recommendations, and perform the fixes.
Need to upskill yourself of your team? Inquire about our training courses and we'll schedule an in-person or virtual training as appropriate.
Looking to move an existing application into a different environment or take advantage of specific AWS, Azure, or GCP services? Many legacy apps can be improved quickly and cheaply by replacing custom-built logic with standard services.
Greenfield project that needs to work with your existing infrastructure? We'll identify ways to take advantage of what you already have and build onto it in ways that allow for future evolution and migration without having to rebuild the world.
While still in High School, Brian dove head-first into the ASP.NET world with the help of the incomparable "ASP.NET Unleashed". (updated for "final" .NET 1.1 version!)
After graudating from High School... and College... and working with other software stacks... and completing several side projects with ASP.NET, Brian landed his first paid ASP.NET Web Forms gig. This grew into additional projects over the years.
Announced in 2014, Microsoft released .NET Core as an open source, cross-platform version of .NET. Essentially a rewrite of the .NET Framework focused around newer web application models and modern design patterns, .NET Core does not include support for ASP.NET Web Forms, forcing companies to completely rewrite applications or stay with .NET Framework despite diminishing support.
This is an excellent question. .NET Framework 4.6.2 goes out of support in early 2027 and official end of support dates have not been provided for .NET Framework versions 4.7.2 and 4.8.1. It's possible they will be tied to the OS versions that they initially shipped on, or they could be given their own support timeline.