Re: Question about Datasets and ASP.NET
- From: "Ryan" <Tyveil@xxxxxxxxxxxxxxxxx>
- Date: Fri, 23 Jun 2006 10:46:44 -0500
So I should do all my processing using SQL functions, etc stored on the SQL
server? Can you elaborate on what you mean by attributes (private member
variables of the form?)? Move away from data binding? Why did Microsoft
implement all these new databinding features if I'm not suppose to use them?
:)
Thanks,
Ryan
"PJ6" <noone@xxxxxxxxxxx> wrote in message
news:eBoYkstlGHA.4212@xxxxxxxxxxxxxxxxxxxxxxx
This is probably a good example of where you want to compile your business
layer in a separate dll, and have that support both the thin and thick
clients. Ideally your UI layers shouldn't care at all about the details of
data access - that means they won't see data sets.
Also, you may want to think about moving away from data binding - raw SQL,
even if it's automatically generated for you, does not belong in compiled
code. Any data access details that you do have in code, such as column
name mapping to particualr object fields, should be kept non-declarative
(i.e. attributes).
Paul
"Ryan" <Tyveil@xxxxxxxxxxxxxxxxx> wrote in message
news:%23toFE6slGHA.2180@xxxxxxxxxxxxxxxxxxxxxxx
I'm in the process of learning more about building my ASP.NET website to
use my SQL datastore and am a bit confused about how ADO.NET works with
ASP.NET. This Microsoft article implies that using ADO.NET with ASP.NET
applications is the way of the past because newer controls allow you to
do all your data binding declaratively.
http://msdn2.microsoft.com/en-us/library/ms178359(d=ide).aspx
However, I haven't been able to get my application to work just using
these controls. There is a lot of complex dataprocessing that needs to
be done with code. For example, once a user completes filling out a
resume form I need to create a new item in the resume table, using the
new resumeid I then need to add rows to multiple tables (lets just say
these resume forms are pretty complex, the questions are created
dynamically by backend users and each form is related to positions
they're applying for, the dynamic question table, etc). So anyways, to
cut a long story short, I'm thinking using ADO.NET Datasets and
Datatables is the way to go. I've done pretty well using these features
with my backend application (a Windows project using Windows forms - not
ASP.NET), but for the ASP.NET website user end I'm missing the Data
Sources window and the easy drag-drop capabilities of creating and
managing Datasets (including the Dataset designer). Is Microsoft trying
to discourage me from using Datasets with ASP.NET? What should I be
using to code the database queries? SQLdatasource is nice but I'm
finding it hard to use programmatically. It works nice to bind to
controls but that seems to be the only way it is usable.
Thanks for any advice.
Ryan
.
- Follow-Ups:
- Re: Question about Datasets and ASP.NET
- From: PJ6
- Re: Question about Datasets and ASP.NET
- References:
- Question about Datasets and ASP.NET
- From: Ryan
- Re: Question about Datasets and ASP.NET
- From: PJ6
- Question about Datasets and ASP.NET
- Prev by Date: Re: Find out child type in base class call?
- Next by Date: Capture WinForm Datagrid After Sort
- Previous by thread: Re: Question about Datasets and ASP.NET
- Next by thread: Re: Question about Datasets and ASP.NET
- Index(es):
Relevant Pages
|