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 am using VSTF power tools and was able to configure email alerts on completion of build. I might be missing something but I was not able to find any options to configure email alerts when the build starts.
From the the TFS Admin Console, when I select the Team Foundation Backup item (march 2011 version), an error "There is an error in XML document (0, 0)" is displayed. I have reinstalled several time with no resolution.
Hello? Anyone? We have spent 3 days on this and can't find any solutions. What would cause the admin console to fail loading the xml doc used for the Power Tools back up? Where does this xml file exist on the computer?
Ok finally found it! Defect-If the ConfigPT.xml file exists (C:\ProgramData\Microsoft\Team Foundation\Server Configuration)but is empty, the snap-in crashes. This is the opposite of the the "fixed" defect where the snapin crashed if there was NO file.
How do you review a shelveset created by other users?
Example: User_A created a shelveset named "testshelveset". And I want to review this shelveset.
I tried the command as following and it does not work...
> tfpt review /shelveset:testshelveset;User_A
> tfpt review /shelveset:"testshelveset";"User_A"
TFPT returns the message...
No shelvesets found matching testrevue;<my_userid>
Note: I can see the shelveset with the command "tf shelvesets /owner:User_A".
One of problems we have with end users are compliants that they are receiving too many alerts. From this I then need to see what alerts are actully in place. Currently there is no place where I can see all the alerts in the database, it would be great if there is a place where I can see all the alerts.
I used Domain Administrator to run SQL Sever EXPRESS, and Domain Administrator to setup the backup. Still get the permission error on last two steps. I tried local folder and remote folder. All failed.
I can open share folder from Window Explore without any problem. I use windows Server 2003.
There is the error log.
[Error @21:50:54.710] Microsoft.SqlServer.Management.Smo.FailedOperationException: Backup failed for Server 'newv7\SqlExpress'. ---> Microsoft.SqlServer.Management.Common.ExecutionFailureException: An exception occurred while executing a Transact-SQL statement or batch. ---> System.Data.SqlClient.SqlException: Cannot open backup device '\\Newv7\TFSBackup\temp_20110711165054.bak'. Operating system error 5(Access is denied.).
BACKUP DATABASE is terminating abnormally.
at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand,
make sure that all accounts have full control on the folder (if its a local one) and have access to the network share. i had to authorize !TFSService, TFSSetup (user to install and configure the backup plan) and the user running the sql service (network service)
I am able to set and use an UNC path in my Workspace (in Team Explorer). However, when using the Windows Explorer (any function) an error message pops up: "The path is not of a legal form." Could you please fix this? Thanks, Dany
Whenever I try to use the process editor, I get prompted with the "Connect to Team Project Collection" window. Although my team foundation server appears in the list, when I connect to it I get the "Object reference not set to an instance of an object" error message. I'm using Visual Studio 2010 sp1, TFPT March 2011 and connecting to TFS 2008.
I work in Windows 7, and while I do see TFS icons and TFS context menu options in Windows Explorer, I don't get the same in file dialogs/lists inside an application (the 'common file dialogs' mentioned in the Description). Can someone tell me if I'm doing something wrong, or is this a bug? This used to work in older versions of the Power Tools, and I loved this feature. Very unhappy it's not working anymore.