Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > ASP .Net > Typed Datasets and ObjectDataSource - clever solution to the scalarparameters problem?

Reply
Thread Tools

Typed Datasets and ObjectDataSource - clever solution to the scalarparameters problem?

 
 
JimLad
Guest
Posts: n/a
 
      11-27-2009
Hi,

VS2008

We've got a CRUD app of about 300 pages with very little business
logic. As such we intend to mostly use typed datasets with a few
custom objects thrown in. Will be using Gridview, Detailsview,
Formview, Listview etc on the UI.

We need to connect the datasets to the UI through the BLL. Everyone
seems to use ObjectDataSource for this. The very obvious limitation of
this is that data modifications have to pass values as scalar
parameters, rather than as typed datarows. This seems pretty horrible
to me and I am no OO purist!

So my real question is what did Microsoft intend us to do in this
situation and what do people do in this situation. Passing scalar
values through the BLL is so completely horrible!

I know this is old news, but I haven't seen a decent solution/
workaround!

Cheers,

James

 
Reply With Quote
 
 
 
 
JimLad
Guest
Posts: n/a
 
      11-29-2009
On Nov 27, 1:04*pm, JimLad <jamesdbi...@yahoo.co.uk> wrote:
> Hi,
>
> VS2008
>
> We've got a CRUD app of about 300 pages with very little business
> logic. As such we intend to mostly use typed datasets with a few
> custom objects thrown in. Will be using Gridview, Detailsview,
> Formview, Listview etc on the UI.
>
> We need to connect the datasets to the UI through the BLL. Everyone
> seems to use ObjectDataSource for this. The very obvious limitation of
> this is that data modifications have to pass values as scalar
> parameters, rather than as typed datarows. This seems pretty horrible
> to me and I am no OO purist!
>
> So my real question is what did Microsoft intend us to do in this
> situation and what do people do in this situation. Passing scalar
> values through the BLL is so completely horrible!
>
> I know this is old news, but I haven't seen a decent solution/
> workaround!
>
> Cheers,
>
> James


Anyone?
 
Reply With Quote
 
 
 
 
Patrice
Guest
Posts: n/a
 
      11-29-2009
Hi,

Hoping someone more familiar with this will help...

I've never been a big fan of typed datasets but if I remember you can choose
the Update style either by providing parameters for each value (is this what
you are talking about ?) or by providing a single object. See :
http://quickstarts.asp.net/QuickStar...atasource.aspx

Can't you do that with typed datasets ?

For now I'm using Linq but DynamicData could be perhaps also helpfull
(http://www.asp.net/(S(ywiyuluxr3qb2d.../DynamicData/). Note that
thought it builds your site from the schema, you can still create and
personnalize all this i.e what you get out of the box is just the default,
you are still free to customiez the result at will...

--
Patrice


"JimLad" <> a écrit dans le message de
news:4bf8bba1-5879-4ee5-8844-...
On Nov 27, 1:04 pm, JimLad <jamesdbi...@yahoo.co.uk> wrote:
> Hi,
>
> VS2008
>
> We've got a CRUD app of about 300 pages with very little business
> logic. As such we intend to mostly use typed datasets with a few
> custom objects thrown in. Will be using Gridview, Detailsview,
> Formview, Listview etc on the UI.
>
> We need to connect the datasets to the UI through the BLL. Everyone
> seems to use ObjectDataSource for this. The very obvious limitation of
> this is that data modifications have to pass values as scalar
> parameters, rather than as typed datarows. This seems pretty horrible
> to me and I am no OO purist!
>
> So my real question is what did Microsoft intend us to do in this
> situation and what do people do in this situation. Passing scalar
> values through the BLL is so completely horrible!
>
> I know this is old news, but I haven't seen a decent solution/
> workaround!
>
> Cheers,
>
> James


Anyone?

 
Reply With Quote
 
JimLad
Guest
Posts: n/a
 
      11-30-2009
On Nov 29, 9:17*pm, "Patrice" <http://scribe-en.blogspot.com/> wrote:
> Hi,
>
> Hoping someone more familiar with this will help...
>
> I've never been a big fan of typed datasets but if I remember you can choose
> the Update style either by providing parameters for each value (is this what
> you are talking about ?) or by providing a single object. See :http://quickstarts.asp.net/QuickStar...lref/data/obje...
>
> Can't you do that with typed datasets ?
>
> For now I'm using Linq but DynamicData could be perhaps also helpfull
> (http://www.asp.net/(S(ywiyuluxr3qb2d.../DynamicData/). Note that
> thought it builds your site from the schema, you can still create and
> personnalize all this i.e what you get out of the box is just the default,
> you are still free to customiez the result at will...
>
> --
> Patrice
>
> "JimLad" <jamesdbi...@yahoo.co.uk> a écrit dans le message denews:4bf8bba1-5879-4ee5-8844-...
> On Nov 27, 1:04 pm, JimLad <jamesdbi...@yahoo.co.uk> wrote:
>
>
>
>
>
> > Hi,

>
> > VS2008

>
> > We've got a CRUD app of about 300 pages with very little business
> > logic. As such we intend to mostly use typed datasets with a few
> > custom objects thrown in. Will be using Gridview, Detailsview,
> > Formview, Listview etc on the UI.

>
> > We need to connect the datasets to the UI through the BLL. Everyone
> > seems to use ObjectDataSource for this. The very obvious limitation of
> > this is that data modifications have to pass values as scalar
> > parameters, rather than as typed datarows. This seems pretty horrible
> > to me and I am no OO purist!

>
> > So my real question is what did Microsoft intend us to do in this
> > situation and what do people do in this situation. Passing scalar
> > values through the BLL is so completely horrible!

>
> > I know this is old news, but I haven't seen a decent solution/
> > workaround!

>
> > Cheers,

>
> > James

>
> Anyone?- Hide quoted text -
>
> - Show quoted text -


Hi Patrice,

Thanks - I'm aware of that - the problem is that ObjectDataSource
can't use a Typed Dataset Row as there is no parameterless
constructor.

Most of our code is in stored procs at the moment and there are a lot
of joins etc. Rewriting everything in LINQ (we are all very good TSQL
coders) doesn't seem very appealing.

Anyone else got any other thoughts on the original question?

Cheers,

James
 
Reply With Quote
 
 
 
Reply

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
SqlCacheDependency and Strongly Typed Datasets chris ASP .Net 2 02-25-2006 02:54 PM
Strongly typed datasets and nested repeaters Duncan Welch ASP .Net 3 04-07-2005 03:37 PM
Problem with Typed Datasets and Web Services Sparky ASP .Net 0 11-15-2004 09:02 AM
Strongly typed datasets and XML Big D ASP .Net 1 02-17-2004 11:32 PM
Traditional Collections and Objects or Typed Datasets ? Rob Thomas ASP .Net 3 08-26-2003 09:06 PM



Advertisments
 



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57