October 29, 2009
A few weeks ago I finally decided to sign up for TechEd 2009. This year, with the start of Sparkles I wasn’t planning to attend, but hey: some parties are not to be missed. After all, the VSTS sessions look very promising with top speakers and it’s a week I can spend to focus 100% on the VS2010 Beta 2 release I have installed on my laptop.
My scheduled VSTS agenda for TechEd 2009:
- VSTS 2010: A Lap around the Developer and Tester Experience (Brian Harry)
- VSTS 2010: A Lap around the New Project Management, Architecture, and Governance Capabilities (Brian Harry)
- Source Code Management with TFS 2010 (Brian Harry)
- An Agile Talk on Agility (Peter Provost)
- Software Testing with VSTS 2010: Part 1, an Introduction (Brian Keller)
- Software Testing with VSTS 2010: Part 2, Making It Real (Brian Keller)
- Tools and Agile Teams (Stephen Forte)
- Microsoft Visual Studio Team System 2010 Team Foundation Server: Become Productive in 30 Minutes (Brian Keller)
- How Microsoft Does It: Internal Use of TFS and Microsoft VSTS for Software Development (Stephanie Cuthbertson)
- Doing It Right: Planning and Tracking Projects with TFS 2010 (Stephanie Cuthbertson)
- Successfully Administering and Running TFS 2008/2010 (Neno Loje)
- Architecture Discovery and Validation with VSTS Architecture Tooling (Peter Provost)
- You Are Still Using Microsoft Visual SourceSafe? (Neno Loje)
- Microsoft Visual Studio Team System “Unplugged” (Stephanie Cuthbertson)
October 27, 2009
Wow! This is great! Tonight I just wanted to find out if and how it would work …
This is what I did with Beta 2 of Visual Studio 2010 Ultimate and TFS 2010 Basic on my Win7 laptop:
- created a new Team Project
- added a new solution with a C# Library Project to the Team Project
- added a default Team Build to build the C# Library Project
- added a new solution with a C# WPF Project to the Team Project
- referenced the library assembly (file reference to dll) into the C# WPF Project and called a method on a class in that assembly
- set a breakpoint on that line and hit F5 to start/debug the WPF application
- pressed F11 (Step Into) when breakpoint was hit
Guess what?! Yes, Visual Studio 2010 was immediately stepping into the source file of the C# Library Project! Sweet!
I remember that it took me some time to get this working for TFS2008!
When you create a new Build Definition with TFS2010, the Index Sources option is set to true by default and this will make sure that source indexing is part of the build.
I took a peek into the DefaultTemplate.xaml file in the BuildProcessTemplates folder and found out that the Index Sources and Publish activity is indeed completely baked in! I love it already!
October 20, 2009
Since yesterday, MSDN subscribers are able to download Visual Studio 2010 Beta 2. I’m really excited about this release! Lots of important improvements in different areas of software development practices. I’m looking forward to further test and evaluate this release …
Today I did install already a Hyper-V image with a full blown Team Foundation Server 2010 Beta 2. Installation was absolutely flawless! First I installed IIS 7.0 and SQL Server 2008 on Windows Server 2008 R2. After that I was able to start the setup wizard of Team Foundation Server 2010 that’s now split into an installation part and a configuration part. The first part only copies the required files to the server while the second part takes care of the configuration. I did choose for the Standard Single Server wizard which guided me towards an easy and understandable configuration of the different TFS components. Thank you guys for keeping it simple! Other wizards are provided for more complex scenarios.
What I extremely like is the TFS Administration Console that pops up after closing the configuration wizard! It gives you a nice overview of what’s installed and you can control the project collections, build controllers, service accounts, … A lot of stuff that was managed via the command line in previous versions of Team Foundation Server. Good stuff! This Administration Console will probably evolve even more in the future.
You can start it now manually via Start > Programs (I do remember that with Beta 1 it was a snap-in for Microsoft Management Console).
So, that leaves me to install Visual Studio 2010 Ultimate Beta 2 for starting up a first development project. Note that Team Explorer is now part of the Visual Studio client edition and doesn’t need to be installed separately. Every Visual Studio edition will have a Team Explorer to connect to a Team Foundation Server. Very good!
You might have noticed that Team System did not come up once in this post up till now. I need to recover from the first shock, but the Team System moniker will eventually disappear. Back to the Visual Studio brand! I do not want to go deeper into this holy discussion but I assume there might be good reasons to take this drastic decision. In the end the decrease of different Visual Studio editions should make it more clear for all type of stakeholders. Agree or not … we will have to live with it! The decision has been made!
- VS 2010 Professional
- VS 2010 Premium
- VS 2010 Ultimate
Read more about the different editions here. The Ultimate Edition will contain *everything*, including IntelliTrace (Historical Debugger) and the Test and Lab Manager which won’t be part of the Premium edition.
There’s also an interesting limited offer for existing MSDN subscribers.
Let’s have some fun! In the coming days I will also try out a TFS Basic installation on a Windows 7 OS …
October 11, 2009
I noticed some interesting changes for the Build Retention Policies in TFS2010 (Beta 1):
- possible differences between retention policy for triggered and manual builds vs private builds
You will be able to set another retention policy on private builds: builds that are run by the enabled Gated Check-in trigger.
- extra What to delete column
You will be able to specify more in detail what information must be deleted when the retention policy kicks in.