Michele Leroux Bustamante has some info on globalization and internationalization here. Includes notes from talk at TechEd 2004.

.NET Dashboard

Here's another discussion from Michele, this time on MSDN. Might be the same content, but has some good info.

keywords: G18N I18N

From TechNet 2004, quick summary of IIS 6 and ASP.NET tuning.
Reference to a good book here as well.

ASP.NET: Best practices for managing and operating IIS6 and ASP.NET

How to deal with return codes and output parameters from ADO.NET

Retrieving the Gazoutas: Understanding SQL Server Return Codes and Output Parameters

After insert, knowing the identity column values.

Managing an @@IDENTITY Crisis

A quick way to do this also (from DotNetBips.com) is to use StoredProc to add the new records. The SP has output param that tells the identity column value. Now you can stuff this value into your in-memory DataRow.

Various issues related to SqlCommandBuilder, auto-generating the insert, update, delete commands, etc.

Weaning Developers from the CommandBuilder

313540 - PRB: Merge Method Creates Duplicate Records for AutoIncrement Fields

Cool, you can suppress the ASSERT GUI handling and have the assertion text write to a file.

<system.diagnostics>
<assert assertuienabled="false" logfilename="c:\TEMP\Debug.log" />
</system.diagnostics>

In this case, your app will continue running, as if you clicked "ignore" in the assertion dialog box. To override this behavior,

Implement a trace listener, override Fail() and call
System.Diagnostics.Debugger.Break()


Google Groups: View Thread "Trace.Assert to console"

This is probably well known, but I just stumbled upon it today.

When building a WinForms app, the output dir (i.e. bin\debug) is recreated, so any blah.exe.config file you may have there is deleted.

To keep your config file - you must add it to the solution, with the name app.config (not "", but just app.config)

The build process will rename and copy this config file to the output dir and name it appropriately.

Keith Brown, .NET security book.

A .NET Developer's Guide to Windows Security: Item 9: How to develop code as a non-admin