Given yesterday's problem with VSS, I felt like it was important to find a solution.  I found a prerelease update to Visual SourceSafe 2005 that is supposed to get VSS to work with Visual Studio 2008 Beta2.  I downloaded it, but it doesn't resolve my problems at this point.  I *bumped* an email about this within the ASPInsiders.  Scott Guthrie was kind enough to grab it and send it onto some others.  Hopefully, something will come back about this.  BTW, I can't say enough kind things about ScottGu.  He has so much energy for the community!  I'd like to develop this application with VS.NET 2k8, but if I can't get some simple source control working, and I am not going to deal with TFS, for a small project running on my laptop, I'll have to go back to VS.NET 2k5 with that project.  Its not a big deal, but does throw a wrench in the works.  Honestly, any type of source control would do.  I just need versioning and to have it to work

Here is the url to the update for VSS 2005: http://www.microsoft.com/downloads/details.aspx?FamilyID=faf41edd-924d-449f-aefc-9c86dd499720&DisplayLang=en

There is a note on the bottom of the download page that you will need to register the file tdnamespaceextension.dll.  When I registered that dll, some of the error messages in VS.NET 2k8 went away, but I am still unable to bind a project to a database in VSS.

Finally, resolution on the subject.  The problem seems to be a security issue related to Vista and VS.NET 2k8 that is particular to my laptop.  The problem seems to be that the VSS database was within the "Program Files\Microsoft Visual SourceSafe" directory.  When I changed the security settings on the local Users group to allow all users access to the rights.dat file, the problem went away.  Life is much better.

I am working on my talk on .NET 3.5 / Visual Studio 2008 in Huntsville, AL on August 14th.  More info to come about this later. 

I started my first debug session today.  I hit F5, and up posts a data collector window.  I was thinking, "wtf is that?" Apparently, there is much more profiling and collecting of application performance in Visual Studio 2008.   This is good stuff.  After all, there are too many poorly performing applications out their in the world.  Oh the humanity.  Start reading about application profiling here:
http://blogs.msdn.com/colinth/archive/2007/07/27/visual-studio-2008-beta-2-now-with-some-of-my-code.aspx
http://blogs.msdn.com/ianhu/archive/2007/07/17/the-visual-studio-profiler-data-collection-control-part-1-excluding-application-startup-time.aspx 

When you go into the debugger in VS.NET 2008 when hitting a web application, you get a list of all the files loaded by that page.  You can go into the files and set breakpoints in the javascript.  This is great.