We have recently installed a Visual Source Safe solution on our network and we are currently experimenting with deploying from VSS to our live servers. We've hit two issues that while deploying that we think can probably be handled easier, we're just not sure what we should do.
We place all 3rd party .dlls included in a site within the App_Code\Libraries folder and then we add a reference to that file, which copies those files and their .refresh files to the bin folder. Every file in the project EXCEPT the dlls in the bin folder are in source safe and get pushed to the live server when we deploy, but the dlls in the bin folder don't so then the site errors out with the message that it can't find the required assemblies. There doesn't seem to be an option to add them to source control either. Then what we have to do is FTP the .dll files into the \bin on the live server. Seems like an unecessary last step, and we'd like it so that the .dlls just get pushed when we deploy from VSS. What could we do to correct that?
The second issue is a more minor one, but it deals with connection strings in web.config. We point the web.config for the dev site to a dev version of the related DB, so when we push changes the web.config gets pushed with the dev connection string to the live server. Is there a way to have the deployment ignore connection strings in web.config so that all other changes are recorded and deployed? Or will we just have to comment/uncomment the dev and live connection strings just before deploying?