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?