Plateforme Level Extreme
Abonnement
Profil corporatif
Produits & Services
Support
Légal
English
When to connect
Message
De
22/01/2005 12:11:03
 
Information générale
Forum:
ASP.NET
Catégorie:
ADO.NET
Titre:
Divers
Thread ID:
00978766
Message ID:
00979619
Vues:
31
Yes, separate projects.

~~Bonnie


>One other design question.
>
>Should I make my BizObjects part of the appliation, or
>separate projects?
>
>I ws considering building them a separate projects, compiled
>as DLL's, so that I could easily swap them out as needed.
>
>
>
>
>
>>>Sound about right?<
>>
>>Perfect!!
>>
>>~~Bonnie
>>
>>P.S. - Although, if you ever want to use Web Services, you'll need to revamp your UI to call the Web Service instead of a BO class. The Web Service will call the BO classes.
>>
>>
>>
>>
>>>Ok then, here's my plan:
>>>
>>>I will create a data access class which will have functions for
>>>creating & returning connection objects, receiving and passing to
>>>the DB queries and stored procedure calls, and the like. This class
>>>will be the only class that knows about which DB to access and
>>>any connection info.
>>>
>>>I will then create a BizObj base class that instantiates the data access
>>>class and maintains a connection.
>>>
>>>The BizObj base class will then be subclassed for each required BO. Each
>>>BO will have functions approppriate to the BO, such as GetClientByID() for
>>>the Client BO.
>>>
>>>The GUI can then instantiate the BO's and call the required functions to get
>>>or manipulate data as needed.
>>>
>>>Sound about right?
>>>
>>>
>>>
>>>>Kevin,
>>>>
>>>>No matter which way you end up doing it, keep in mind that the way to make this the most flexible is to do all your data access in a separate class. Don't put data access code in your UI classes.
>>>>
>>>>~~Bonnie
>>>>
>>>>
>>>>>Well everyone,
>>>>>
>>>>>I've gotten to different answers on this;
>>>>>
>>>>>Open the connection and keep it open, and open the
>>>>>connection when you need it, then close it.
>>>>>
>>>>>As I said in an earlier post, I dont expect to use
>>>>>this app across the web anytime soon. It is primarily
>>>>>a desktop app, which might later access the data on a LAN.
>>>>>
>>>>>So I guess I will open the connection and leave it open.
>>>>>I could always change that later.
>>>>>
>>>>>Thanks for all the input!
>>>>>
>>>>>
>>>>>>In a .Net application, do I want to create a connection
>>>>>>on application startup, or only when I'm ready to access
>>>>>>the data?
>>>>>>
>>>>>>Thanks
Bonnie Berent DeWitt
NET/C# MVP since 2003

http://geek-goddess-bonnie.blogspot.com
Précédent
Suivant
Répondre
Fil
Voir

Click here to load this message in the networking platform