.NET (Core and Framework)

John Simmons / outlaw programmer wrote:

but I have a need to create the parameter list OUTSIDE of the confines of the SqlCommand object.

Pete O'Hanlon wrote:

It's a hack, but you could do it.

led mike wrote:

I'm probably missing something obvious but why is that hack?

Pete O'Hanlon wrote:

Potayto, potahto.

Guffa wrote:

Actually, the parameter should be IEnumerable<sqlparameter>. That way you can send in any kind of collection of paramters, like a list or an array.

Pete O'Hanlon wrote:

Or indeed IEnumerable<dbparameter>

John Simmons / outlaw programmer wrote:

Besides that, putting the parameters into a list would have required the extra overhead of traversing that list in order to fill the SqlCommand's internal collection object, where simply assigning the collection requires just one line of code.

John Simmons / outlaw programmer wrote:

I wrote a function in a class that accepts a stored procedure name and, curiously enough, an SqlParameterCollection, and returns a DataTable - all of the nasty sql stuff is contained in the function

John Simmons / outlaw programmer wrote:

So I want to create an instance of SqlParameterCollection.

void ExecuteQuery(string query, IDictionary<string, object=""> values); </string,>

void ExecuteQuery(string query, params object[] values);