TableAdapters in a n-Tier Scenario

Hi guys,

just wondering about peoples thoughts on using a tableadapter in a n-tier scenario.

I can see how they would be very useful in client/server type architecture, however I don't really like the idea of having a tableadapter attached to my dataset when using it in an n-tier architecture. Is there anyway to expose the dataset by itself in the client and middle tier without having the tableadapter attached?

What I would really like is to have the table adapter some how in a seperate class to the dataset, so that it is not exposed in my client or middle tier.

[575 byte] By [MatthewHunter] at [2008-1-31]

«« How C# talk with Flash Communiaction Server
»» Data Access Layer with the new DataSet

# 1

DataAdapters are acutally in separate classes then dataset. But I guess you really don't want to reference them from another tier.
So, I suggest you to build dataadapters manually (and delete autogenerated ones - I am not sure whether is possible to prevent autogeneration) or perhaps, use some sort of automation tool, such as excellent CodeSmith at www.codesmithtools.com, that builds the source code (adapters) for you.

Mihies at 2007-8-21 >

top of Msdn Tech,.NET Development,.NET Framework Data Access and Storage...

# 2

Matthew,

When you build a WebService that returns a strongly-typed DataSet, the client application can see the schema for the DataSet but does not see the TableAdapters.

I hope this information proves helpful.

David Sceppa
Microsoft

DavidSceppa at 2007-8-21 >

.NET Development Hot Topic

.NET Development New Topic

.NET Development

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech