Stored Procedures' issue on duplicated name

[ghn.henrique]

Hi there,

If I have two stored procedures with the same name, but in different schemas, TSQLStoredProc will duplicated parameters, and it won't execute correctly. I had to create a new procedure, like "ProcName2", as a workaround. Could it be corrected?

There's also another bug within stored procs: it won't let me have a stored proc with a Varbinary(max) parameter in it. It'll raise an exception as I try to execute it.

Cordially,

[Dimon]

To solve the problem you should set the StoredProcName property to the "OtherSchema.ProcName" value but not to "ProcName".