Is NDepend 5 coming soon?


My Visual Studio 2012 is hinting towards the release of NDepend version 5. It's very soon after the release of 4.0, so it kind of surprised me a little. The download link isn't working yet, so no way to confirm...

The release notes page is also keeping its lips tightly together.

Connecting Visual Studio 2008 to TFS 2010, 2012 and the TFS Service Preview


Not all of us are so lucky that we can work with the latest bits at all time. Especially the folks that are in the Microsoft BI area always seem to be behind a release or two. This has always resulted in issues connecting to TFS from their version of Visual Studio.

For quite some time there has been a Forward Compatibility Patch for Visual Studio 2008 to connect to TFS 2010. But when it came to this patch, installation order was very important. If you wanted to use both BI Studio and connect to TFS the correct order would be:
  1. Visual Studio 2008
  2. Team Foundation Client 2008
  3. Visual Studio 2008 SP1
  4. Optionally: SQL Server BI Studio 2008 r2 (BIDS)
  5. Visual Studio 2008 Forward Compatibility Patch for TFS 2010
If you installed SQL Server BI Studio 2008r2 before installing Team Foundation Client chances are you wont be able to connect to TFS 2010 at all and you're most likely to get the following error message:
TF30335: The server name cannot contain the characters '/' or ':', or start with 'http://' or 'https://'
In the past the only way to correct this, was to remove the forward compatibility patch, remove Visual Studio 2008 SP1, repair Visual Studio 2008 and then re-apply them in the correct order. With some luck that would bring it back to life.

Now there's an easier solution. Just apply the new Forward Compatibility Patch for TFS 2012 and the Team Foundation Services after all of the earlier mentioned items. And as a bonus you'll be able to connect to the latest versions of TFS as well. On top of that it also fixes a few other issues.

Another important note: Visual Studio 2008 and below don't understand the concept of Project Collections. So when connecting to a TFS 2010 or later, you need to tag the project collection onto the url of the TFS Server.

For TFS 2010/2012 and newer this defaults to: https://[server]/tfs/[ProjectCollection]

For Team Foundation Service this defaults to: https://[youraccount]

To connect Visual Studio 2005 to TFS 2012 or the Team Foundation Services, check out this other post.

Red-Gate silently releases version of Reflector


It looks like Red-gate pushed out their new version a little in advance of the official announcement. When you download the latest version from their site you will get, the new version that includes
And something I hadn't seen before, though it has been in there for ages, PowerCommands! They're hidden in the options window (under tools, options) and it includes quite a few nice features. Copy as HTML, Copy as Text for code. Email snippet, Open in Visual Studio Version and the list goes on. They're not all as polished as the rest of the product, but some are quite useful. 

Enabling TFS Reporting requires installation on a Windows *Server*


I've been working on TFS report customization lately and today a new team member joined. We normally start by installing a local TFS instance with reporting enabled to be able to debug warehouse adapters and the like. But today we couldn't find the option to enable reporting anywhere in the Team Foundation Server Administration Console. All the guides, walk-throughs and such mention that it should be there right under "Application Tier" and shows up all right on my machine.

It turns out that you can install TFS with almost all features except with Report Server integration on a Windows 7 machine. You really need Windows Server for that one feature to work.

Re-installing the workstation as we speak :).

It would have been nice if the Administration Console would have shown the reporting item and on the page explained that this requires Windows Server to work.

Thanks to Tarun, here's the doc that explains it:
You can install Team Foundation Server on a client computer that is running one of the operating systems in the next list. However, client operating systems do not support integration with SharePoint Products or reporting. If you want to use either of these features, you must install Team Foundation Server on a server operating system.

I just joined the ALM Rangers program


Last week I found an invite to the Microsoft ALM Rangers group in my mailbox. And I'm happy to say that I didn't have to think twice to answer with an affirmative yes!

You can read my Ranger introduction here.

Micro HDMI to HDMI now available through DealExtreme


Given that the dock for the Samsung 7 Slate has an HDMI-A (the big one) and the slate itself has an HDMI-D (micro) connector, you either need to carry two adapter cables or.... when shopping for adapter cables you had to choose between them. It has been hard finding an adapter that can convert a micro-HDMI connector to a full sized HDMI connector. There are of course a lot of adapters that work the other way around, but I prefer not to have a very large plug sticking out of my slate when I don't use the dock.

I had already found a link to a wholesaler who carries such adapter, but so far no normal retailer carried it, until a couple of weeks ago:
Combine it with the following adapter cables and you'll never have trouble connecting to a projector or 2nd screen. (unless you find one that uses displayport only)
One note though... there seems to be a bug in the dock, the driver or in Windows 8, but the Dock HDMI connector doesn't always work as expected. I've found a workaround, but it requires you to be able to connect to your monitor using two cables. One from the dock and one from the tablet.I can get it to work using the following funny workaround:
  1. Connect the monitor to the dock using one cable (the VGA cable for example, make sure power comes from the slate or a wall adapter, not from the dock usb)
  2. Connect the monitor to the tablet using the other cable (the DVI-D cable for example)
  3. Extend the display while the tablet is out of the dock (this has always worked)
  4. Insert the tablet into the dock (thus while doubly connected)


Most Reading