This solved my problem. If you are after enforcing code-commenting, then download and install this program. Add the new "policy" that is now available in Source control and restart Visual Studio. Users now have to enter comments.
I ran the MSI installer on my x32 Win7 box, rebooted, launched powershell and ran "Add-PSSnapin Microsoft.TeamFoundation.PowerShell" and got the following error:
Add-PSSnapin : The Windows PowerShell snap-in 'Microsoft.TeamFoundation.PowerShell' is not installed on this machine.
HUH? Where does the dll get copied to during install? Am I missing a path element?
By default, the Powershell Cmdlets feature in the MSI do not get installed--if you want to use them you must choose a Custom installation configuration and explicitly select them to be installed.
Also, I see you've specified that this happened on a 32-bit OS, but if you should happen to install on a 64-bit machine you'll get the same error unless you run Powershell (x86). The Cmdlets don't work in 64-bit mode for some reason.
Any luck with this? I have 2008 R2 server (64 bit) and trying to install the powershell cmdlets. When Install the power tools December 2011 edition, the setup runs fine if I choose to not install the powersheel cmdlets. If I choose custom setup and add the cmdlets to the installtion I get a 1001 Error and the install fails and rolls back.
Installing Dec 2011 onto 2 new TFS systems, same result on both - 5 errors complaining about 5 different keys as noted below. 2 different persons tried it: local admin on Win 7 machine hosting a small TFS pilot environment, and a domain admin on larger production TFS environment - same result for both of us. Workaround was to hit "Ignore" and continue on - but I expect that Explorer context menus might be missing?
Error 1406. Could not write value to key \SOFTWARE \Microsoft \Windows \CurrentVersion \Explorer \ShellIconOverlayIdentifiers \TfsOverlayControlled. Verif that you have suficient access to that key, or contact your support personnel. ABORT | RETRY | IGNORE
Then same for "TfsOverlayEdit", "TfsOverlayAdd", "TfsOverlayLocked", "TfsOverlayRename".
I guess I am missing something (still kind of new to this). I am an administrator for my team's project library. However, for some reason I cannot see other team members in the Team Member node (I have it enabled in options). I am able to control permissions and add/remove people from accessing our library, I just cannot see any team members through the node (it is not expandable). I am sure it is something silly, but any help would be appreciated.
Sorry for the late reply. Are you still having problems with team members ? Let me know if this post helps identify where team members get the list from :
Guys, I've downloaded and installed the Team Foundation Server Power Tools December 2011 update but not sure how I can start using it to connect to a Team Foundation Server? I have Visual Web Developer 2010 and a stripped down version of Visual Studio 2008 which was installed with SQL Server express but not sure where to go from here. Can you help?
From the Shell menus, when I try to checkin a change to a file that has been checkin locked in another workspace, there's no error message. The file is obviously also not checked in.
From the command-line I get a clear error message.
Also, from the shell menus, if I attempt to checkout a file that has been checkout locked in another workspace, I get an error message (the same error I get from the command-line).
Am I missing something?
I do run TFS2010 on a 64bit Windows 2008 R2 too (there is no x86 version of Win2008 R2) and didn't experience any issue to install the power tools. It is installed in C:\Program Files (x86)\Microsoft Team Foundation Server 2010 Power Tools.
Are you logged on the server as a local admin ?
I have installed the December 2011 version and it has made Visual Studio 2010 Ultimate unstable when using Team Foundation Server functionality. I seem to be able to check in and check out OK, but trying to use Team Explorer is problematic. Any suggestions of finding a fix for it?