Hi Mary,
That's a good point and you are right this is design time issue not a run
time issue. However, having the type defined in one place makes changes to
the code much easier to make. The round trip issue you referenced could be
avoided if Visual Studio was more tightly integrated with SQL server. Then it
would only update the type information at compile time. In general, I would
like to see better integration of stored procedures and application code. I
would like to be able to call a stored procedure the same way I call any C#
function. I do not like having to writing all the plumbing code that is
currently required to call stored procedures. Why should have to define
stored procedure parameters in two places? I don't do that with methods I
write in C#.
I know that the new version of SQL Server takes a step in that direction by
building the CLR into SQL Server. I hope following version will continue that
direction.
Thank you for your efforts to help. I think I will just have to be patient
and wait for newer versions of SQL Server and .Net.
Thanks,
Mike
|
Similar Threads
