What’s new in the December 2010 Refresh?
The version of this virtual machine
which was refreshed on December 9, 2010, includes the following additions:
Visual Studio 2010 Feature Pack 2
· Team Foundation Server 2010 Power Tools
(September 2010 Release)
· Visual Studio 2010 Productivity Power Tools
(these are disabled in VS so that the screenshots of the hands-on-labs still
match; you can quickly enable the Productivity Power Tools via Tools ->
Extension Manager from within Visual Studio)
· Test Scribe for Microsoft
· Visual Studio Scrum 1.0 Process Template
· All Windows
Updates through December 8, 2010
· Lab Management GDR (KB983578)
Visual Studio 2010 Feature Pack 2 pre-requisite hotfix (KB2403277)
Microsoft Test Manager hotfix (KB2387011)
· Minor fit-and-finish fixes based
on customer feedback
· A new expiration date of June 1, 2011
Thursday, December 09, 2010
Thursday, October 14, 2010
Update (11/03/2010): I posted my deck on SkyDrive...but you still need to attend in person! (Lots of demos...)
Wednesday, September 15, 2010
- The MSI installer does not apply the process template nor install the SharePoint feature. You need to upload the template manually and run STSADM.exe commands to deploy the TFS WSP. Follow the ReadMe.txt files in the installation directories for the template and the feature, respectively.
- The path in the SharePoint installation ReadMe.txt file refers to the STSADM.exe path in the "12 hive" but this switches to the "14 hive" for SharePoint 2010. Just replace the paths to ../12/.. with ../14/..
Wednesday, August 25, 2010
QA: "What's the status on defect #4874?"
Dev: "Yeah, I fixed that Tuesday."
QA: "Err, ok. Well where is it? I mean where can I verify it?"
Dev: "No clue. I committed it Tuesday. It passed unit tests and built successfully."
QA: "Alright. I'll track it down."
Invariably, QA speaks with the build manager (if there is one) to find the build in which that defect was repaired. After discovering the correct build, now QA needs an environment stood up to house that build. But wait, the UAT environment is currently testing the next release. It can't be disturbed for another week.
At this point, the QA person's blood pressure heads for unsafe levels and the Dice.com browsing begins. But it doesn't have to be this way...
Lab Management in Visual Studio 2010 along with TFS solves many of these pains. Here's what the above scenario might look like with Lab Management:
QA doesn't inquire to the Dev about #4874 because it's already marked Resolved and back in QA's list of Defect Work Items. It's associated with a Continuous Integration Team Build instance which is marked with a Build Quality of Ready for UAT (meaning all unit tests passed and the build compiled successfully). Behind the scenes, as part of the build, Lab Management spun up a virtual web server, application server and database server. Team Build deployed the solution to this virtual environment and even sent an email to the build manager and the QA person (they chose to be alerted) saying this environment was ready for testing. This shop is currently testing four pending releases along with a production hotfix that's going out later today--all at the same time in completely separate environments.
Best of all, it's an amazing value. If you made/make the investment in Visual Studio 2010 Ultimate, you get Lab Management for free. Yes, that's right: free. That said, you will need some not insignificant hardware to serve as a host for these virtual servers...but you have that already, right?
Tuesday, July 06, 2010
Rather than suffering the life-shattering disruption of an unrecoverable drive, I called a Code Blue...and here's what I did:
Background: I have Win7 64-bit running on a Dell Latitude D830 with a bay-mounted SATA external 500GB drive and an external USB 500GB drive.
- Download Paragon Backup & Recovery Free Edition; install
- Use Paragon B&R to create a full backup of my existing hard drive (including MBR/Master Boot Record) onto my external USB drive (about 1/2 the size of my total hard drive)
- Use Paradon B&R to restore from the external USB drive to the external bay drive
- Shut down Windows7
- Swap primary hard drive with external bay drive
- Start up Windows7
- Order new hard drive to replace old, busted, Kerklunk drive...
Unbelievably, that's it. Everything (including Windows Activation) just worked. I will shout to the hills about the awesome-ness of Paragon's tools. Yea Paragon. Seriously. Booyah.
Saturday, June 12, 2010
Saturday, May 29, 2010
Sunday, May 23, 2010
Tuesday, May 18, 2010
Recently, I had an inquiry about where the "Changeset Comments Policy" went for Check-in Policies...check the Power Tools.
Before installing Power Tools…
After installing Power Tools…
Tuesday, May 11, 2010
Congratulations to the Microsoft team for recently releasing the much anticipated Visual Studio and Team Foundation Server 2010. My firm is embarking on several roll-outs right off the bat so I wanted to capture some of our efforts. To start, lets just provide the basics:
Sunday, April 25, 2010
I'll be speaking along with Alexei Govorine on managing Scrum projects leveraging the recently released Visual Studio 2010 and Team Foundation Server 2010.
Click here for COAAH write up and registration. My firm, Cardinal Solutions is a sponsor.
Regards to the Safelite folks who organized a safe, fun and entertaining event. Held in Las Vegas, I typically think of one (or two) things: gambling. However, out by Lake Mead is gorgeous. The event utilized the lake, trails and some serious up-and-down hills through rocky terrain to deliver a challenging run, swim and bike.
Sunday, March 14, 2010
Tuesday, March 09, 2010
Q. Has security administration improved with 2010?
A. Yes, fellow MVP Paul Hacker points out the new TFSAdmin 2.0 tool on CodePlex.
Q. Is anyone doing hosted TFS?
A. Yes, again see Paul Hacker's firm SaaS Made Easy.
Tuesday, February 16, 2010
…went great. I followed the PDF posted here and only encountered a single issue (which I wanted to record here).
[ Reporting ] TF255275: The following Web service for SQL Server Reporting Services could not be accessed: http://win-4h5rozlea69/ReportServer/ReportService2005.asmx.