Copying websites not for deployment

Last post 03-31-2008 10:51 PM by Benson Yu - MSFT. 3 replies.

Sort Posts:

  • Copying websites not for deployment

    03-27-2008, 8:27 AM
    • Loading...
    • jim copson
    • Joined on 01-09-2008, 3:14 PM
    • Posts 3

    A simple question. In a small project using 2 development sites we have just shipped a website from one to the other. We just shipped the website folder with all the files. We didn't use the 'copy website' function and we are currently using the expresss versions of the software. Given that the environments are similar(sofware levels, etc) we expected to be able to open the folder at the second deveopment site as an existing web site and for it to run. However we have lots of problems which I won't go into. I just want to know if just copying the website folder to the second deveopment site and opening it as an existing web site is theoretically a valid approach or is it too simplistic?  

     

  • Re: Copying websites not for deployment

    03-27-2008, 8:58 AM

    Quite valid.  Though the code alone does not make a web site.  Since you don't go into details, all I can say is you configured something wrong.  Or not at all.

    Jeff

    Please: Don't forget to click "Mark as Answer" on the post that helped you. That way future readers will know which post solved your issue.
  • Re: Copying websites not for deployment

    03-27-2008, 10:50 AM
    • Loading...
    • jim copson
    • Joined on 01-09-2008, 3:14 PM
    • Posts 3

    Thanks for your response although I am not sure, if the approach is valid, what is required in terms of configuration as the 'not at all' comment applies. I assumed that the website folder contained all the configuration info that was required. The receiving developer just opened the web site folder as an existing WEB site. No configuration was done, in fact nothing was done except to open the the folder as an existing WEB site. Are we better off creating a new web site and copying in the subfolders and files from the existing web site folder? What are the configuration considerations at the receiving site?

  • Re: Copying websites not for deployment

    03-31-2008, 10:51 PM
    Answer

     

    jim copson:
    However we have lots of problems which I won't go into.

    Hi jim copson,

    Is there anything more detailed about "lots of problems"? As far as I know, it depends on which version of Visual Studio you are using.

    For Visual Studio 2005, since it has its own lightweight web server, simply copy all the source files to another machine and then open it via “File | Open | Web Site… | File System” (for website project) or via “File | Open | Project/Solution…” (for web application project) will work without any problem. What we should notice is that the referenced assemblies in GAC should be installed on that machine as well.

    However, for Visual Studio 2003, we should configue the copied web project as web application/virtual directory in IIS, and then open it via “File | Open | Project From Web… | http://localhost/projectName”. For this scenario, I have answered the similar issue before. Please check my reply in the following link.

    How to re-create a lost Solution file?
    http://forums.asp.net/t/1161541.aspx

    Sincerely,
    Benson Yu
    Microsoft Online Community Support

    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Page 1 of 1 (4 items)