Where will you be the week of May 14, 2011? I hope it’s with me and a bunch of other great folks at Tech Ed 2011.
It looks to be another great show. I’m lucky enough to be presenting an all-day workshop on virtualization for developers as well as two sessions.
One session is on using Expression Blend 4 as a developer. The second is on Team Build 2010.
I hope to see you there. And if you’ve not registered, there’s still time for both the show and/or my pre-con.
If you’re coming to my pre-con, drop me a mail with your t-shirt size. See the contact link on the blog.
See you there!
I’m doing a talk today at DevConnections in Orlando, FL today. The talk is primarily about all the yummy goodness that Microsoft ships out of band from the core Visual Studio product boxes. In addition, I cover what’s in the SKUs above Visual Studio 2010 Professional edition—Premium and Ultimate.
So here’s a list of the items I either showed a demo of, or mentioned.
Notes
Feature of SKU means it’s in the box.
Benefit means you get it if you have the SKU and valid MSDN Subscription
N/A under Minimum SKU means it works with command-line tools or doesn’t technically require Visual Studio 2010 to work
I had the need today to run two copies of Microsoft Test Manager (aka MTM.EXE) so that I could copy data from a Test Case from one Team Project to another. Unfortunately, MTM.EXE is a single-instance application. I considered a few different options including RDP to another machine or account. Thankfully, I got a great tip from a fellow VS ALM geek, Anna Russo.
The trick you ask? Duplicate MTM.EXE and MTM.EXE.CONFIG and rename. I chose to create MTM2.EXE and MTM2.EXE.CONFIG. And there you go, two instance of MTM running side-by-side.
Thanks Anna for the tip. You’ll find MTM.EXE at %Program Files%\Microsoft Visual Studio 10.0\Common7\IDE. You’ll of course need Administrator rights to duplicate the files in that directory.
Thanks to everyone who came out to my workshop yesterday. I had a great time.
Here's the slides (zipped PDF) for your enjoyment.
Thanks again and I hope to make it down again sooner than later.
Randell-Pre-Con-TechEd-2010-AU.zip (3.71 mb)
Well, I’m back from holiday with the family. It was two great weeks of travel and fun.
In between however, I spoke at VSLive Redmond.
For those of you attended thank you! And a special thank you to those who attended my session on TFS 2010 or my all day workshop.
For those of you in the workshop, here’s the links I promised.
TFS 2010 Install guide
Brian Harry's Blog (the TFS Godfather)
Hakan's "Magic Upgrade Script"
My MSDN Articles to date on "Team System"
TFS Integration Platform
TFS 2010 Scrum Template
Download and run the MSI.
Then "Upload" via Visual Studio from:
%ProgramFilesx86%\Microsoft\Microsoft Visual Studio Scrum 1.0\Process Template
TFS 2010 Power Tools
Team Lab Blog
Enjoy!
:-)
Well if you do, you’ll find that you’ll be unable to run your Unit Tests. You also find if you try to open up your test settings file, you get an error as follows:
I filed a bug on Connect (#524181) and in working with Microsoft, got a solution. Here’s how to fix it.
Disclaimer: this works on my *virtual machine*. If you try this and your machine blows up, don’t come crying.
OK, with that out of the way, here’s what you need to do:
- 1. Shutdown any running copies of Visual Studio 2010 Professional Beta 2.
- 2. Start the Registry Editor.
- 3. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\10.0\EnterpriseTools\QualityTools\TestTypes .
- 4. Back up the registry key just in case.
- 5. Delete the following sub-keys:
a. {37e36796-fb51-4610-8d5c-e00ceaa68b9f}
b. {4e7599fa-5ecb-43e9-a887-cd63cf72d207}
c. {fa4c85ff-1236-4463-b954-3ba2f0eabd95}
d. {982b8c01-1a8a-48f5-b98a-67ee64bc8687}
That should do it. You should now be able to run Unit Tests and edit your test settings.
To be clear, you should only need to do this if you installed Team Foundation Server 2010 Beta 2 after you installed Visual Studio 2010 Professional Beta 2. If you’re using Visual Studio 2010 Ultimate Beta 2, you won’t have an issue.
Hope this helps.