Get this error message after installing the "recent MS03-32 Security Update for Internet Explorer" security patch, if you are running .NET framework 1.0 and Windows XP professional.

------

Update (03/17/04) -- got similar weird problem when trying to create ASP.NET web service on my local machine. Thought it was a problem with hitting port 81, but 80 wasn't working either. Found some recent event logs complaining about failing to log in as ASPNET account. Looked at account list, and ASPNET was set to "force user to change pwd" -- weird - doubtful that's correct.

Found my fixup cmd file, updated it to ignore the warning about .NET 1.1, and ran it.
Resets the ASPNET account with new random password, and fixes all settings for IIS to use .NET 1.1

Create web service works now!

-----
Update (11/24/03) -- got this same problem after recent Windows Update (not sure of exact security patch number). Ended up running this same fixup.cmd, even though I'm running .NET 1.1 Modified fixup.cmd to allow for fixing .NET 1.1 -- changed directory where it operates to the 1.1.4322 version directory.
I have uploaded my version here
-----

Thanks to this article at ASP.NET site, we have the solution.

Problem stems from an issue with the ASPNET account used to run the anonymous asp.net requests. Paraphrasing, this fix does the following:

• stops IIS and ASP.NET services
  
• deletes and recreates the ASPNET account with a known temporary password
  
• uses windows "runas" command to launch exe that creates the new ASPNET user profile
  
• re-registers ASP.NET, this creates a new random password for the account and applies ASP.NET access control settings for it
  
• restart the IIS service
  

keywords: server application unavailable asp.net 1.0 security patch

Longhorn: Background Spell Checking for Avalon TextBoxes

My results here...

Don's Hello World Longhorn App which is a bit more involved than mine.
His uses code in a CDATA section of the XAML to produce Console.WriteLine( "Hello World" );

Sam Gentile shows us his quick and dirty Longhorn Hello World using cmd line and MSBUILD.
Writing your first Longhorn App
(btw, this works without the Longhorn SDK installed as described in the text -- my VPC environment for the time being has ONLY the Longhorn OS)

Running as least privilege, securing IIS, and other best practices.

Best Practices: How To: Secure Your Developer Workstation (.NET Framework Security)

running as non administrator (admin)

Graphics to follow a path, etc.
Vector Drawing for "Avalon"

Charles Petzold with a tutorial for MSDN mag.

Longhorn Developer Center: Code Name Avalon: Create Real Apps Using New Code and Markup Model

Should look into this and see what they did...

Logging Application Block (PAG Documentation)

Chris Anderson gives some inside info on how they got to where they are today with XAML.

His blog entry here

Comments from this dude about what makes for a good presentation (this one geared towards PDC)

ex: font sizes, how to start cmd prompt with such, etc.

Tips for a great presentation

Adamn Nathan from MS QA dept talked about this tool at PDC ("interop lessons learned" talk). Among other things, it will show you the calls to unmanaged code, garbage collections, etc.

GotDotNet User Sample: CLR SPY: Tool for using Customer Debug Probes (CDP)