Sharing .NET DLL's across projects

[rhj4]

I have a VS 2010 .NET4.0 project called RoseGarden that contains 16 separate LINQ class projects. These represent reusable code that is shared by multiple website projects. We are using no other tools except Vault and VS 2010.

Each Rose Garden project may refer to other Rose Garden projects, and each generates a single DLL for this project. I have created a separate folder (lib) that contains a shared copy of all of the DLLs. After rebuilding the Rose Garden, VAULT will determine which DLLs in the lib need updating and a Get Latest will refresh them

The Rose Garden code is in one Vault Repository and my web site projects code is in different repository. Checking in web site code causes it to be propagated to a website that is accessible for testing of the deployed code.

I am trying to work out a simple development process. Right now, the process is:
1) Update any of the Rose Garden project classes
2) Check out the bin folder and everything beneath it as well as the bin folders of any projects that this project depends on. If I don't do this, the compiler won't be able to update the dll and psb files.
3) Compile the code.
4) Check in all bin folders that have been updated (and keep them checked out)
5) Refresh the shared library to get the latest version

Then I switch to the web site project and right click on each DLL that needs to be updated and select "Update Reference".

At this point, I can test and debug. By sharing the .psb files, I can even step into the Rose Garden code and watch it execute.

Ultimately, this process works, but it is cumbersome. Lots of checkouts and check ins. What I am looking for are ideas and recommendations to make the process simpler and faster.

[lbauer]

I could use more information.

VAULT will determine which DLLs in the lib need updating and a Get Latest will refresh them

Are you using a build process, like CCNET? Or are you using Shadow Folders?