Skip to main content

Team Foundation Server source control versus Subversion

There is a lot of discussion going on if TFS Source Control is good or bad. In my experience it’s just a matter of getting used to it. Once you understand how TFS Source Control works, it’s a painless process.

For a client I had to summarize some differences between Subversion(their current source control system) and TFS.

 

Subversion TFS Source Control
Branching in Subversion has a constant cost Branching in TFS has a variable cost based on the number of items in the subtree being branched. (content does not get branched, just the file metadata).
Subversion doesn't force you to check out an item before you start editing it. TFS needs to check out an item before you can start editing it.
Subversion does not support undeleting deleted items(after a rename). TFS supports easily undeleting deleted items. This includes being able to undelete something after a parent has been renamed.
Subversion only shows an item history. It does not show non-history related branches of an item. TFS can show you full branch topologies.
Subversion doesn't have shelve support. TFS includes shelves.
Subversion has rich offline support. TFS offline support is limited.
Subversion has server side hook scripts TFS has client-side checkin policies.
Subversion doesn't have a real rename implementation. TFS supports cyclic and dependant renames. (pending, shelving, merging, undoing, and checking in)
Subversion supports symbolic links inside of the repository that don't create symbolic links on the file system, sync just downloads items from the destination instead. (See the documentation on svn:externals) TFS has no sharing functionality.
Subversion does not track the client status. TFS has the concept of a workspace. It knows what version of the file the client has.

Popular posts from this blog

.NET 8–Keyed/Named Services

A feature that a lot of IoC container libraries support but that was missing in the default DI container provided by Microsoft is the support for Keyed or Named Services. This feature allows you to register the same type multiple times using different names, allowing you to resolve a specific instance based on the circumstances. Although there is some controversy if supporting this feature is a good idea or not, it certainly can be handy. To support this feature a new interface IKeyedServiceProvider got introduced in .NET 8 providing 2 new methods on our ServiceProvider instance: object? GetKeyedService(Type serviceType, object? serviceKey); object GetRequiredKeyedService(Type serviceType, object? serviceKey); To use it, we need to register our service using one of the new extension methods: Resolving the service can be done either through the FromKeyedServices attribute: or by injecting the IKeyedServiceProvider interface and calling the GetRequiredKeyedServic...

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.

Kubernetes–Limit your environmental impact

Reducing the carbon footprint and CO2 emission of our (cloud) workloads, is a responsibility of all of us. If you are running a Kubernetes cluster, have a look at Kube-Green . kube-green is a simple Kubernetes operator that automatically shuts down (some of) your pods when you don't need them. A single pod produces about 11 Kg CO2eq per year( here the calculation). Reason enough to give it a try! Installing kube-green in your cluster The easiest way to install the operator in your cluster is through kubectl. We first need to install a cert-manager: kubectl apply -f https://github.com/cert-manager/cert-manager/releases/download/v1.14.5/cert-manager.yaml Remark: Wait a minute before you continue as it can take some time before the cert-manager is up & running inside your cluster. Now we can install the kube-green operator: kubectl apply -f https://github.com/kube-green/kube-green/releases/latest/download/kube-green.yaml Now in the namespace where we want t...