If I can every get my module coding back on track I wish to finish upgrading my codesmith template suite. I started this in the dnn 4/5 days and got it to the point where about 85% of a vb module would generate and maybe 50% of a c#. The idea was a fully operational module out of the gate, with a dal and ui that was set up to match your tables. By tables I mean plural, and I'm testing with one database with 50 tables, another with 20. I also created code for DNN functionality like import, export, and search. I also include embedded comments, copyright headers, and generate the RESX based on the descriptive metadata in the database. I wish to generate commercial quality code, not a QAD example.
I'm part of the way through upgrading them to dnn7 as I intended to use this as my means to upgrade my modules. For now I'll fix the dal bits and go back to dal2 later, but I'd like to add knockout generation, giving the option of dal/dal2 and web forms vs knockout. The idea being a working crud module out of the box that does things the "dnn way", that got all the tedious stuff out of the way so you concentrate on ui enhancement and business logic. Ideally this module would be free of custom libraries or odd build processes that would make it difficult to finish the coding without learning some "special" framework.
I'm already using Scott Wilkinson's template as a guide, along with the Christoc templates. I'm also looking at Scott's Client Centric examples. Those are good examples, but Scott and Chris have slightly different topologies for both the file systems and name spaces. When I look at other core modules and examples people have very helpfully pointed out I see more differences. I would like to have a matrix put together that shows put your models here, and use this namespace, and your utilities here, and use that namespace, and your UI elements, etc, and import these name spaces and use those name spaces. A cookbook that takes you past the fairly simple examples that are available. When I look at more complicated modules, like Events, there's yet another topology, so without knowing WHY they are put together that way it's difficult to know which model to follow.
Ideally I'd like to use the templates to completely refactor other modules I have to the "new" standards. Some are kinda messy, since I was learning how to so something while I did it and a redo would make cleaner and more maintainable code. Get a nice clean structure, UI, and DAL, and use that as a base to pull the rest of the code forward. I'd really like recommendations on the folder structure, namespace organization, and default functionality.
I would also appreciate some reviews of the resulting code. For example if someone sends me some DDL I could run my templates against it and send the code back. If you already have codesmith I'd be happy to share the templates in exchange for feedback.