In the workshop, I was saying that I genuinely see no issues in using Web Forms today.
Like every other thing in this imperfect world, the Web Forms technology has pros and cons, but it just works so it’s more than OK to use it even though it’s a fifteen-year old technology.
While this new MVC-based paradigm looks familiar and attractive to Web developers coming from a Java or PHP background, it feels weird and cumbersome to developers who grew up with Web Forms and server controls.
Hence the question: is it really safe to mix Web Forms and ASP. When it came out, Web Forms was the right framework at the right time.
Dino Esposito shows how to give your Web Forms application a new lease of life.
Last fall I gave a presentation at a conference about the realistic options you have today for building web sites on the Microsoft Web stack. NET MVC, there will be no illusions of state, there will not be such a thing as a page load and no page life cycle at all, etc. NET MVC was to be extensible throughout all aspects of the framework.Just because you're using Web Forms, it doesn't mean that you are stuck in a technical time-warp. You now just have a class with regular methods on it that you can invoke in unit tests to find out if that controller is going to behave correctly. NET runtime or ties to the ASPX page, which is very hard to test.However, the teams behind these Web sites are, reasonably, looking ahead and planning new features.