I’m pretty excited because this week is one of my absolutely favorite weeks of the year.  I’m heading to the Microsoft campus in Redmond to attend the Microsoft MVP Summit where MVPs around the world travel in to have deep discussions about Microsoft products. 

I especially enjoy having been a Visual Studio Team System/ALM MVP the last few years because the other Team System MVPs are really one of the best groups of colleagues out there!  We have deeply heated discussions about all sorts of topics but it’s always constructive and deeply engaging. 

We also happen to be associated with a super product group that really values the feedback we give and it’s truly reflective in the great work that they craft together in the final product.  It’s our time to be the voice of the customer and the product team genuinely appreciates the insight.

Is there something about Visual Studio ALM (Team System) or TFS that you’d like me to make sure I bring up?

Even though I won’t be able to report to you what we end up talking about (since we are all under NDA for this event,) I can only tell you that if this year’s time spent is anywhere near the past several years then our talks about Visual Studio ALM features and Team Foundation server is going to be awesome!

Take care,

Ed Blankenship

I’ve been hearing this question quite a bit…  “Can I collect an IntelliTrace log in Production?”  This would be a really good idea especially now that there is a standalone command-line utility, IntelliTrace.exe, that you can run to collect IntelliTrace log files.  Unfortunately, it looks like the Visual Studio 2010 Licensing White Paper answers that question for us on page 28:

The IntelliTrace DDA and/or IntelliTrace.exe cannot be used:

• On a device or server in a production environment.
• For purposes of system or application monitoring.
• In non-interactive scenarios other than as part of an automated test or debugging-data collection session.

Bummer! :(  Honestly, I imagine that has to do with something around how IntelliTrace works and Microsoft doesn’t feel comfortable the impact it may have on running Production environments.  Just my conjecture though…

You’ll notice that you can use IntelliTrace in other instances though; most notably on development & test environments!

The IntelliTrace diagnostic data adapter (DDA) and/or IntelliTrace.exe can be used for test and debugging purposes:

• As part of an interactive test or debugging session.
• As part of an automated test or debugging-data collection session that is authored by a licensed user and triggered by the same or another licensed user.

You can even share IntelliTrace files between two companies as long as both companies are properly licensed!

IntelliTrace files may be shared among two or more companies as long as all users capturing and debugging IntelliTrace files are licensed with either Visual Studio 2010 Ultimate or Visual Studio Test Professional 2010, depending on the activities they are performing. For example, a company can share IntelliTrace files with an external development consultant. Similarly. a company can use an external company for testing purposes and debug IntelliTrace files provided by that vendor.

Here were the common scenarios mentioned in the licensing white paper.  See if you happen to fit into one of them:

Example 1: Finding a defect in a test environment Company A is building a Web application. All the developers are licensed for Visual Studio 2010 Ultimate with MSDN, and the testers are licensed with Visual Studio Test Professional 2010 with MSDN. During a test run a defect is discovered in the test environment that is difficult to reproduce in a development environment. The test machines have previously been configured with the Visual Studio Test Agent 2010, which includes the IntelliTrace DDA. The tester uses the Microsoft Test Manager to execute the test case with the IntelliTrace diagnostic data adapter (DDA) enabled. When the defect is encountered, the tester files a new bug, with the IntelliTrace files from each of the test machines is automatically attached to the bug. When a developer opens the bug using Visual Studio Ultimate, he or she can open the IntelliTrace files and step through the execution.

Example 2: Working with an external consultant In Example 1, Company A uses an external consultant to help with development. If the external consultant is licensed for Visual Studio Ultimate, he or she can open and debug the IntelliTrace files provided by Company A.

Example 3: Working with an external test vendor In Example 1, Company A uses Company B as an outsourced test vendor. The two companies can work together using IntelliTrace as long as all developers at Company A and all testers at company B are licensed appropriately.

I’m not sure what the minimal technical footprint is to get IntelliTrace.exe to collect an iTrace file just yet but my answer right now will be to have one of these installed:

• Visual Studio 2010 Ultimate
• Visual Studio 2010 Test Professional
• Visual Studio 2010 Test Agents (additional software) <--- probably the smallest impact to a system

If I find out some more information about this scenario, then I’ll be putting together a future blog post!

Take care,

Ed Blankenship

The Release Candidate for Visual Studio 2010 and Team Foundation Server 2010 was made available a few days to MSDN Subscribers.  It’s now going to be made available to the rest of the world today:  http://go.microsoft.com/fwlink/?LinkID=151797

The first impression I have is that Visual Studio has been super super snappy and lot more purple :)  You can really take advantage of all of the performance work that has been performed by the product groups.  What’s funny is that I have was too slow several times to grab the screenshot below! :)

I have also done several TFS 2010 Beta 2 to RC upgrades so far and all of them have gone super well including a super complex setup that we have at Notion Solutions.  If you are planning on upgrading from Beta 2 to RC, be sure to read the Upgrade Guide before you get started.

As with the Beta 2, the RC of TFS, Visual Studio, and .NET Framework 4 can be used in production with a “Go-Live” license.  Be sure to check out Jeff Beehler’s blog post that has more information about the “Go-Live” license including how to register for complimentary support in case you need it.

After you get everything installed and used it for a few days, please be sure to give feedback about whether you think the release is ready to go by taking the RC survey.  There is only a limited time to give any feedback and the bar is high for things that will change before RTM so don’t delay!

Ed Blankenship

Updated – 8/19/2011 – New Rollback Features Available in the UI with TFS 2010 Power Tools (See Below for More Details)

One of the new features for TFS 2010 Version Control is the ability to rollback or undo a changeset or check-in inside the product and see it as a new pending change type (and new change type in the history) inside Team Explorer. This feature has been available in TFS 2008 but you had to use the TFS Power Tools. The only gotcha for the TFS 2010 implementation is that you have to use the command-line application tf.exe to actually perform the rollback operation. More information about the tool is available here in the MSDN Library: http://msdn.microsoft.com/en-us/library/dd380776(VS.100).aspx

The syntax is:

tf rollback /changeset:changesetfrom~changesetto [itemspec] [/recursive]
[/lock:none|checkin|checkout] [/version:versionspec]
[/keepmergehistory] [/noprompt] [/login:username,[password]]

tf rollback /toversion:versionspec itemspec [/recursive]
[/lock:none|checkin|checkout] [/version:versionspec]
[/keepmergehistory] [/noprompt] [/login:username,[password]]

Versionspec:
Date/Time D"any .Net Framework-supported format"
or any of the date formats of the local machine
Changeset number Cnnnnnn
Label Llabelname
Latest version T
Workspace Wworkspacename;workspaceowner

Rollback Available in the UI Now

If you have the August 2011 or later version of the TFS 2010 Power Tools installed, you now have the ability to fire off a rollback straight from Team Explorer without having to use the command-line approach.  The main way would be to fire it off from the Source Control Explorer window.

However, you can start the rollback process from the Changeset History window as well.

Ed Blankenship

As promised, I have published the slides from my PowerPoint Deck for my talk on Saturday at the Columbia Code Camp.

Thanks to everyone I bugged during the week before to grab a hold of these slides! Contact me (using the contact form on the website) if you'd like to get a copy of the PowerPoint deck.

Ed Blankenship

Tomorrow, I’ll be presenting in this month’s geekSpeak about migrating from Visual SourceSafe to Team Foundation Server 2010.  I’m sure we’ll get through the VSS content pretty quickly so with the time left we’ll talk about new branching & merging features, branch visualization, and gated check-in.

In this geekSpeak, Microsoft Most Valuable Professional (MVP) Ed Blankenship discusses migrating source code from Visual SourceSafe, including the history. There has not been a better time to migrate to the newest Microsoft source control offering, Microsoft Visual Studio 2010 Team Foundation Server, because Microsoft Visual SourceSafe support is ending soon and Team Foundation Server will be part of Microsoft Developer Network (MSDN) subscriptions in 2010. Ed discusses specific version-control features to help you become more productive like branching and merging visualization, annotate, shelving, and gated check-in. This geekSpeak is hosted by Glen Gordon and Brian Hitney.

Registration for the event available here:  http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032438525

BTW – The end-of-life support date for Visual SourceSafe is mid-year 2011.  Don’t get stuck on an unsupported product :) especially one that’s holding your source code!

Update:  The recording of this presentation is now available on Channel 9 here:  http://channel9.msdn.com/shows/geekSpeak/geekSpeak-Recording-Migrating-to-Team-Foundation-Server-from-Visual-SourceSafe/ .  Sorry about the dropped call in the middle of the presentation.  Also, here’s some links that I mentioned during the talk:

• Whitepaper – “From VSS to TFS”:  http://sstjean.blogspot.com/2006/10/document-from-vss-to-tfs-introduction.html
• Whitepaper – Exposing TFS to the Internet:  http://blogs.msdn.com/ablock/archive/2009/08/24/exposing-tfs-2010-beta-2-to-the-internet.aspx
• Visual Studio 2010 and .NET 4.0 Training Kit (Labs, Videos, Slide Decks, etc.): http://www.microsoft.com/downloads/details.aspx?FamilyID=752CB725-969B-4732-A383-ED5740F02E93&displaylang=en

Ed Blankenship

I’m going to be doing a session at the Columbia Code Camp about Visual Studio 2010 Ultimate and Team Foundation Server 2010 and really looking forward to it!  Looks like Cameron Skinner already beat me by speaking out in Charlotte earlier this week but hopefully I’ll still have some people who haven’t seen the new features just yet!

Check out the other 32 sessions in the Agenda and be sure to Register.  Already looks like a big crowd so I’m hoping it ends up being successful.  There’s a lot to get through for a one-hour overview session but I plan on sticking around to chat if anyone ends up having any questions that we can’t get answered during the presentation.

Session:  Lap Around TFS and Visual Studio 2010 Ultimate

Time:  11:15 AM – 12:15 PM  (Right before lunch!)

Track:  Framework

Room:  Amoco Hall (1C01)

Location:  University of South Carolina, Swearingen Building, 301 Main St., Columbia, SC 29201

Cost:  Free!

Update: Slides are now available below.

Ed Blankenship

I'm pleased to announce that we now have pricing information that is publicly available for the Visual Studio 2010 and Team Foundation Server 2010 products!  Remember, these are Retail prices and if you are in a company you should never be paying retail :)  Always talk to your Microsoft Sales team and ask for volume licensing deals.

Also, if you didn’t hear, a production license for TFS 2010 and a TFS 2010 CAL is included with every MSDN subscription!

Suggested Retail Pricing (USD) for Visual Studio 2010

* Subscription contents vary by purchased product.

Ed Blankenship

Thanks to the Visual Studio ALM Rangers, we have a new release of the TFS Branching Guidance!  Think of it like TFS Branching Guidance 3.0… it was developed specifically for TFS 2010 including tidbits on best practices using all of the new branching & merging hierarchy and visualizing change features.

I often talk about branching & merging strategies with my clients and it’s always great to have some diagrams and content to go back to and leave with them so that they can delve into Configuration Management a little more.

Head on over to their CodePlex site:  http://tfsbranchingguideiii.codeplex.com/

Project Description
The purpose of this project is to build some insightful and practical guidance around branching and merging with Visual Studio Team Foundation Server 2010. The new release focuses on Hands on Labs and includes lots of lessons learnt from the community Q&A.
Visual Studio Team Foundation Server Branching Guide 2010
Branching and merging of software is a very large topic. It is an area where there is a lot of maturity in the software industry. This Ranger solution focuses on applied and practical examples of branching that you can use right now. The 2010 release includes discussions around branching concepts and strategies but also focuses on practical hands-on labs.
Visual Studio ALM Rangers
This guidance is created by the Rangers who have the mission to provide out of band solutions for missing features or guidance. This content was created with support from Microsoft Product Group, Microsoft Most Valued Professionals (MVPs) and technical specialists from technology communities around the globe, giving you a real-world view from the field, where the technology has been tested and used.
What is in the package?
The content is packaged in 8 separate zip files to give you the choice of selective downloads but the default download is the TFS_Branching_Guide_2010_Complete_Package_v1 if you are interested in all parts.

• TFS_Branching_Guide_Main_2010_v1.zip --> Start here
• TFS_Branching_Guide_Scenarios_2010_v1.zip
• TFS_Branching_Guide_Scenarios_2010_Poster_v1.zip
• HOL_Quick_Start_Basic_Branch_Plan_2010_v1.zip
• Lab_Files_HOL_Quick_Start_Basic_Branch_Plan_v1.zip
• TFS_Branching_Guide_Q&A_2010_v1.zip
• TFS_Branching_Guide_Diagrams_2010_v1.zip
• TFS_Branching_Guide_2010_Complete_Package_v1

Team
Bill Heys, James Pickell, Willy-Peter Schaub, Bijan Javidi, Oliver Hilgers, Bob Jacobs, Sin Min Lee, Neno Loje, Mathias Olausson, Matt Velloso
How to submit new ideas?
The recommended method is to simply post ideas to the community or to contact the Rangers at http://msdn.microsoft.com/en-us/teamsystem/ee358786.aspx.

Ed Blankenship

Tomorrow, I’ll be presenting in this month’s geekSpeak about migrating from Visual SourceSafe to Team Foundation Server 2010.  I’m sure we’ll get through the VSS content pretty quickly so with the time left we’ll talk about new branching & merging features, branch visualization, and gated check-in.

In this geekSpeak, Microsoft Most Valuable Professional (MVP) Ed Blankenship discusses migrating source code from Visual SourceSafe, including the history. There has not been a better time to migrate to the newest Microsoft source control offering, Microsoft Visual Studio 2010 Team Foundation Server, because Microsoft Visual SourceSafe support is ending soon and Team Foundation Server will be part of Microsoft Developer Network (MSDN) subscriptions in 2010. Ed discusses specific version-control features to help you become more productive like branching and merging visualization, annotate, shelving, and gated check-in. This geekSpeak is hosted by Glen Gordon and Brian Hitney.

Registration for the event available here:  http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?culture=en-US&EventID=1032438525

BTW – The end-of-life support date for Visual SourceSafe is mid-year 2011.  Don’t get stuck on an unsupported product :) especially one that’s holding your source code!

Ed Blankenship