Re: Typed DataSets in VS2005

Thanks Nirosh, but I'm not sure I understood all that.

I'm only talking about a typed DataSet: not about the entire data access
layer - which we code ourselves and which uses many typed datasets. At
least that was the case until now. If typed datasets now have the
connection string hard coded into them, we'll definitely not be using them
any more - for security reasons apart from anything else.


Peter

"Champika Nirosh" <test@xxxxxx> wrote in message
news:eLAvOUfcHHA.3960@xxxxxxxxxxxxxxxxxxxxxxx
VSS 2005 support auto generating the dataaccess layer .. and in that case
you are free to change the code where it hardcode the connection string so
that it will read it from a config file (obviously you have to change the
code again if you have to create/ edit the dataset again.

In my view point the automatically generated code is very good if you are
heading toward a quick concept demo or a working prototype.. but if you
are looking to develop a real extensible large-scale system, then I rather
advice you to have your own data access layer, indeed you may have some
assistance from the Data access Applcation Blocks or enterprise library.
There you will get that chance of developing a flexible dataaccess layer..
I am telling this with my experience and if you go with the auto geneated
code you will at times drive in to bottleneck of your code..

Nirosh.


"Peter Bradley" <pbradley@xxxxxxxxxx> wrote in message
news:eLioYLfcHHA.2404@xxxxxxxxxxxxxxxxxxxxxxx
Hi all,

This post is sort of tangentially related to my earlier posts on
configuration files for DLLs.

Does anyone know how to create typed DataSets using VS2005's new DataSet
designer, but with the ability to configure the connection string via a
config file? The designer seems to hard-code the connection string into
the dataset itself, which just can't be right.

The typed DataSets created by VS2005 comes with a dll.config file that
looks as though it's trying to do something like that, and which is put
with the executable at compile time, but altering the connection string
in there doesn't appear to have any effect. We've seen lots of people
asking this question, but haven't found anyone answering it yet.


Thanks in advance





Peter






.

Relevant Pages

  • Re: App Architecture: Typed Datasets, EntLib, Performance
    ... much of your application to C code and put a service layer on top for the ... application, business entities (typed datasets), business ... and data access. ... I see the value in using DAAB if I want to be completely provider ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: App Architecture: Typed Datasets, EntLib, Performance
    ... Deploying Business Entities ... and have typed datasets as the common ... Some say that they should not be filled by the data access ... layer, but rather should exist only in the business layer, which would ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: App Architecture: Typed Datasets, EntLib, Performance
    ... Deploying Business Entities ... and have typed datasets as the common library ... Some say that they should not be filled by the data access ... layer, but rather should exist only in the business layer, which would ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: App Architecture: Typed Datasets, EntLib, Performance
    ... application, business entities (typed datasets), business ... and data access. ... layer, but rather should exist only in the business layer, which would ... I see the value in using DAAB if I want to be completely provider ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: Typed DataSets in VS2005
    ... layer - which we code ourselves and which uses many typed datasets. ... connection string hard coded into them, we'll definitely not be using them ... so that it will read it from a config file (obviously you have to change ...
    (microsoft.public.dotnet.languages.csharp)