Difference between revisions of "Microsoft TFS2010"
From Richard's Wiki
(New page: * [http://visualstudiomagazine.com/Articles/2010/03/30/Agile-Project-Management-for-Everybody.aspx?Page=2 Agile Project Management using TFS 2010]) |
|||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
* [http://visualstudiomagazine.com/Articles/2010/03/30/Agile-Project-Management-for-Everybody.aspx?Page=2 Agile Project Management using TFS 2010] | * [http://visualstudiomagazine.com/Articles/2010/03/30/Agile-Project-Management-for-Everybody.aspx?Page=2 Agile Project Management using TFS 2010] | ||
+ | |||
+ | ==== Fix problem where project files need to be checked out repeatedly when using TFS with reverse proxy ==== | ||
+ | If you get the situation where all the project files keep getting "automatically" checke dout by TFS because source control information needs to be changed, it's because they have been imported/upgraded from VSS. You need to change the four Scc tags in each project file to have a value SAK | ||
+ | |||
+ | Change: | ||
+ | |||
+ | :<SccProjectName>%24/Project/Trunk/Source/A.Library.Tests</SccProjectName><br> | ||
+ | :<SccLocalPath>.</SccLocalPath><br> | ||
+ | :<SccAuxPath>http://myserver:8080</SccAuxPath><br> | ||
+ | :<SccProvider>{4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}</SccProvider><br> | ||
+ | |||
+ | To this<br> | ||
+ | |||
+ | :<SccProjectName>SAK</SccProjectName><br> | ||
+ | :<SccLocalPath>SAK</SccLocalPath><br> | ||
+ | :<SccAuxPath>SAK</SccAuxPath><br> | ||
+ | :<SccProvider>SAK</SccProvider><br> | ||
+ | |||
+ | Details at [http://stackoverflow.com/questions/1728987/what-is-the-best-practice-for-setting-the-sccauxpath-property-in-a-visual-basic What is the best practice for setting the SccAuxPath property (StackOverflow)]<br> | ||
+ | and [http://alinconstantin.blogspot.com/2008/02/sak-source-control-strings-in-visual.html The SAK source control strings in Visual Studio's project files (ALIN CONSTANTIN'S BLOG)] | ||
+ | ==== Enable TFS Client Tracing in VS2010 ==== | ||
+ | See [http://blogs.msdn.com/b/edhintz/archive/2007/03/30/tfs-client-tracing.aspx TFS Client Tracing (blogs.msdn.com)] | ||
+ | |||
+ | # Shut down Visual Studio | ||
+ | # Using Windows Explorer navigate to the following directory: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE (replace c: with appropriate drive) | ||
+ | # Make a backup copy of devenv.exe.config | ||
+ | # Edit devenv.exe.config by adding the following before the last </configuration> : | ||
+ | <system.diagnostics> | ||
+ | <switches> | ||
+ | <add name="TeamFoundationSoapProxy" value="4" /> | ||
+ | <add name="VersionControl" value="4" /> | ||
+ | </switches> | ||
+ | <trace autoflush="true" indentsize="3"> | ||
+ | <listeners> | ||
+ | <add name="myListener" | ||
+ | type="Microsoft.TeamFoundation.TeamFoundationTextWriterTraceListener,Microsoft.TeamFoundation.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" | ||
+ | initializeData="c:\tf.log" /> | ||
+ | <add name="perfListener" type="Microsoft.TeamFoundation.Client.PerfTraceListener,Microsoft.TeamFoundation.Client, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" | ||
+ | /> | ||
+ | </listeners> | ||
+ | </trace> | ||
+ | </system.diagnostics> | ||
+ | |||
+ | Trace data will be written to "c:\tf.log" (initializeData attribute above). Change this file name if you prefer | ||
+ | # Save the file | ||
+ | # Start Visual Studio | ||
+ | # Run steps you are interested in tracing | ||
+ | # Open c:\tfs-tracefile.log or whatever file you specified in step 5 | ||
+ | # This writes alot of data, so you will want to restore to the original setting when finished by copying the original file back or commenting out the lines in step 4 by surrounding the lines with <!-- and --> . |
Latest revision as of 00:33, 12 August 2011
Fix problem where project files need to be checked out repeatedly when using TFS with reverse proxy
If you get the situation where all the project files keep getting "automatically" checke dout by TFS because source control information needs to be changed, it's because they have been imported/upgraded from VSS. You need to change the four Scc tags in each project file to have a value SAK
Change:
- <SccProjectName>%24/Project/Trunk/Source/A.Library.Tests</SccProjectName>
- <SccLocalPath>.</SccLocalPath>
- <SccAuxPath>http://myserver:8080</SccAuxPath>
- <SccProvider>{4CA58AB2-18FA-4F8D-95D4-32DDF27D184C}</SccProvider>
To this
- <SccProjectName>SAK</SccProjectName>
- <SccLocalPath>SAK</SccLocalPath>
- <SccAuxPath>SAK</SccAuxPath>
- <SccProvider>SAK</SccProvider>
Details at What is the best practice for setting the SccAuxPath property (StackOverflow)
and The SAK source control strings in Visual Studio's project files (ALIN CONSTANTIN'S BLOG)
Enable TFS Client Tracing in VS2010
See TFS Client Tracing (blogs.msdn.com)
- Shut down Visual Studio
- Using Windows Explorer navigate to the following directory: C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE (replace c: with appropriate drive)
- Make a backup copy of devenv.exe.config
- Edit devenv.exe.config by adding the following before the last </configuration> :
<system.diagnostics> <switches> <add name="TeamFoundationSoapProxy" value="4" /> <add name="VersionControl" value="4" /> </switches> <trace autoflush="true" indentsize="3"> <listeners> <add name="myListener" type="Microsoft.TeamFoundation.TeamFoundationTextWriterTraceListener,Microsoft.TeamFoundation.Common, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" initializeData="c:\tf.log" /> <add name="perfListener" type="Microsoft.TeamFoundation.Client.PerfTraceListener,Microsoft.TeamFoundation.Client, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </listeners> </trace> </system.diagnostics>
Trace data will be written to "c:\tf.log" (initializeData attribute above). Change this file name if you prefer
- Save the file
- Start Visual Studio
- Run steps you are interested in tracing
- Open c:\tfs-tracefile.log or whatever file you specified in step 5
- This writes alot of data, so you will want to restore to the original setting when finished by copying the original file back or commenting out the lines in step 4 by surrounding the lines with <!-- and --> .