Yes, I've been using the generated install package and using the extensions Wizard to install it. When I look in the bin folder it's there along with a .pdb and a .xml file.

I just did. It's pretty interesting, and the CRUD generator may come in handy. That said, it introduces yet another template system that may generate some wonderful code, but if that code doesn't work for some reason you're back where your started. I have a fairly extensive library of CodeSmith templates that do most of what CRUD-Generator does and my attempts to update them to support DNN7 are an additional source of frustration. When your only real option is to reverse engineer an example, and doing something as innocuous as using a ColumnName decoration on all columns instead of one breaks the DAL2 layer what do you do? 

What would be helpful is documentation on WHY the code is written like it is, and some consistent recommendations for best practices. I know nobody wants to step on anyone's toes but how hard would it be to have a set of recommended folders and an explanation of each element you'd put there, plus what recommended namespace to use for it? One big honking' controller vs table based ones, recommendations for dealing with common items such as lookup tables and joins, etc. While MS allows a million ways to do everything some of those ways integrate into DNN better than others.

CRUDGenerator is creating DAL2 elements; models, controllers and UI controls. It seems to be using the DNNtc template as a base. Since I've never been terribly intimate with Entity Framework, and my experience with CRUDGenerator is however long it took to read through the code to figure out which German labeled buttons did what I can't compare further than that.