Version 3 of the templates is now available at:

www.crewstone.com/LinkClick.aspx

Check the readme file for the updates. Highlights are more validation code, integration of C# templates from Declan Ward, and additional improvements to import/export.

As the author of the Crewstone templates I wouldn't say one is better than the other since I use both. They are intended for different purposes. If you are writing a module that doesn't have extensive database structure, or you're building as you go the Code Endeavor templates are an excellent way to get your basic module framework put together. If you already have a large data structure build and you want a bunch of the GUI, data layers, etc, skeletonized for you then my templates will do much of that. They do not create a completely working module, they only attempt to eliminate as much of the tedium as possible when you're working with a lot of database fields. If you have a small number of tables or simple data structures you may want to consider DNN Kickstart Studio. You can get that on Snowcovered,

Installation and placement isn't terribly complicated, but I need to point out to use my templates you need CodeSmith. When you install codesmith it creates a CodeSmith directory in whatever your default user space is and you place the template folder there. They will show up on the list of available templates in the CodeSmith window. Open the Master template, and fill out the necessary information such as company name, module name, where your database is, and where you want the generated output to go, etc. The mechanics of doing that are part of CodeSmith, and I haven't planned on creating CodeSmith tutorial as there of some available on the CodeSmith site. The fields are described in the readme.txt. I should point out that my templates were created for multi-table modules to fill in some of the gaps that other single-table oriented templates didn't cover, they may be a lot to bite off if you haven't done much DNN programming.

As far as where to put the generated output, I highly recommend you look at some of the model development tutorials as they explain that quite nicely. I will note that my templates use a Web Site Project (WSP) not a Web Application Project. I take the generated output and copy it into my DNN test site, then import the module definition (.DNN) file. Once i'm finished with the remaining work in Visual Studio, I use the module packaging option in DNN to create the ZIP file.