Setting up Delphi 5 as an enterprise development system
From: Dennis <temp223_at_ipipeline.net>
Date: Thu, 24 Feb 2000 16:21:12 GMT
Message-ID: <YTct4.269$Dl1.12933234_at_news1.van.metronet.ca>
My shop is going to be doing some development in D5, and I'm trying to wrap my brain around how I'm going to set up the environment. I've already written a component, which I suppose will have to be explicitly installed on each workstation. OK, no problem. But there is/are also going to be a lot of programs (geez, going to need version control too), which will use a lot of shared objects.
Date: Thu, 24 Feb 2000 16:21:12 GMT
Message-ID: <YTct4.269$Dl1.12933234_at_news1.van.metronet.ca>
My shop is going to be doing some development in D5, and I'm trying to wrap my brain around how I'm going to set up the environment. I've already written a component, which I suppose will have to be explicitly installed on each workstation. OK, no problem. But there is/are also going to be a lot of programs (geez, going to need version control too), which will use a lot of shared objects.
So what I'm wondering right now is
- should my programs share the units (and the objects they contain) as source-code-level .PAS files, or as compiled .DCUs (if the latter is even possible)
- Obviously these things are going to have to be in some kind of shared directory. Under environment options / library in the Delphi IDE, there are a couple of choices - the two that seem to make sense are Library Path and Browsing Path. Is there any particular reason why one is better for this purpose than t'other?
I realize there are probably no hard-and-fast rules, and there may not even be strong reasons for doing it one way or the other. Even that is useful data. I'm hoping there are people out there who are using Delphi in an enterprise (multiple programmer) environment, who can give me pros and cons and the benefit of hindsight.
TIA Received on Thu Feb 24 2000 - 17:21:12 CET