So Rick LaPlante has had a good summer, that's good to hear - my summer has been one great big uncetainty void, what with not having a permanent place to live, starting a new job, having the baby learning and growing at an ever increasing pace... not that any of these things are bad (though I'll be glad when I move into my new place in a couple weeks), just uncertain.  So, I started this blog entry to poke at Rick for telling us about his summer and then dropping the big news if we managed to get through the first half of his entry, and here I am, having now done the same thing.

SO, the big news from Rick:

I’m excited to say that today we signed off on the the last few issues and started the release process for the next Community Technology Preview.  You should be able to get the bits off of MSDN later this week.  ...  This will be a big CTP because it will include the Team Foundation server installation (which I know many of you are very anxiously awaiting).  It will also be based on the Whidbey Beta 1 bits so you will finally have a matched set of Beta 1 compilers/editors/frameworks, and the Team System all in 1 place.  Because it’s based on the Beta 1 bits, the official title of the release will be “Visual Studio 2005 Beta 1 refresh with the Team System”.

Sweet.  Having just spent the last week driving the effort to use NAnt, NUnit, FxCop, and NCover all wrapped up nicely by CruiseControl.Net to create a fully automated, continuously integrated build environment - it should be interesting to see how VS Team System will match up to the ease of VS.Net integration (ok, duh, MS'll win this one), ease of server setup (CruiseControl.Net was much easier to set up than I was prepared for - I'll be blogging my findings once I'm done), and most crucially, ease of developer acceptance - once the NiftyNewToy aura has worn off, how much (or how little) of a PITA will it be for a developer to use VSTS?  Right now with my CC.Net setup, all a developer *has* to do is check something in - the tests, reporting, and redistribution of binaries and documentation is all automated.  Of course, the developer *should* run tests before he checks something in - but we all know that doesn't mean it'll happen 100% of the time.

- G