Whidbey & Longhorn Project Name Restrictions

This is just a reminder that strange things can happen when you try to name a project with an existing class in the .NET framework.  For example, for creating a new sample test project, I usually give it some sort of simple descriptor and put it in my HD's example code folder.

I was playing around with some very simple animation, and wanted to keep around a sample of animations based on paths, so I name my project PathAnimation, put some code in, attempt to compile, and get turned down because the PathAnimation class already exists in the 1.2/2.0 framework... whoops!