Windows Applicathttp://www.microsoft.com/windowsxp/appexperience/appverifier.asp ion Verifier. "The Windows Application Verifier (AppVerifier) examines executable programs for common application quality issues. Running this tool on an application aids a tester in detecting issues dealing with stability, security, and compatibility."

This tool should be required for all QA departments, just like FxCop is required for all .NET developers. [sellsbrothers.com: Windows Developer News]

OK, OK.

Useful tool: Database design/data access code generation:

DeKlarit provides a simple way to automate a great part of the application design, development and maintenance process by automatically generating the data model and the code for your data access and business logic layers.

 

The anatomy of a stylesheet. [Simon Willison's Weblog]

First part of a series on css - a good introduction.

FeedDemon is a news aggregator being designed by Nick Bradbury who also designed HomeSite.  It has some minor yet interesting improvements on news aggregator UI. [Don Park's Blog]

At last, someone applying thought to the UI and getting away from the trite three paned. I'll grant this is three paned but at least the panes aren't treeview, listview and content view. But then I would like this since it was the sought of UI style I was thinking of, perhaps this will save me the bother.

SharpLibrary Released. The SharpLibrary is a comprehensive Graphical User Interface library written for the .NET Framework. It has as its main goal to alleviate a lot of the limitations of the standard controls in the WindowsForms namespace. As such, it enhances many of the default controls with needed features that developers often find themselves wishing the out of the box controls had. It also has its fare share of controls totally written from scratch when the standard controls were too limited to obtain a feature or there was simply not equivalent available. The result was controls that look good, are flexible, powerful and which also are free from the limitation, compatibility issues and just simply age that the native controls inherently have and thus are better suited for further enhancements that can accommodate the most demanding requirement of applications being written in the 21st century.


Posted by Carlos H. Perez on Tue, May 13, 2003 @ 7:40PM [sellsbrothers.com: Windows Developer News]

Managing an @@Identity Crisis. Discusses a strategy for returning newly created Identity values after the INSERT is executed. Letting SQL Server generate Identity values might make your job harder if you don't know how to retrieve the new Identity values. [MSDN Just Published]

I also wanted to point everyone to a nice Regular Expression repository RegExpLib.com (created by Steven Smith) and Dan Applemans excellent Regular Expressions with .NET book. [Alex Lowe's .NET Blog]

Thank you, bloomin' brilliant.

Dom Validator Controls V2.0.

Paul Glavich has released version 2.0 of his Dom Validator controls.

These controls support all of the client-side validator functionality found in the Microsoft supplied validator controls, but contain support for a wider variety of browsers such as Netscape 6.0+ (client and server side) and 4.72+ (server side only), along with Internet Explorer. This release incorporates a new RangeDomValidator to complete the validator control set, has many bug fixes, and includes .Net framework 1.1 support.

[ScottW's ASP.NET WebLog]

How ASP.NET Web Services Work. See how Microsoft ASP.NET Web services methods (WebMethods) provide a high-productivity approach to building Web services. WebMethods can expose traditional Microsoft .NET methods as Web service operations that support HTTP, XML, XML Schema, SOAP, and WSDL. [MSDN: .NET Framework and CLR]

Cutting Edge - Form-based Programming in ASP.NET. Tips for Forms Programming [MSDN: .NET Framework and CLR]

In here it mentions that showModalDialog suffers from the fact that it cannot host a form without wrapping in an iframe - in Zeepe 7 we don't need the iframe hack.

It also mentions something I didn't know - a .NET generated form must post back to the same 'page'; reasonable I suppose but ....