1. We want to keep the shared library at the root of the solution, so:

Solution
|_Shared Code
|_Client Site

Where the shared code is in one SVN repo, the client site in another. I’ve set up a demo in that way, checking out the client site, then adding the svn:external as you describe through VisualSVN. But the shared code is not visible in the solution explorer as a separate project unless I manually add it. Is that what you’d expect, and would that work correctly?

2. If you’re indeed using this in a production environment with several sites sharing common code, how do you go about deploying a single site to a live server — from the working copy, or from source control? Ideally, we’d like to be able to check everything into source control once it’s done and then deploy using FTP, which would work using a hosted svn service like beanstalk, but since the client code and shared code are in separate repos, I’m not sure that would work. I guess the other option would be to check everything in, then back out to the working copy, and to FTP deploy from the local machine or dev server.

Thanks again for a very useful post.

Best,

Jamie