Re: add dlls + ocxs to source safe ?

From: Ralph (msnews.20.nt_consulting32_at_spamgourmet.com)
Date: 10/13/04 

Date: Wed, 13 Oct 2004 11:01:52 -0500

"scott" <nospamscott@yahoo.com> wrote in message
news:e3caySRsEHA.2720@TK2MSFTNGP12.phx.gbl...
> one of the problems i keep find is that if OCXs and DLLs are added to VSS
> then when we come to compile a version (using "get lastest version") the
> code is copied locally but DLLs are read only so cant be recompiled. hence
> you need to check them out and it.
>
> scott
>

If you decide to keep the product components in VSS, don't keep them in the
same folder as the rest of the project. I like to keep them in a separate
production or bin area. Always do official builds from the production area -
not individual developer enviroments. This is important to avoid the
situation you just mentioned as well as providing opportunities of other
surprises. (Especially in the case of OCXs and a multiple developer
environment where a developer can easily introduce stuble changes and/or
compile against an .oca and not the published component.)

COM is based on a simple premise - once something is published (distributed
and shared) the interface is chiselled in stone and anything compiled
against that interface expects to see that interface and only that interface
(with slight wiggle room for 'additions'). Your main job is to protect and
maintain those interfaces. All ventures into "DLL Hell" stem from violating
that premise.

-ralph