Datadapeters, connections, datasets, parameters. should we put them in data classes or in the buziness classes.
I think Queries, views, columns we should put these in data tier , right
Thanks
should we put our ADO.Net objects in data tier or biz tier
Hot Topic
- Transactions across WebServices
- Can't do a rollback after Update
- How use c# ADO.NET to insert the data in sql2005
- Freezing TCP SocketListener
- Getting WebException on every other attempt to UploadData
- MS NET FRAMEWORK 1.1
- Is there a way in the .NET Framework to get an IBindCTX?
- Sockets: two way comm. and extended conversation?
- Getting IP Addresses
- socket not released
.NET Development
- Listboxes: Configuring how it selects items as you type
- Set cookie from IE hosted windows user control
- IE Hosted Form not working on Windows Server 2003 w/ SSL
- How to compare 2 xml files?
- Comparing two data tables
- TableAdapter Update problem
- problem setting page.title asp.net 2.0
- SQL Express Connection Problem - Please Help
- loading usercontrol programatically
- Use of ClientScript.RegisterClientScriptBlock
should we put our ADO.Net objects in data tier or biz tier
AYankeeCat
http://www.microsoft.com/downloads/details.aspx FamilyID=a8381e9c-884d-4cb2-9dbe-255c2790634b&DisplayLang=en
http://www.microsoft.com/downloads/details.aspx FamilyId=A08E4A09-7AE3-4942-B466-CC778A3BAB34&displaylang=en
http://msdn.microsoft.com/practices/compcat/default.aspx
Pinakee
As a rulle of thumb ADO.NET has to be in the Data tier logic. However, there are situations when Business tier needs a direct access to the database. It rarely happens though. Further more you should consider encapsulating your ADO.NET logic into a data access helper components in the cases where you have to deal with different data stores.
Look up patterns&practices documentation. They've got all these topics covered there.
Cheers,
Dmitry
Tunes
move2mars
ADO.NET objects are responsible for retrieving and persisting information to a data-store.
Your Business Objects (which are in the BL), should not need to know to where they're being persisted, or from what data store they're coming from. I mean: a business object does not need to know that it has to be persisted in an XML file, a Relational Database, or something else...
A Business Object does not need a connection to a DB, it does not need to fill itself from the DB. The Data Layer is responsible for that.