| | Sun | Mon | Tue | Wed | Thu | Fri | Sat |
|---|
| 25 | 26 | 27 | 28 | 29 | 30 | 1 | | 2 | 3 | 4 | 5 | 6 | 7 | 8 | | 9 | 10 | 11 | 12 | 13 | 14 | 15 | | 16 | 17 | 18 | 19 | 20 | 21 | 22 | | 23 | 24 | 25 | 26 | 27 | 28 | 29 | | 30 | 31 | 1 | 2 | 3 | 4 | 5 |
Subscribe to this feed:
|
| 
Archives:
| May, 2010 (1) |
| March, 2010 (1) |
| November, 2009 (1) |
| September, 2009 (1) |
| July, 2009 (2) |
| June, 2009 (1) |
| May, 2009 (1) |
| March, 2009 (5) |
| February, 2009 (3) |
| July, 2008 (1) |
| June, 2008 (2) |
| May, 2008 (1) |
| April, 2008 (2) |
| March, 2008 (4) |
| February, 2008 (4) |
| December, 2007 (2) |
| October, 2007 (2) |
| September, 2007 (1) |
| June, 2007 (1) |
| May, 2007 (4) |
| April, 2007 (4) |
| March, 2007 (2) |
| February, 2007 (4) |
| January, 2007 (3) |
| December, 2006 (1) |
| November, 2006 (4) |
| October, 2006 (7) |
| September, 2006 (2) |
| August, 2006 (14) |
| July, 2006 (9) |
|
Framework Design Guidelines is one of the best .NET books I've read, bar none. The only downside for some will be that the examples are in C#, but even so, there is tons of great, real-world guidance that applies to all levels of .NET development. Written by a couple of Microsoft developers who worked on the .NET framework, it's suprisingly candid and easy to read.
ASP.NET 2.0 includes a new set of features called ' Health Monitoring.' This involves a lot of different ways to monitor the 'health' of your application in event logs, performance counters, etc. One use of it, though, is to send email notification of exceptions. This is something we traditionally had to do in code, or with a logging framework like Enterprise Library Logging. In ASP.NET 2.0, though, it can be done by simply configuring the application.This also includes some cool features- such as the ability to prevent sending the same error 100 times. Other providers support going to a SQL Server table or the event log.
Craig Utley presented a very useful Microsoft Webcast a few months back on three common OO design patterns (Singleton, Factory, and Observer). In addition to describing practical coding techniques to solve particular problems, Craig also shows two methods for implementing each pattern -- a "traditional" approach that uses coding constructs available in most languages, and a more elegant ".NET" approach that takes advantage of features of the .NET framework to achieve the same goal; for example, his .NET implementation of an "Observer" pattern uses delegates/events to communicate between publisher and subscriber objects, rather than having the publisher aggregate references to the subscribers.
There is also a good reference to various patterns, with sample implementations, here.
One of the interesting features of
SQL Server 2005 is a new utility for working with Reporting Services called
Report Builder.
Designed as a reporting solution for the non-developer set (a la MS
Access reporting, and others), the tool works against “Data Source Views” (DSVs)
created as an abstraction of the underlying tables – the general idea is that
the end user works with entities and relationships of entities rather than with
relational database tables (think “General Ledger View” vs. GL00100, GL00101,
etc.)
For the more savvy users in some
organizations, Report Builder, used in conjunction with well-planned DSVs could
eliminate some of the ad-hoc reporting tasks that are often delegated to
developers.
Video demonstration here.
There is an excellent collection of tutorial videos on the Official ASP.NET 2.0 web site. While they are probably most beneficial for developers seeking to learn about the new features in 2.0, they should also be useful for those moving to ASP.NET 2.0 from other environments, like traditional ASP or PHP.
|