Play ASP.NET Web Forms
Sign in to queue


Do you want to learn techniques to enhance your Web Forms development experience. See how you can improve your code's maintainability and testability and your site's performance. Leverage new features in ASP.NET Web Forms 4.5 to reduce the amount of UI "yuck" code and focus on your application's logic. We will look at some of the improvements to Web Forms such as support for EF 6, new Scaffolders and more features which you might not have heard of. We will see how to leverage all of the latest tools in Visual Studio like Browser Link and Web Essentials to make their coding experience simpler, shorter, and more enjoyable.  





Right click to download this episode

The Discussion

  • User profile image

    I've heard (and understand) all of the benefits of using async data calls, but I have never heard if there are any negatives to setting the async page directive to true... I have a large (mostly legacy) webforms site running under 4.5 and make several calls out of my business tier that would benefit from using async. However, the pages that ultimately call into those business methods don't know that they might call async processes. So, that leads me to the question, Is there some reason why I should not run a page with the async directive set to true? Would there be a drawback to setting it to true for the whole site/application?

  • User profile image

    In a modern webforms app (.net 4.7.2) the default project structure doesn't really have any folder to contain business logic.

    Is it reasonable (or even best practice) to just add a folder called "Business Logic" to the root project and stick all my classes in there ?

Add Your 2 Cents