I just spent time looking at available code generation tools for CSLA. Although each was impressive in its own right, I felt that almost all of them were offering a different approach or philosophy about how to write the bulk of an application.
Certainly there is value in this, but to contrast my thoughts, I just want to say that I am thinking of creating a different kind of code generation project - one that would be more or less a loose collection of tools to generate, or help to generate, CSLA code. Users could pick and choose what they felt was relevant to their needs.
I am new to Csla, but my programming interests in the past have centered on writing utilities. With this interest, I don't think it would be long before I would write some simple tools that generate or facilitate CSLA code.
While writing this post, my thoughts suggest that what I am describing is more a "contribution" than a project, but I still think of a project because simple code generation tools can grow. To me, a contribution is generally something that is given at one point in time.
But this effort, like a contribution, would be something that is not sold. Value to me would be from feedback, whether user comments or discussion.
At this point I'll stop writing and listen for input.
I'm the coordinator of CslaContrib so in terms of contribution that may be a place to start.
CslaContrib is a collection of sample code projects and contributions that doesn't make it into the framework itself.
Have you looked at CslaGenFork (http://cslagenfork.codeplex.com) ?
I'll download cslagen Fork and try it out.
Thanks for the suggestion.
Copyright (c) Marimer LLC