![configure visualsvn exclusions configure visualsvn exclusions](https://i.stack.imgur.com/LMYBQ.png)
![configure visualsvn exclusions configure visualsvn exclusions](https://s1.manualzz.com/store/data/045986701_1-84bc4053d87fcc5c7c60521f7ee6df8b.png)
This in the case of regular TF source control has a range of fundamental flaws in my opinion which are particularly shown when working with Sitecore solutions. So first is probably the most obvious function of the TFS ecosystem, the source control management system. I think in the web world it is more trouble than its worth and here is why:
CONFIGURE VISUALSVN EXCLUSIONS WINDOWS
Before I go further – I don’t believe TFS is the devil incarnate, I think it works just fine for solutions that are entirely in the MS stack where files are not subject to quick change – stuff like – windows phone apps / windows desktop apps / console apps maybe. I will quickly run through each and what I believe to be the pitfalls in their day to day use. As I am sure you are aware, TFS is broken down into a number of fundamental components. TFS in particular I have used for around 4 years now (note – I have not seen TFS 2015 as yet, but I believe that many of the same fundamental issues will still exist.). net based CMS systems for pretty close to 10 years, during this time I have used a load of tools to achieve various aspects of development. I have been working in development for around 15 years and specifically with.
![configure visualsvn exclusions configure visualsvn exclusions](https://www.troyhunt.com/content/images/2016/02/221220image5B425D.png)
To put things in perspective, I thought I would give a little background. This tool is Microsofts large ALM offering – TFS. I have had the opportunity to work in many environments with a range of tooling and processes over my career and there is one tool more than any other that I find a genuine hinderance on a day to day basis. I haven’t posted in a while, but recent projects got me thinking.