Selling the use of BTDF to a client - Reason #6 to use BTDF

Topics: General Questions
Mar 3, 2015 at 2:45 PM
Edited Mar 3, 2015 at 2:45 PM
A client has some slight resistance to BTDF; i.e. they are asking: if we only have simple projects, and only two environments, is the learning curve and set up time worth the benefits.

So I put on my salesman hat, and was reviewing your "Top 5 Reasons to Use BTDF" on your home page of CodePlex.

I think this would be another huge reason:

With BTDF and the proper procedures, you make sure that the binding files matching the source code at a point in time. This is done by checking in the binding file (and the customized version of it for BTDF), and always creating the MSI on a build machine for deployment to UAT or PROD. Rather than developers giving an MSI to deployment team, the MSI should be taken directly from some predetermined folder on the build machine.

Neal Walters
Mar 4, 2015 at 2:55 AM
Thanks Neal. I added a bullet point about using a build server to produce an MSI. That's definitely worth calling out.