 | Lars Fosdal on Security alarm provider Woonve… |
 | Thomas Mueller on Question got closed in May 202… |
 | Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
| Thaddy de Koning on Formulier voor bewindvoerders… |
Posted by jpluimers on 2012/10/03
When moving a truckload of stuff from Visual Source Crash, I came a long many .webinfo files.
I wasn’t sure they should be in TFS, and indeed they should not:
.webinfo should be excluded. (Some info about webinfo: How to copy and configure ASP.NET projects between different local computers)
–jeroen
via: asp.net – Should the WebInfo file be excluded from SVN – Stack Overflow.
Posted in .NET, ASP.NET, Development, Software Development, Source Code Management, TFS (Team Foundation System) | Leave a Comment »
Posted by jpluimers on 2012/09/20
This post describes the TFS workspace cleanup features Treeclean and Scorch.
Both are not in the Visual Studio UI nor TFS tool, but are available form the ftpt command from the optional Team Foundation Power Tools package.
The main reason you need these two features is that TFS does not always clean up after it self when you perform get latest. For instance renamed directories, as well as bin and obj directories are not automatically removed.
The tfpt command I most often use this this one:
tfpt treeclean /exclude:*.suo,*.user
This deletes files from your local TFS workspace directory tree that are not in the source control system, but skips the *.suo and *.user files.
Tfpt also allows you to scorch files from your TFS.
So my second most used tfpt command is scorch in either of the two below forms:
tfpt scorch /recursive /diff
tfpt scorch /recursive /diff /exclude:*.suo,*.user
The first form is for the automatic build environment, the second for my normal development workspace.
Below is the explanation of treeclean and scorch.
First some other great commands from this StackOverflow answer by Martin Woodward:
Not quite, however you might want to download the TFS Power Tools and check out the command line utility tfpt.exe.
The “tfpt online” and “tfpt treeclean” might be most useful to you when working outside of an integrated TFS client. tfpt online will look for files in your local directory that are not under version control, treeclean will show you files in your local directory that are not under version control so that you can remove then if they are not required.
Scorch does more than Treeclean.
I use Treeclean for 90% of my normal workspace work, Scorch (with exclude) for about 10% of the time in my regular workspace.
For my CCnet build integration workspace, I only use Scorch (without exclude).
Treeclean just cleans the tree of stuff that is not in TFS:
B:\MasterWorkingDir>tfpt treeclean /? tfpt treeclean - Delete files and folders not under version control Usage: tfpt treeclean [/exclude:filespec1,filespec2,...] [filespec...] [/recursive] [/batchsize:num] [/noprompt [/preview]]
Scorch does more work: at the end, both source control and the local disk situation are identical.
B:\MasterWorkingDir>tfpt scorch /? tfpt scorch - Ensure source control and the local disk are identical Your local disk will be scanned for: (1) items that are not in source control (2) items which are different on disk from the workspace version (3) items which are in the workspace but are missing on disk Items not in source control will be deleted from disk, just as with the tfpt treeclean command. Items determined to be different on disk from the workspace version will be redownloaded from the server. Items missing on disk will also be redownloaded. Items with pending changes are exempted. By default, items deleted from your local disk (#3 above) will not be scanned for, and local items are determined to be identical/different from the workspace version *solely by examining the read-only bit on the file*. To redownload items deleted from your local disk (#3 above), supply the /deletes option. To detect items which are different from the workspace version but still have their read-only bit set (+R), supply the /diff option. When using either or both of these options, tfpt scorch runs more slowly. Usage: tfpt scorch [/exclude:filespec1,filespec2,...] [filespec...] [/recursive] [/batchsize:num] [/noprompt [/preview]] [/deletes] [/diff]
The commandline options are also different.
Scorch has these extra when compared to Treeclean:
/batchsize:num Set the batch size for server calls (default 500)
/deletes Detect and replace items missing from the local disk
/diff Use MD5 hashes to compare items with source control
Treeclean can have these options:
/noprompt Operate in command-line mode only
/exclude:filespec[,..] Files and directories matching a filespec in this list
are excluded from processing
/preview Do not make changes; only list the potential actions
/recursive Switch from one level of recursion to full recursion
/batchsize:num Set the batch size for server calls (default 500)
filespec... Only files and directories matching these filespecs
are processed
Scorch can have these options:
/noprompt Operate in command-line mode only
/exclude:filespec[,..] Files and directories matching a filespec in this list
are excluded from processing
/preview Do not make changes; only list the potential actions
/recursive Switch from one level of recursion to full recursion
/batchsize:num Set the batch size for server calls (default 500)
filespec... Only files and directories matching these filespecs
are processed
–jeroen
via:
Posted in CodePlex, Development, Software Development, Source Code Management, TFS (Team Foundation System), Visual Studio 11, Visual Studio 2002, Visual Studio 2003, Visual Studio 2005, Visual Studio 2008, Visual Studio 2010, Visual Studio and tools | 4 Comments »
Posted by jpluimers on 2012/09/19
Interesting:
git-tfs is a two-way bridge between TFS and git, similar to git-svn.
Need to check out if it is more like the SVNBridge wrapper that wraps SVN around TFS on either the server or the client, or like git-svn which wraps git around SVN only around the client.
–jeroen
via: git-tfs.
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management, Subversion/SVN, TFS (Team Foundation System) | Leave a Comment »
Posted by jpluimers on 2012/08/29
Just found a glitch in the unmap support for tf workfold (and found out it has already been reported).
First what I tried to do:
D:\develop.TFS02 into D:\develop\CodePlex\TFS02 using tf map (which BTW allows you to do in place branch switching).D:\develop.TFS02\besharp from TFSFirst a few things; the first one succeeded (as it implicitly uses the /map command), the last ones failed because /unmap is ambivalent on the /collection parameter: on the one hand it wants to do without, but when it discovers it cannot do without, it wrongly indicates it requires it.
D:\develop.TFS02\besharp>tf workfold /collection:https://tfs.codeplex.com/tfs/tfs02 /workspace:%COMPUTERNAME% $/ D:\develop\CodePlex\TFS02 D:\develop.TFS02\besharp>tf workfold /collection:https://tfs.codeplex.com/tfs/tfs02 /workspace:%COMPUTERNAME% /unmap $BeSharp The option collection is not allowed. D:\develop.TFS02\besharp>tf workfold /unmap /collection:https://tfs.codeplex.com/tfs/tfs02 /workspace:%COMPUTERNAME% D:\develop.TFS02\besharp The option collection is not allowed. D:\develop.TFS02\besharp>tf workfold /unmap D:\develop.TFS02\besharp Unable to determine the workspace. You may be able to correct this by running 'tf workspaces /collection:TeamProjectCollectionUrl'. D:\develop.TFS02\besharp>tf workfold /unmap /workspace:%COMPUTERNAME% D:\develop.TFS02\besharp Multiple workspaces exist with the name T61PJWP. Please specify the Team Foundation Server or qualify the name with the owner.
The workaround is to
–jeroen
Via:
Posted in .NET, Development, Software Development, Source Code Management, TFS (Team Foundation System), Visual Studio 2010, Visual Studio and tools | Leave a Comment »
Posted by jpluimers on 2012/08/23
A while ago, I inherited a bunch of C# and VB.NET projects. One of them always generated the below error when including it in Team Foundation System (yes, the original projects were salvaged from Visual Source Shredder version 6.0c):
[Source Control]
Some projects have been bound to server locations that may be incorrect.
A location may be incorrect either because it does not contain the majority of the projects' files or because those files are not in the correct location relative to the specified server folder.
You should probably fix all the bindings in the solution. However, you may continue and bind these projects to the specified locations even when some may be incorrect.
[Fix server bindings] [Continue with these bindings] [Help]
First I tried the Help button: it links to a Help page on MSDN explaining the error can be cause with some statistics on projects not being in the source control system. Since all projects were, there, I looked for more information.
I tried finding a “Fix Server Bindings” or a 2010 “Some projects have been bound to server locations that may be incorrect” link that fitted my use case (getting projects from VSS into TFS), but the solutions I tried eventually all led to the same issue.
Fixing the server bindings would always fail: the solution (which itself is also a project) would get the status Invalid.
The next steps were these:
Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{8D9964D4-6129-4B8F-9238-F9161A02B968}"
ProjectSection(SolutionItems) = preProject
...
Framework\Config.dll = Framework\Config.dll
...
EndProjectSection
EndProjectReading the Help more carefully, with in the back of my mind keeping “Solution Items” all as projects, I finally got the cause:
When some percentage of Solution Items cannot be found locally, and are not in the version control system, Visual Studio marks the solution binding to the version control system as “Invalid”.
The temporary solution is to ignore the error, until I have found all the missing files (they are scattered around some network shares), or made sure they are not needed at all.
There are many of those (you recognize them from the missing padlock icon in the Solution Explorer).
Version control rot is just like link rot, that’s why one of the high priority action items is to introduce for build automation at this client, then deploy those as clean builds into the Develop and Test stages of the DTAP, then verify if the solutions still work).
–jeroen
Posted in .NET, C#, C# 1.0, C# 2.0, C# 3.0, C# 4.0, C# 5.0, Development, Internet, link rot, Power User, Software Development, Source Code Management, TFS (Team Foundation System), VB.NET, Visual Studio 2010, Visual Studio and tools, WWW - the World Wide Web of information | Leave a Comment »
Posted by jpluimers on 2012/07/19
When switching between different source code management systems for doing version control at clients, it is always a bit of “getting used” to the mantra of both their system, and how it has been implemented.
Few people can really explain this well.
Richard Berg did in his great StackOverflow answer sharing his ideas on how to handle Trunk/Branch/Tag (for people starting with SVN, read this answer by David Schmitt before you mix them up).
I still see truckloads of people, and even teams try to do without version control. Please do use source control. If you don’t know where to get started, read some text on Source Control for beginners, or for instance the free on-line Red Bean books on SVN, Mercurial or CVS.
Also read some other great answers by Richard Berg (many on TFS, but also this very balanced view on usage of nullable in languages and proper use of Invoke-Expression in PowerShell: recommended reading).
–jeroen
Posted in Mercurial/Hg, Source Code Management, Subversion/SVN, TFS (Team Foundation System) | Leave a Comment »
Posted by jpluimers on 2012/06/19
Never knew it was so brilliantly easy to undelete files from TFS: you can do it in Visual Studio, by enabling “Show deleted items in the Source Control Explorer” in the settings.
Just look at TFS – Undelete File or Folder for the screen shots.
Not sure in which Visual Studio version this got introduced, but it works in VS 2010 and up.
–jeroen
Posted in Development, Software Development, Source Code Management, TFS (Team Foundation System), Visual Studio 11, Visual Studio 2010, Visual Studio and tools | Leave a Comment »
Posted by jpluimers on 2012/05/15
(Thanks to a “Missed Post” problem on WordPress.com, this one didn’t get posted on the scheduled date. Sorry for any inconvenience)
One of the next steps in the automated build process I’m setting up is increasing AssemblyVersion values after succesful builds.
It is is in a CCnet / TFS2010 / VS2010 environment.
Some links:
–jeroen
via: change assemblyversion during checkin ccnet – Google Search.
Posted in .NET, C#, Continuous Integration, CruiseControl.net, Development, Missed Schedule, SocialMedia, Software Development, Source Code Management, TFS (Team Foundation System), WordPress | Leave a Comment »
Posted by jpluimers on 2012/01/18
I keep forgetting this:
When logging in to CodePlex using TFS, then you need to prefix your username with “snd\” and suffix it with “_cp“.
So if your CodePlex username is wiert, then your login becomes snd\wiert_cp.
Somehow, this used to be more prominently on the codeplex site, but it isn’t any more.
–jeroen
via: TFS2010 « Ahmed Al-Asaad’s Blog.
Posted in CodePlex, Development, Source Code Management, TFS (Team Foundation System) | Leave a Comment »
Posted by jpluimers on 2011/12/28
While re-designing a Visual Studio 2010 plus Delphi XE2 install for a specific client, I updated some of my Tools page links:
–jeroen
Posted in .NET, C#, Delphi, Development, Software Development, TFS (Team Foundation System), Visual Studio 2008, Visual Studio 2010, Visual Studio and tools | 1 Comment »
The Wiert Corner - irregular stream of stuff 