Hey Rick,

If there is a topic about this in the docs, please direct me to it - I couldn't find one.

I need to move WWWC to a new dev machine and I wanted to check with you to see if I have the right idea.

I have only one WC app and it's been years since I've done this but the last time I did I *think* I...

• Enabled IIS (done)
• Installed WWWC
• Created a new project on the new machine with the same name as the existing project on the old machine
• Copied the files from the project folder on the old machine to the corresponding folder on the new machine

Does this sound like the right approach or is there something I'm overlooking?

Thanks,
Carl

Assuming this is a somewhat recent Web Connection app (v6+), it should be much easier than that:

• Copy your files
• Run Start-FoxPro-IDE-in-Project.ps1 (launches in the Deploy folder)
• Compile your project

If you use the Web Connection Web Server or IIS Express you're done: Just LAUNCH() and you should be good to go assuming your environment was set up in the old project to find everything. If not fix your config.fpw paths or your environment loader program or whatever.

If you need to configure IIS to run:

• Install IIS (use Install-IIS-Features.ps1)
• Go back to your project and run DO yourProject-serverConfig.prg

This should configure IIS.

All this is based on the standard Web Connection project structure (ie. web and deploy folders off the project root).

Older Projects

If this is an older project that doesn't use the newer Web Connection project structure, or doesn't have the powershell launcher or the server configuration PRG you can:

• Create a new project
• Copy missing files from there into the old project

Or if you really want to take advantage of all new features, migrate your old project to the new project by copying all files over, then making sure all the dependencies get pulled in via a loader program (or in OnLoad() if just a few). You can take a look at the wcdemomain.prg file to see what can get set in OnLoad() - basically SET PROCEDURE declarations, SET PATH settings and any environment settings.

Finally you can then add/change the YourAppMain.prg and the Process() method to map your extensions to the old Process class(es) files.

    CASE lcExtension == "moa" 
        DO MyOldAppProcess with THIS

+++ Rick --

Thanks Rick,

I'll give it a shot.

Carl