Subject: RE: [xsl] XSLT In the Build Process? From: "Dion Houston" <dionh@xxxxxxxxxxxxxxxxxxxxx> Date: Fri, 9 May 2003 13:12:56 -0700 |
Well, I've written a test tool that uses the .NET Framework CodeDOM to create C# or VB code. For example, I have a tag like: <VariableDeclaration name="var" type="System.String"/> And this will generate: String var; This turned out to be quite a novel approach to the problem I was facing. Using this technique you can in theory generate source in any language supported by the CodeDOM. Dion -----Original Message----- From: Mitch Amiano [mailto:mitch.amiano@xxxxxxxxxxxxxxxxxxxx] Sent: Friday, May 09, 2003 12:54 PM To: xsl-list Subject: [xsl] XSLT In the Build Process? I've observed a team of developers using XSLT as a build tool to generate C++ code, instead of using the UML tool that had been selected for them (Rhapsody). They modelled various aspects of the problem domain using XML, and used XSLT templates to pump out C++. Reasons for their decision to go down this path included the precise control they could exercise over the code generation framework and hence the generated code, the ease of revising the XML inputs and XSLT templates, and the seamless fit with their Unix based ClearCase configuration management and "make" based build scripts. How common is this approach? Anyone else have experience long-term applying a similar approach? - Mitch XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] XSLT In the Build Process, Mike Haarman | Thread | Re: [xsl] XSLT In the Build Process, Mitch Amiano |
[xsl] XSLT In the Build Process?, Mitch Amiano | Date | RE: [xsl] fop and internet explorer, cknell |
Month |