Is there any way that the compiled .Net dll's can be shared or

compiled on to the server so that developers do not have to wait for

the compile each time?



The project I am developing will be a mixture of .Net assemblies with

aspx 

pages and existing COM+ components, so I need to ensure that when 

individual team members are working on a local version of a particular

assembly/project they have the latest version of any other assemblies

it 

may interact with.



In the past when developing large applications with VB and multiple

COM+

dlls, the compiled dlls would be stored on a server. Users would

create 

the components locally, push them up on to a development server for 

others to pull down the objects using a simple program that would copy

and 

register the dlls locally on their pc so they could develop with the 

latest objects.



I am trying to map out a procedure that will combine these two methods

in some way.



Is this feasible?

...Or recommended! :¬)



There seems to be different ways, and I think the new method is going

to 

be a change from the old VB method and the Visual Interdev source

control.



I'd be very grateful if anyone could offer any advice on this.



Many thanks



Colin