CODEWITHSUNDEEP
asp.netasp.net-3.5data-access-layer
Chris
Chris

Reputation: 2303

Creating Data Access Layer for Small website

I am creating my application in asp.net 3.5. I have to make my Data Access layer, in which I am doing the traditional method of fetching/updating the data. Which is SqlConnection than SQLCommand, than SQLadapter. Will there be any other way I can create my DAL layer easily.

Specification.

  1. My website is small. Approx 7-10 pages.
  2. Database has around 80 tables.

What I know:

  1. Linq to SQL - I don't want to use it because I am not fully aware about the LINQ statement and I need to develop the application really fast. [3 days :-( ]. Also, there are 100% chances that the table structure will be altered in future.

  2. Enterprise Library: It will take too much time for me to integrate to my application.

Any other suggestion to create my data layer, quick ... fast ... and "NOT" dirty. Thanks in advance.

Upvotes: 3

Views: 929

Answers (4)

Mun
Mun

Reputation: 14308

You may also want to consider SubSonic. It's relatively easy to implement and is fairly intuitive to use. Used it for the first time recently on a small project, and despite some initial configuration problems getting it to work with MySQL, it handled data access pretty well.

Upvotes: 0

stephen776
stephen776

Reputation: 9234

Being a LINQ beginner myself, I would recommend taking the plunge and going with linq-to-sql or entity framework. I cant say for certain without knowing your requirements but theres a good chance taking the time to learn basic linq for this project would speed up development overall.

Upvotes: 0

immutabl
immutabl

Reputation: 6903

How about using Codesmith (free version 2.6) to generate a simple set of data access objects off your database? Given the small number of DB objects that you need to model I think this would be a quick and easy way of achieving your goal given the time constraints.

Upvotes: 2

decyclone
decyclone

Reputation: 30830

I would have recommended using LINQ to SQL. But, since that is a no from you, only other option I would suggest is Strongly Typed Datasets and Table Adapters generated by Visual Studio. They are old but decent enough to work in any modern application.

They are fast to create. They provide type safety. They are quite flexible for configuration and customization. Since they are generated by Visual Studio, any changes made to database can be easily reflected quickly.

Upvotes: 0

Related Questions