Here. From Andrew Webb: Even if you don't want to download the beta, this article gives a nice overview of what to expect in the 1.1 version of .NET Framework. Note the 'Developer Tools Roadmap' link at top-right of the Beta Overview page. www.gotdotnet.com has an article about forwards and backwards compatibility between 1.0 and 1.1.

Here. From Keith Wedinger: What if your current application is currently a Java EJB (Enterprise JavaBeans) implementation? Is it worth the cost and effort to migrate to Microsoft's new platform?

Here. From Jim Wilson: The DevelopMentor .NET Compact Framework Tools and Samples page is finally available. Check it out to see if there is something that you need or if you have something that you think would be helpful to others please post it.

Here. QuickCode is a VS.NET add-in that expands phrases into code, e.g. prop int test would expand to an entire property implementation. It works for C# and VB.NET and appears to be very flexible.

Here. "The KDE Project has emerged as possibly the first real-world adopter of Project Mono for application development. Mono is an open source alternative to .NET for Unix and Linux desktops, initiated in July 2001 by Ximian Inc." The reason that this is interesting for Windows developers is that with both of the major Linux desktops, i.e. Gnome and KDE, supporting .NET, it's possible that a simple .NET application or component could actually work across Windows, Gnome and KDE. Now .NET becomes the OS. Shades of Java, which failed in this space I know, but still interesting...

Here. Just when you'd thought you're learned everything there was to know about foreach in part 1, I've got more in part 2! This part (the final : ) discusses implementing support for foreach in your own custom types as well as how to patch holes in the framework where they forgot to add foreach support. Enjoy.

Here. Ian Griffiths and Chris Sells "Unresponsive programs are extremely frustrating to use. Applications that sometimes freeze for a moment are a source of much irritation, especially if they don't provide any feedback on what they are doing, or how long it is likely to be before they start responding again. This behaviour can be particularly common among applications that use remote facilities such as Web services. This article describes how to maintain responsiveness in .NET Windows Forms rich client applications, even when invoking potentially long-running Web services, by using multiple threads."

Here. Shawn Wildermuth and Chris Sells "In the .NET Framework, rich clients can bring database servers to their knees, just like Web-based applications. But with the disconnected nature of ADO.NET, your rich clients can manipulate and analyze database data without impacting the database server. Once you have the data in the rich client, you can do high-performance analysis of the data—including sorting, filtering, and querying—without expensive server calls. In this article we will show you how to use DataSet, DataView, and XmlDataDocument to make your rich clients work with database data in a disconnected way."