0

I'm using codesmith to generate our CSLA layer, and have 3 separate Codesmith projects (.csp) to generate

  • CSLA Business Objects
  • Data Access
  • Scaffolded Unit Tests

Each of those project files have a list of target database tables within them, in the format:

<property name="EditableChild">
    ....
    <tableList>
      <table>
        <owner>dbo</owner>
        <name>Table1</name>
      </table>
      <table>
        <owner>dbo</owner>
        <name>Table2</name>
      </table>
    </tableList>
 </property>

I obviously don't want to maintain that list in three places. Is there any way we can share that same list of tables between the Codesmith project files, without merging them into a single project?

Kevin Blake
  • 434
  • 2
  • 5

1 Answers1

0

I work for CodeSmith Tools.. This currently isn't possible, but I've added this to the backlog. It would be cool if you could specify a source file with the content like you can do with connection strings in an app.config.

I've really wanted to move csla to use an xml file for entity generation. However, a lot of people don't want to maintain this xml file :(. This would however, solve this issue. You could always use the copy to clipboard feature in the property grid and then paste the properties to the other outputs in the csp. This would help keep these files in sync.

Blake Niemyjski
  • 3,432
  • 3
  • 25
  • 41
  • 1
    Thanks Blake - I've very rarely actually loaded up the property grid to manage the file, so I'm quite happy managing it as an xml file. It's interesting to hear of other developers so opposed to it :) That's very useful to know it's not yet supported, so I'll continue with my backup plan of using msbuild for now (such as the [Community Tasks XmlUpdate](http://geekswithblogs.net/paulwhitblog/archive/2006/04/11/74844.aspx) to keep our files in sync). Thank you :) – Kevin Blake Feb 12 '13 at 09:52