My working environment:
Windows 7 Enterprise SP1, 64-bit OS, VisualStudio 2010 Premium.
My scenario:
I have a windows solution that needs to be published over a VPN to the "Live Server".
When I publish the solution to the "Test Server", it publishes fine, installs without problems, and the testers can do their stuff.
My problem:
When I publish to the "Live Server" over the VPN, the necessary files are copied over (the following files, where * represents the name of various classes, projects within my solution, etc: *.dll.deploy, the *.exe.manifest, the *.application, the *.exe.deploy) – 64 in total.
I have physically watched the copying process to verify that all the files are copied over.
The Publishing Folder Location and the Installation Folder URL are the same, as indicated on the Publish tab in the Properties of the Start-up project.
At the end of the copying, I get a VS error list with between 5-7 errors, and then a rollback starts that deletes those 64 files from the deployment location. Those errors ALWAYS include a combination of 9 specific files, and the files shown in the error list are not the same every time.
The error message:
"Failed to copy file '…filename…' to '…deployment location…' to the website. Unable to add file to '…deployment location…' The specified network name is no longer available."
While the copying took place, I pinged the "Live Server" with the –t tag to ensure that I can spot a drop in connectivity.
My request:
Is there anyone that can assist me, or point me in the right direction to sort out this problem? Is there something that I am overlooking? Any advice will be highly appreciated.
I am thinking of:
Since nothing changes between be publishing to the "Test Server" and the "Live Server" except for the deployment folder location, can I plainly copy the 64 files from the "Test Server" over to the "Live Server"?
Thanks in advance.