The scripts don't produce a turnkey solution, you have to wire it all up and you need to understand the generated code and modify it as needed.

The way I would do it is:

1. createthe table, make sure it has a primary key

2. use the MSSQL stored procedure Codesmith template to generate procs

3. use the MS SQL Data Access template to generate data access code

4. use the Business class stubber template to generate a business class

5. generate the module control (I would not use the inline one myself)

6 use one of the mp_Table_ToGridView-IListBinding template to generate some usefull chunks of code for the gridview to copy an past into my control

I would use external projects with code behind. You "could" use the inline example and put all the data and business logic classes right in the control, but I like to have them separated projects per layer myself. I don't like to put data access code in my web code.

Hope it helps,

Joe

If you're using MySql it should work as long as you have the newer 4.x version of Codesmith. I'm pretty sure it can be used to generate against MySql tables.

Our Codesmith templates don't crerate MySql stored procedures, the sql statements are generated right in the DataLayer code so you can skip the step about stored procedures for MySql. Its more work having to maintain the stored procedures anyway. I do use stored procs for MS SQL because I've done so since the beginning, but MySql didn't even support stored procs when we started using it and I can't see any real reason to start using them now when its more work to do so and none of the existing code uses them for MySql and any supposed performance benefits of using procedures is so small it would be hard to measure. So I go for the easy maintenance using no stored procs for MySql. We just build the sql statements using StringBuilder.

Hope it helps,

Joe