This post originated from an RSS feed registered with .NET Buzz by Sascha Corti. Original Post: Me running Longhorn Feed Title: Console.WriteLine("Hello World"); Feed URL: http://www.corti.com/WebLogSascha/blogxbrowsing.asmx/GetRss? Feed Description: A technology blog with a focus on the .NET framework, the Visual Studio .NET tools and the Windows server platform with of course the normal weblog-noise on what's happening in the industry and reviews of the latest geeky gadgets. Latest .NET Buzz Posts Latest .NET Buzz Posts by Sascha Corti Latest Posts From Console.WriteLine("Hello World");

After testing PDC Longhorn in Virtual PC 2004 on my laptop (which does run perfectly well, being just veeeeery slow), I have decided to dedicate a relatively new desktop system to the new OS. Feels a *lot* better.

I then added all the required OS services (like IIS for ASP.NET), installed the PDC Whidbey build and after that (!) the Longhorn SDK, the Tablet PC SDK and the Pocket PC 2003 SDK, all included on the Longhorn DVD - this way, all the new project types get properly registered with Visual Studio .NET.

Things work perfectly well and the only problem I have encountered so far is the ".NET Framework Configuration" application that does not parse the HTML generated in the right pane.

My first Avalon (XAML) application is compiling and running just fine (even though it is still far from spectacular).