In the case studies in Chapter 9, “Case Study: Generating a Connection String Manager,” and Chapter 10, “Case Study: Generating Validation Code,” I built separate, standalone solutions for each problem. In both instances, a significant part of the case study was devoted to developing the Visual Studio add-in that integrated the code generator into the application. In practice, I don’t actually build my code-generation solutions that way.
Rather than have multiple code-generation solutions that I load into Visual Studio, I have one add-in project with multiple class files. Each class file (e.g.,
WebFormUtilities) contains several related code-generation solutions. Because I have only one ...