ActiveX DLL ProjectWindows NT Server 4 (Windows Metaframe Server)IE 5.01Visual Basic 6Visual Source Safe 6
Not sure eactaly why you are having this problem, but a paradigm shift
might be in order here. When building web projects as a team, it is
often better to set up each developer machine with a local copy of the
web and all components. There are a couple of reasons. First, each
developer can check the app without worrying about other users.
Second, each developer can unit test their code with the latest builds
from other developers prior to checking code in; this makes for a
safer environment.
I find that many people are trying to use master mode development of
their websites. While this is possible, I have seen people step on
each other many times using this paradigm.
On more, unrelated, suggestion. Use MTS for all of your components.
With MTS, you will not have to completely stop services to update
components that are out of process (server packages). You will delete,
stop the MTS package and install the new component. It is much nicer
than the old method of rebooting every once in awhile when IIS did not
go down and up gracefully.
GB