I'm working on a library that is shared accross multiple projects. This library is composed of a number of dlls. I am having difficulty figuring out a reliable way to lay out the project structure. I am using Visual Studio 2005 on WinXP.
I've got the library dlls in c:\my_project\library\bin, and the project executable in c:\my_project\bin. I want to keep the bin folders separate from each other, so I add c:\my_project\library\bin to the PATH variable and everything works okay.
Now suppose that I've got a second project with the same structure: c:\my_other_project\library\bin contains a different version of the library and c:\my_other_project\bin contains a completely different set of project binaries.
In this case I need to update my PATH variable every time I switch which project I am currently working with and I cannot launch both projects at the same time.
I think that this is a case for using SxS assemblies, but I can't find any good documents on creating the assemblies (and more importantly, getting the build process to do it automatically and getting the debugger to walk into the SxS folder).
Does anyone have any suggestions that would allow me to set this up without manual configuration changing? I need to be able to run outside of the debugger, so please don't suggest that I use the settings in the debug tab to set the path... I do that already when debugging.