> So, you still want to write a lot of entity classes, thousands of lines > of property get/set code and oh, for example xml / remoting support by hand? > > Code generation can help you get things done if you use the right > code generator, for example one which combines it with an O/R mapper core.
Code generation for DAL is one thing, code generation for UI is another. As for the snippet generation for properties et al, that's what a snippet generator is for in your editor of choice. Heck, I did that in TECO in 79, so I think I get "code generation" at that scale. What I DON'T find useful is "frameworks" that generate the same old basic site (or DAL classes or whatever) that don't really map to anything I can deploy in an end-user customizable environment. I do code for vertical markets, not one-off contracting or programmer tools, so I can't have people regenerate code when something needs to be customized at their end. I also don't find any value in the generation of DAL-layer DTOs from a "presumed fully designed" database schema. I'm much happier with business objects as POCOs that I can implement with NO database in existence, and eventually map them to whatever persistence is warranted. As for the idea that XML/Remoting object can be generated, color me gray with disappointment that you imply that those things are real-world usable. In my lifecycle, there's no chance that a database schema or today's POCOs are going to give me a stable interface that I want to program against. I would my rather model those things in a tool that works for that and then craft the XTOs that can do versionable contracts with them. I've generated code from UML diagrams (and roundtripped it nicely) using the latest Rational stuff, but that's pretty close to as far as I can go without dropping dangerously close to needing to attend Waterfall 2006. Marc p.s. Frans, please don't coopt this thread to sell your EXCELLENT tool, I've used it, respect it, but I don't need it. -- "Under capitalism, man exploits man. Under communism, it's just the opposite." –John Kenneth Gailbraith Marc C. Brooks mailto:[EMAIL PROTECTED] http://musingmarc.blogspot.com
