Limitations / Problems with ObjectDataSource

Guys,
Can anyone help me in understanding the Limitations / Problems with ObjectDataSource in .NET 2.0 and 3.5 framework? I have heard that this is not a best practice to use ObjectDataSource. We are going to create a new application with SOA and SaaS model. We want the application be very much flexible and easily adoptable.
Please suggest me.
saj_37ukAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Richard LeeSoftware EnthusiastCommented:
ObjectDataSource Limitations:

1. Tightly coupled to databound control.
2. Tightly coupled to select/update/delete methods
3. Event lifecyle difficult to follow especially when interacting with other complex controls.
4. Event firing out of your control.
5. Hard to extend application.

A better loosely coupled and more flexible data access layer is appropriate for your SOA and SaaS model. To increase reliability and decrease development time an ORM such as LINQ or Entity Framework can be used.

I would strongly advised against using ObjectDataSource a model such as the following could be used.

             <-- Lightweight DTOs                <-- ORM DTOs
Presentation    <--    Business     <--    LINQ/Entity Framework/etc    <--    Data Source
-------------------------------------------------------------------------------------------------------
 Presentation           Business                                    Data Layer
     Layer                     Layer
-------------------------------------------------------------------------------------------------------
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
saj_37ukAuthor Commented:
Thank you very much!
Do you have any other suggestion for using with SOA & SaaS model? We are planning to include CSLA framework.
0
Richard LeeSoftware EnthusiastCommented:
I am not a fan of the CSLA framework however it works and caters for concurrency.

To support loose coupling & separation of concerns (SoC) you may want to look into a UI design pattern/framework. Since you are using ASP.NET the ASP.NET MVC Framework springs to mind. http://www.asp.net/mvc.

This ensures that all logic that handles functionality can be seperate and therefore can be handled by a service outside of the UI. You can also look into the Model View Presenter (MVP) pattern. Almost the same but you can choose your preference.
0
saj_37ukAuthor Commented:
Thank you very much for your open suggestions. I'm accepting this as a solution of my query.
0
Richard LeeSoftware EnthusiastCommented:
Thanks but I don't think you prompted to close the solution rather than accept.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
.NET Programming

From novice to tech pro — start learning today.