Microsoft Downloads page was just updated with the new Microsoft Visual Studio Code Name “Orcas” Development Tools for .NET Framework 3.0 RC1.
The download is availble here.

From the readme:

Welcome to the release notes for the .NET Framework 3.0 RC1 synchronized release of the Microsoft Visual Studio Code Name “Orcas” Community Technology Preview - Development Tools for .NET Framework 3.0®!

This software package is not planned for final release or support. Most of the technology incorporated in this package will be included in the Code Name “Orcas” release of Visual Studio, and that is where it will reach final release quality, and will be supported as part of that released Visual Studio product.  The full Code Name “Orcas” release of Visual Studio will contain additional .NET Framework 3.0 development technology.  We are providing access to some of this .NET Framework 3.0 development technology early, so customers using Visual Studio 2005 have an improved development experience for .NET Framework 3.0 applications.

Included in this CTP release is the Windows Presentation Foundation visual designer (”Cider”) for Visual Studio. The Cider designer is very limited in capabilities in these early technology previews, but does work for very simple layout tasks, can serve as a preview for editing more complex WPF forms, and preserves XAML when moving between the XAML editor and the designer. More information about the Cider designer is on the Channel9 wiki, and questions can be directed to the WPF Designer (”Cider”) forum on MSDN.

If you have problems using this package or with Windows Presentation Foundation (”Avalon”) or Windows Communications Foundation (”Indigo”) development, please utilize the newsgroups and forums that are available to get help from the community, including Microsoft employees that participate in these newsgroups and forums:

• .NET Framework 3.0 Development Newsgroups: http://msdn.microsoft.com/Longhorn/community/newsgroups/default.aspx
• Visual Studio Forums: http://forums.microsoft.com/msdn/

Please note that this release only works with the Final release of Visual Studio 2005, and the RC1 release of the .NET Framework 3.0 runtime (which is included in Windows Vista RC1) and the RC1 release of the Windows SDK. Updating any of these without also updating this package will cause problems.

Technorati : .NET, .NET 3.0, Microsoft, WF, WinFX
Del.icio.us : .NET, .NET 3.0, Microsoft, WF, WinFX
Ice Rocket : .NET, .NET 3.0, Microsoft, WF, WinFX

Finally found the definite answer to the question raised in the following post.

The following link at MSDN describes all the breaking changes when migrating from .NET 1.1 to 2.0 and sort them by categories.

I’ve been using nGallery for quite a while and I can’t say it is perfect. In fact, I had to edit some of its code just to get it to work (nGallery tries to create a new folder for each album which is not possible in most web hosts due to security settings - File.CreateFolder has to have access to the entire folder path - d:\host internal folder structure\my web\gallery\albums\…)

nGallery has become part of Community Server which requires a database to work. I believe a lot of people out there would still like to use an Xml based personal gallery to save the DB costs (like they use dasBlog instead of .Text etc.)

I’ve been toying with the idea of starting my own web gallery project… Maybe I’ll call it dasGallery

Someone asked me if there’s a publication of a list of incompatibilities between .NET 1.0 and 2.0. I tried searching for this info but all I could find was articles about migrating between ASP.NET versions and and about System.Xml migration.

Anyone can recommend of other helpful migration resources?

AspAlliance posted an article listing free components for ASP.NET 1.1 by categories (navigation\UI\data etc.)
I found some great stuff I didn’t know of in this article so check it out at : http://aspalliance.com/652

I especially likes ComponentArt’s free Snap Control and obout’s Calendar.

Here’s an update regarding the recently discovered ASP.NET volnerability.

Microsoft has released an ASP.NET HTTP module that Web site administrators can apply to their Web server. You can download the installer for this new module here.

The KB article is here.

A serious vulnerability issue that affects ASP.NET was recently discovered.

There’s a bug in ASP.NET’s canonicalization process which can allow an attacker to slip past the UrlAuthorizationModule by using a backslash instead of a forword slash.

For example, an unauthorized attacked might be able to access a secured directory using the following URL (notice the ‘\’ between “something“ and “secure“:

http://www.ekampf.com/something\secure/securedPage.aspx

Apperantly this isn’t reproducable in Windows2003 (the built-in URLScan capability is fixing the URL before it gets to ASP.NET) but earlier platforms are still vulnerable.

Microsoft has posted an article detailing steps that you can take to protect yourself in the meantime, while they work on a patch.