Bring Back SQLHelper Class

Jan 16, 2015 at 11:49 AM
Why would you break backwards compatibility when you upgraded?

My open source project is still using version 4 because you got rid of the class in version 5 and now I can't get my project to work with the new version.

Open source doesn't pay well enough to have to fix code because you broke compatibility.

Version 4 worked well enough so I guess I will stay on that.
Jan 16, 2015 at 12:34 PM
Edited Jan 16, 2015 at 12:34 PM
FYI: as far as I know, SqlHelper was never part of Enterprise Library but was part of the pre-Enterprise Library Application Block maybe from around 2001.

See this blog posting from 2006 talking about the switch.
Jan 16, 2015 at 12:37 PM
I added the class in and it works, so I was coming here to delete this but don't see a way.

My app source code generator only executes stored procedures so it works.

I may not even need the Enterprise Library reference then.
Jan 16, 2015 at 12:42 PM
If you are only using SqlHelper then I don't think you need Enterprise Library. Compared with Sqlhelper, the Enterprise Library Data Application Block provides an additional abstraction which makes codes database agnostic.
Jan 16, 2015 at 4:49 PM
Yes I figured that out. I actually ported the SQLHelper class from the Application Block into one of my classes and everything works.

I know the code is from 2001 but it isn't like milk, if it works it saves me refactoring dozen of projects than I am ok with that.

Thanks for your answer I had already come to that conclusion this morning.