Reputation: 1260
I have a SQL Server stored procedure that was recently updated to accept more parameters. On one of the parameters I mistakenly assigned the wrong parameter name
x.SqlParameterName = "FOO";
So it was giving me an error saying
FOO is not a parameter in stored procedure.
What I did was assigned the correct parameter name:
x.SqlParamterName = "BLAH";
But upon running the application, it was still giving me the same error saying
FOO is not a parameter of stored procedure
Why is this happening?
Upvotes: 0
Views: 37
Reputation: 1260
It turns I out it was a simple yet very common case of deleting the contents of the project's bin folder that solved the issue. Cleaning and Rebuilding the solution wasn't properly updating the bin files.
Upvotes: 1