Ok so this is more of a .NET question than LLBL specific, but I'm hoping some other folks here have dealt with this situation:

Our DB has hundreds of tables and my LLBL DAL and DALDBSpecific projects are getting quite large. Right now I am using Project References to reference these libraries to my BLL projects.

I would like to give VS a little breathing room and change these to regular DLL references, so I can get the DAL/DALDBSpecific projects out of my solution.

Given that we make DB changes and rebuild the libraries maybe once a week on average, I am concerned about whether making this change will cause headaches. ie, will the new libraries be copied over on the next build, or will VS continue to use the old libraries previously copied to the build directories?

Given that these libraries are referenced by dozens of BLL libraries in our project, having to re-reference them anytime we regenerated LLBL would be annoying at best.

Anyone have experiences doing this? Good, bad, ugly?

Thanks.

Any dlls you reference should be copied to the output path everytime you build the project. Except if they are already there and they are identical to the ones in the source folder.

You can also use project "post build" actions to force copy of the dlls to the required path.