I have exactly the same thought with this blog’s author.
As we all know, ASP.NET introduces a brand new concept namely event-driven programming to the web development fields. Although it sounds attractive, for the ASP.NET beginners, it is not so important that you should know any detail to build some nice look so called web applications. However, when you get more and more familiar with this technology, you will find it is more and more necessary to know some details under the face. Why you want to know more about this event-driven programming model, because more and more controls come onto your web form and the event these controls expose just come more and more out of your control and finally explode.
Here, I’m sure the following article will helpful for those in the smoke after explosion.
Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries by Krzysztof Cwalina and Brad Abrams is one of my favorite books. They are working on a new version, too. What would be a new Framework Design Guidelines book without a section on LINQ Best Practices when used as part of a framework API? Here is a blog post with just that type of information that covers:
- A Brief Overview of LINQ
- Extension Methods, Func<>, Action<>, and Expression<>
- Extending on LINQ
- Extending IEnumerable<>
- Extending IQueryable<>
- Implementing the Query Pattern
"Writing applications that interact with data sources, such as databases, XML documents, or Web Services such as Flickr or Amazon, is made easier in the .NET Framework 3.5 with the addition of a set of features collectively referred to as LINQ (Language-Integrated Query). In what follows, we start with a very brief overview of LINQ, followed by guidelines for designing APIs in relation to LINQ."
When you come from xUnix world to ms world, I believe you like things like this.
Pretty simple but very useful snippet to help abandon session soon after user click to close the browser.