Deprecation in ADO.NET

calling stored procedure in ADO.NET 2.0 | keyongtech

calling stored procedure in ADO.NET 2.0 | keyongtech — Thu, 22 Jan 2009 05:42:39 GMT

Pingback from calling stored procedure in ADO.NET 2.0 | keyongtech

re:Deprecation in ADO.NET

TrackBack — Sun, 10 Apr 2005 01:19:00 GMT

^_^,Pretty Good!

re: Deprecation in ADO.NET

Ranjan — Thu, 07 Apr 2005 06:27:00 GMT

I think
"In general, having multiple overloads where the distinguishing parameter type is “object” in one of them is a dangerous thing to do."
should become an FxCop rule now.

SqlParameters.Add(string, object) is Out!

TrackBack — Wed, 06 Apr 2005 21:55:00 GMT

One of the pleasures of working with Beta products is just when your code is working, you find out a...

re: Deprecation in ADO.NET

Pablo Castro [MS] — Mon, 04 Apr 2005 19:10:00 GMT

Hi Eric,

Note that AddWithValue is a strict replacement for Add(string name, object value), it's not an attempt to extend the API.

I somewhat agree that adding more overloads would save a line of code, but it would also increase the surface area of the ADO.NET API quite a bit (we'd need an Add method for every CLR primitive type, and probably one for every SQL type as well).

We have certainly thought avoid this (more along the lines of avoiding boxing than for avoiding the extra line), but we decided not to go ahead with the extension in the Whidbey release.

Also note that if you don't specify the type we'll not introduce implicit conversions on the client; we'll infer the type directly from your value. We'll only do conversions if you give us both a value and a type and they don't match. (conversions also might happen on the server-side if the target type is different, of course)

I hope this helps clarify the issue.

Pablo Castro
Program Manager - ADO.NET Team
Microsoft Corp.

re: Deprecation in ADO.NET

Eric Newton — Mon, 04 Apr 2005 17:00:00 GMT

But the addwithvalue doesnt allow us to type the parameter, leading to possible implicit conversions.

I've proposed some AddWithValue overloads that take typed parameters and set the SqlDbType for them:
http://lab.msdn.microsoft.com/productFeedback/viewfeedback.aspx?feedbackid=c334a645-8f20-4d0a-80c1-c1fdca1bc39e

re: Deprecation in ADO.NET

Phil — Tue, 22 Mar 2005 21:11:00 GMT

Jackie,

That's great I had wondered myself but had not gotten round to asking :-)

Plip.