Hi Tom!

>We are discussing how we will do this. Some concerns are who has the source code and who can modify it? There are many ways that this can be done but we are attempting to determine the good and bad points before we get too deep into this subject.
>

I agree with you. We have just recently started .Net programming and at this time only a small percentage of time is for .Net programming. The majority is still working with FoxPro. With that in mind, we do not have a set way to deploy applications and developer components. I am trying to figure out the better ways of handling these procedures before our department gets deeper into .Net programming where it will be a little harder to change policies.

>A suggestion from one of our developers is to use VSS to maintain version control. Make it available to the original developer (this can include additional developers in another scenario) and use MTS to deploy the component. Again, we have a lot of work to do before we will be satisfied with any scheme.
>
>At our workplace we have many developers and two main departments. We have what I term a “cubical mentality”, in more ways than one. We think inside the cubical and nothing filters out of our specific areas.
>

We have a small department here with a few database and web programmers. This department is very new to .NET and I am setting the precedence for the other programmers here. I want to setup a set of procedures that overall will last, be efficient, and make sense. Thanks Tom for your input and any other suggestions would be most helpful!