According to this post: https://connect.microsoft.com/VisualStudio/feedback/details/362523/sqlmetal-error-when-used-on-a-database-with-a-table-valued-parameter#tabs
and several other posts I've found containing a list of features and bug fixes for LINQ to Sql in 4.0 this was supposed to be fixed in that it would simply ignore that Sproc and go on it's merry way.
SQL Metal
- Foreign key property setter now checks all affected associations not just the first
- Improved error handling when primary key type not supported
- Now skips stored procedures containing table-valued parameters instead of aborting process
- Can now be used against connections that use AttachDbFilename syntax
- No longer crashes when unexpected data types are encountered
I have installed the newest SDK (v7.1) and sqlmetal.exe is still not getting past that stored procedure.
Does anyone know if that promised improvement (of skipping instead of bombing) was included? And if so, in which version?
