The presentation layer is a vitally important part of an application. This article discusses the thin and smart client approaches and provides guidance on how to choose between them.

Choosing the Right Presentation Layer Architecture

[ Via Mark Bower ]

Brad Abrams just published an article containing the CLR team’s internal coding conventions . It’s a good example of a coding style document.

[ Via Larry Osterman's WebLog ]

By having support for 1.1 it will make it much easier for customers to get their feet wet prior to converting to 2.0.  As much as we all wish all our clients will convert to 2.0 the day it arrives - we all know that’s not the reality.

Take a minute and register your vote!

Click here to view the issue on Feedback Center and register your vote!

[ Via MrDave's WebLog ]

Brad Abrams wrote interesting information about Trend of .NET Framework installations

Log parser is a powerful, versatile tool that provides universal query access to text-based data such as log files, XML files and CSV files, as well as key data sources on the Windows? operating system such as the Event Log, the Registry, the file system, and Active Directory?.
You tell Log Parser what information you need and how you want it processed. The results of your query can be custom-formatted in text based output, or they can be persisted to more specialty targets like SQL, SYSLOG, or a chart.
The world is your database with Log Parser.

Log Parser is made up of three components:

• Input Formats are generic record providers; records are equivalent to rows in a SQL table, and Input Formats can be thought of as SQL tables containing the data you want to process.
  Log Parser’s built-in Input Formats can retrieve data from the following sources:
  • IIS log files (W3C, IIS, NCSA, Centralized Binary Logs, HTTP Error logs, URLScan logs, ODBC logs)
  • Windows Event Log
  • Generic XML, CSV, TSV and W3C - formatted text files (e.g. Exchange Tracking log files, Personal Firewall log files, Windows Media? Services log files, FTP log files, SMTP log files, etc.)
  • Windows Registry
  • Active Directory Objects
  • File and Directory information
  • NetMon .cap capture files
  • Extended/Combined NCSA log files
  • ETW traces
  • Custom plugins (through a public COM interface)
• A SQL-Like Engine Core processes the records generated by an Input Format, using a dialect of the SQL language that includes common SQL clauses (SELECT, WHERE, GROUP BY, HAVING, ORDER BY), aggregate functions (SUM, COUNT, AVG, MAX, MIN), and a rich set of functions (e.g. SUBSTR, CASE, COALESCE, REVERSEDNS, etc.); the resulting records are then sent to an Output Format.
• Output Formats are generic consumers of records; they can be thought of as SQL tables that receive the results of the data processing.
  Log Parser’s built-in Output Formats can:
  • Write data to text files in different formats (CSV, TSV, XML, W3C, user-defined, etc.)
  • Send data to a SQL database
  • Send data to a SYSLOG server
  • Create charts and save them in either GIF or JPG image files
  • Display data to the console or to the screen

Download Log Parser 2.2

[ Via Conrad Agramont's WebLog ]