Hello guys,

 I am in doubt what solution is the best for a case that we have in hand.

We have to develop a web application (ASP.NET 2 with loads of reports which I think we will use SSRS) and on this particular project there are about 100 tables involved.

As you know we can add a DataSet for each table, that would either generate Select/Insert/Update/Delete statement or we can have our own one written as store procedure and get DataSet to use those existing one for a better performance.

Now is Visual Studio DataSet a good solution or are we better of to write our own classes (Business Object) for every table with Insert/Update/Select method and then call those methods of the object.

There are some ORM (Object-Relational Mapping) application out in the market that we can also buy to generate these classes for us to, but which one is the best and the most efficient solution? What are the advantages and disadvantages of each one?

I appreciate any help and suggestion.

Regards,

Mehdi

Hi Mehdi,

Whether to use an ORM depends on the scale of your app.

When you have a big solution, your business logic might change often or you're considering about the flexibility of it, you can try to use ORM.

However, if you need rapid development, you can just use a DataSet as the solution.