I'm unable to get this to load on Visual Studio 2015, just as local (install.cmd) instance.
Some of the UI has changed, but I can still get to the Check-in Policies window, but don't see this pol...
Id #11459 | Release:
| Updated: Dec 6, 2016 at 2:29 PM by behradborhani | Created: Sep 18, 2015 at 7:44 PM by TimDunn
I followed the steps to recompile and install the policy in vs2012, all work fine, but there's a big issue.
Every time change a file content and then refresh the "Pending Changes" page (just switc...
Id #11458 | Release:
| Updated: Dec 9, 2013 at 9:29 PM by hakuna | Created: Dec 9, 2013 at 9:29 PM by hakuna
Our team wants to show the actual TFS path for the $Source$ keyword, without replacing the "$" with "?" in the TFS path.
The associated patch allows "$/" to appear within the $Source$ keyword.
Id #9064 | Release:
| Updated: Feb 14, 2013 at 2:37 AM by nekno | Created: Aug 13, 2011 at 12:38 AM by nekno
The majority of our team resides in a single time zone. Since the file headers using keyword substitution are meant for human readability, we decided that a localized timestamp with a time zone off...
Id #9063 | Release:
| Updated: Feb 14, 2013 at 2:37 AM by nekno | Created: Aug 13, 2011 at 12:33 AM by nekno
It would be nice if there were an option or configuration to wrap comments in $LOG$.
Id #9005 | Release:
| Updated: Feb 14, 2013 at 2:37 AM by lothaine | Created: Jul 28, 2011 at 3:32 PM by lothaine
You need to find a method to allow keywords of mixed case. For example, you require the log keyword to be all lowercase when the user could use Title Case or be all uppercase.
Id #5184 | Release:
| Updated: Feb 14, 2013 at 2:37 AM by wheeley | Created: Jan 10, 2010 at 11:42 PM by wheeley
The ReplaceKeywordTest_0n() tests seem designed to fail - the insert of the substitution value creates an blank space just before the closing '$', but the tests don't put this space in when buildin...
Id #5126 | Release:
| Updated: Feb 14, 2013 at 2:37 AM by daengh | Created: Dec 29, 2009 at 12:26 AM by daengh