Generate Typed DataTable from Stored Procedure

I am a brand new CodeSmith user. I have a stored procedure that selects rows for custom business entity. I would like to create a CodeSmith template that has the stored procedure as a parameter and generates a typed DataTable class for the entity. Is there a way that I can analyze the stored procedure and/or its output in order to determine column names and perhaps even attributes of the columns in source tables? I know that Visual Studio will generate a typed DataSet from a stored procedure. I am attempting to do something similar, only with the classes designed the way I want them instead of the way Visual Studio constructs them. Can somebody point me in the right direction? Thanks.

You should look at the DBDocumenter example.  Specifically in sproc_details.cst you can see where Eric parses the SPROC and gets parameter details.

HTH,

 There is also the CommandWrapper Template samples in the same folder.  The CommandWrapper template looks at a stored procedure and creates an object wrapper to execute the stored procedure.

Thanks for the suggestions. I've looked at these, but I need information about the table data that a stored procedure returns. These examples deal more with the input and output parameters. I've been exploring the CommandResultSchema with some success, but I'm having trouble determining whether or not a CommandResultColumnSchema represents an IDENTITY column in the source table. Do you have any thoughts on this? Thanks.

I understand what you are saying now.  This doesn't exist yet as far as I know.  However there is no reason why you couldn't write a template to actually parse the SPROCs to determine the source tables attributes.  The table details template will allow the harvesting of this info.  I know this may seem rudimentary BUT it would be complete information.

<% if (SourceTable.Columns[x].IsPrimaryKeyMember) { %>
<% if (SourceTable.Columns[x].ExtendedProperties["CS_IsIdentity"].Value.ToString().ToLower() == "true") { %>

I hope this helps,

Yes, it looks like that is what I will need to do. I'll need to determine the mapping of result columns to database table columns. Once I've got that, determining whether or not a source table column is an identity column appears to be trivial. Do you know of any code that attempts to map stored procedure result columns to source database columns?

No, I haven't seen that already done.   Everything I have seen starts with the table and moves out.

Sorry,