VS 2008 and TFS 2013: It Works… if You Can Risk It

VS 2012 LogoNevermind my 20-month hiatus. Life happened. Now I’m back. On with the post.

With the release of TFS 2013 (huzzah!) came another round of regression testing where I work. Of note this time around was the deprecated support of Visual Studio 2008.

Per Microsoft’s own documentation:

To connect to Visual Studio Team Foundation Server 2013 from Visual Studio 2008 or Team Explorer for Visual Studio 2005 Team System requires installation of Microsoft Source Code Control Interface (MSSCCI) Provider 2013. This configuration supports users in accessing Team Foundation version control from these earlier client versions.

In general, I’m happy to see Microsoft deprecating support of three-generation-behind products – I was elated when they dropped VS 2005 support in TFS 2012 – but this time the reaction was mixed. Here’s why.

Yes, Visual Studio 2008 is a three-generation-behind product and, with Visual Studio’s multi-targeting support, upgrading the IDE has become increasingly trivial. My concern is not with Visual Studio. Instead, it’s with BIDS.

BIDS 2008 is VS 2008

Yes, BIDS. As in Business Intelligence Development Studio, the VS 2008 Shell that ships with SQL 2008 and SQL 2008 R2.  SQL 2008 R2 is technically only one generation behind the latest release, yet it relies on the VS 2008 shell for Business Intelligence development (such as SQL Reporting Services, SSIS and SSAS projects).  With the release of SQL 2012, the product team packaged a new version of BIDS, dubbed SQL Server Data Tools 2012 (which runs on the VS 2010 shell – confused yet?).

Here’s the rub.  While you can develop SSRS reports in SSDT 2012 and deploy them to SQL 2008 (or R2) environments, you cannot do the same with SSIS and SSAS packages. For whatever reason, the SQL team coupled their design tool versions with the SQL server run-time environment. So SSIS 2008 packages must be deployed to SQL 2008 environments; SSIS 2012 packages to SQL 2012, etc. Again, per the MSDN documentation:

Use the SQL Server 2008 version of Business Intelligence Development Studio to develop and maintain packages that are based on SQL Server 2008 Integration Services (SSIS).

Now, my company has made a pretty good investment in business intelligence solutions, including SSIS and SSAS. So for developers who are still running SQL 2008 R2 environments, what does this mean to their productivity if we migrate to TFS 2013? Must they undergo the slow torture that is MSSCCI?

Is it Really Broken?

So back to the title of this blog… In regression testing TFS 2013, I wanted to see what all would happen if I tried to connect a TE 2008 client to our TFS 2013 RTM instance. Would Microsoft have a friendly error message waiting for me? Would things try to work only to crash and burn horribly? My, what surprises were in store for me.

For my testing environment, I was running VS 2008 w/ SP1 with BIDS 2008 R2 installed as well as the TFS 2012 GDR. And everything. Worked. Normally. Or as normally as it had run under TFS 2012.

  • Version control worked as expected (check-in, check-out, branching, labeling, shelving, etc.)
  • Work Item tracking opened as usual. I could create and edit work items. And I could view any flat-view queries as well.
  • TFS builds kicked off as well, though I didn’t try to create any builds from the 2008 client.

So it looks like Microsoft’s statement that VS 2008 requires MSSCCI is not entirely true.  Not that I’m complaining. As much as I’d like VS 2008 to undergo the MSSCCI treatment, I can’t say the same for BIDS. Of course, while it technically works, don’t expect Microsoft to support it.  That’s the risky part that you’ll have to figure out whether to take on. Best case, everything continues to work as expected. Worst case, something breaks and you have to install the 2013 MSSCCI. Or get off VS 2008 / SQL 2008. Though one would be considerably easier than the other.

Book Recommendation: Professional Team Foundation Server 2010

The latest addition to my technical book collection is Professional Team Foundation Server 2010. This is a “must have” book for anybody who is a TFS admin or even a Team Project admin.

I’m about two-thirds of the way through the book and I honestly can’t go more than one or two pages without finding some new tip or piece of information to try out in my own environment. The great strength of the book comes from the wealth of experience the authors drawn upon when discussing each of the topics.

The book itself takes a comprehensive look at the many aspects of Team Foundation Server, including version control, work item tracking, reporting, process templates, build, and administration. The administration content is extremely useful and the topic is given a full third of the book. For anybody who works in an enterprise environment or who has to deal with high availability and disaster recovery systems, you’ll be glad to see chapters devoted specifically to addressing these topics.

Lastly, for anybody interesting in pursuing the Microsoft certification for Team Foundation Server 2010 (exam 70-512), this has been touted as the unofficial training book.

TFS’ Lack of Support for Linked Reports – Bah!

I posted this issue on the MSDN forums, but wanted to cross-post it on my blog as well.

One of my recent challenges at work has been around building custom reports against TFS, specifically around version control. TFS provides a lot of nice reports related to Work Item Tracking and Build Automation, but very little around version control. (For example, how long has something been checked out of TFS?)

While I understand the big-picture reason for this – code changes should be linked to work items to allow for requirements traceability – it is also a common scenario for new development teams to start out using TFS solely for version control.

In tackling these custom reports, I was looking for a way to deploy a single report and have it be available in each Team Project as a linked report (a capability available in SQL Reporting Services). This provides improved maintainability in that I can deploy updates and fixes to a single deployment target rather than deploy copies of reports to each Team Project on my Collection or server.

Based on my research, I concluded the following:

Linked Reports do work when being viewed on the Reporting Server directly.

On the Report Server, I created a new folder under /TfsReports/DefaultCollection, called “SharedCollectionReports“. This is where I would store all of my reports that are shared across team projects in a collection. I then used Visual Studio / BIDS to deploy my RS report to this new location.

From here, I created a linked report to two different Team Projects and set up unique report parameters for each (but still using the same base report).  I confirmed that each report returned data unique to its parameters.

Linked TFS Report in SQL Reporting Services

Linked TFS Report in SQL Reporting Services

I then made a change to the report and re-uploaded a newer version of the base report to the “SharedCollectionReports” folder and confirmed that the linked reports in both team projects reflected the changes.

So, this functionality does work as expected when accessed directly from the Report Server.


Linked Reports are NOT visible in Team Explorer

Unfortunately, when opening up the Team Project in Visual Studio Team Explorer, the linked report does not show up.

Team Explorer not displaying linked reports

Linked report missing from Team Explorer view.

Unfortunately, it looks like this has been a known issue for a while, based on a related MSDN thread I found.

I’ve posted a feature request on the Visual Studio/TFS User Voice site. If this is a feature you would also like to see added to TFS, please vote for this feature.

Keeping Up with TFS 2010 Service Packs and Updates

Grant Holliday posted a really nice reference guide yesterday explaining the various Service Packs and Hotfixes that are currently available for TFS 2010 and its underlying components. This is something I had been searching for recently to ensure my own TFS installation was up-to-date. It is very thorough and highlights several aspects of the TFS infrastructure.

Thanks for putting this together Grant!

Changing Roles

This week, I made the transition to a new team within my company.  It’s good to make a change every once in a while so that things don’t get stale.  I’ve heard it said that, as soon as you are so comfortable in your current role that you’re afraid to make a change – that’s when it’s time to try something new. 🙂

My new role is a bit more technical than my last and will give me more time to dig deeper into the latest .NET technologies out there.  I’m also going to be doing a bit more TFS administration. I’m looking forward to seeing how TFS works “under the hood” and be able to play around with all the cool new ALM features that are getting baked into the product.

I know I’ve been pretty lackadaisical lately with my posts.  To tell you the truth, I just wasn’t getting a lot of time to play with the tools, technologies and practices that this blog is all about, and I just didn’t have anything noteworthy to write about. With this new role change, I expect that will change.

Most of you have visited this blog for TFS-related content. Look for more of that (and other topics) to come!