Instructions for using TDS and a tutorial (which I estimate will take a couple of hours to complete, if you build and exercise all the features) are included in the TDS.cs source code.

Note:  I plan to add the following suggestion to the instructions in the next version of TDS:

To make it easier to locate TestMethodsSourceFiles and TestMethodsToBeRun, you may wish to move them to a separate file (I call mine TDS_Methods.cs) containing something like this:

namespace TDS {
public partial class Test {

/// <summary>
/// Names of all TDS*.cs source files in the project.
/// </summary>
static string TestMethodsSourceFiles = @"



/// <summary>
/// Names of test methods in the TDS.Test{} class.
/// </summary>
static string TestMethodsToBeRun = @"


} }
Of course, delete the old definitions in TDS.cs and make suitable changes to the contents of this file.  Maintaining these lists in a separate file of this type should make it easier to update them when adding to your project new TDS test methods or new files containing them.

Additional examples, using files in Release 1.8

For an example (with instructions) of using TDS to assist with the building of  a Text Templating (*.tt or *.t4) file, see TDS Example – Editing a Text Template File.  This shows how to build and test a T4 file that generates an XML schema that guides the development of an example XML database, a database dictionary describing the tables, fields, and possibly other components of a database (perhaps one managed by SQL Server) describing the books in a library.

Building onto this database-dictionary example, the contents of such an XML file may be used to update the comments in an ADO.NET Entity Data Model (*.edmx file) that models a database of books.  (With the help of TDS code, I have written a program to do this automatically, but it's not ready for publication.)  If your EDMX file contains <Documentation> elements, see "Add XML comments to EF6-generated *.cs files" for a utility to place their contents into suitable XML comments in the generated code.  This wanders a bit from the original topic, as the utility is a short one and the use of TDS code in building it is not explicitly shown.

NOTE: The EF7 team is retiring the XML-based EDMX format; in EF7 all models will be stored as code, so the utility mentioned above will not work with EF7.  However, I understand that EF6 will continue to be supported for a long time to come, including the EDMX format.

Last edited Jun 25, 2015 at 3:57 AM by vjohns, version 19