Click here to Skip to main content
15,891,943 members
Please Sign up or sign in to vote.
1.00/5 (1 vote)
See more:
I am fixing to start a new job and the first project will be a rewrite of a VB6 application into VB.NET 4.5. I am wondering if you had the choice what you would use for data access. The database is a MSSQL database. I have worked in VB.NET for several years and have written against mySQL using our own custom methods. I wonder what the pro and cons of each type of technology I should consider. I have researched entity framework but am not very familiar. Any input would be appreciated. Thanks,
Posted
Comments
AndrewCharlz 13-Mar-14 23:49pm    
sqlclient is a good one

Sorry, but your question is too vague to answer it directly.

I'd suggest you to start here: Tutorial 1: Creating a Data Access Layer[^]
Implement a Data Access Layer for Your App with ADO.NET[^]
 
Share this answer
 
Comments
Member 10649324 21-Mar-14 13:39pm    
To clarify I would like your opinions on technologies such as Entity Framework, LINQ to SQL. writing my own custom methods, some other technology for data access?
The devil is in details.
It depends on your goals and resources (including your knowledge, experience and time).
DAL based on custom methods is good choice, but often it is an overkill and not to mention a lot of coding.
Time spent on learning EF is well spent, and DAL based on EF is faster to finish, but it is not without flaws.
I warmly suggest you NOT to chose typed data-set path, I had to use it for years and it made me an embittered man.
You can decide to learn some other ORM, but that is far beyond my scope.

P.S.
I agree with Maciej Los about vagueness of your questions.
 
Share this answer
 
Comments
Member 10649324 21-Mar-14 13:39pm    
To clarify I would like your opinions on technologies such as Entity Framework, LINQ to SQL. writing my own custom methods, some other technology for data access?
Oshtri Deka 22-Mar-14 17:20pm    
Lately I only use custom methods and Entity framework, but I'll never say they're best choice.
I have no professional experience in LINQ to SQL, but I doubt I'll ever try to use it. It's OK technology, but it's not evolving.
My choice of technology depends on data source, client's demands and how soon it must be done.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900