A further note - the generator routines contain a section like:

-- Set @SET_DB to name of SP to set permissions or to blank
SELECT  @SET_DB      = 'asp_dbPermissions'
SELECT  @ObPrefix    = 'x'          -- Prefix for object variables
SELECT  @DefLanguage = 'VB'         -- Default language C# or VB
SELECT  @Separator2  = ''           -- Separator between Tablename and action
--  Configuration end

•  Change @SET_DB to your routine for setting stored procedure permissions or blank it out if wish to do it your self. A small system can easily have hundreds of stored procedures or more, setting them by hand can take hours, but a permissions routine can do  it very reliably (why send a human to do a machines job!)
• Change obPrefix if you prefer another prefix to x for object variables
• Change DefLanguge to C# if you want the wrapper code to default to C#
  
• Put a value in separator2 if you TableYOURVALUEInsert to TableInsert