Re: Deployment file locations

If you compile into an EXE you don't need your PRGs from the c:\wconnect (or other plain code path). Those will all compile in.

If you have PRG files that located in the Web folder, you don't need to deploy those either, but the FXP files you do.

FoxPro basically looks for executable files first in the VFP file cache (ie. inside of the project file) then in the current path, then any paths in your SET PATH. Web Connection also checks for files in the specific path you specified in the .wcsx (or .alb) files - it explicitly tries to run the FXP file from that path using the fully translated path.

You can also compile those PRGs into the project and that will also work, but the whole point of having the PRG's in the Web folder is so that you don't have to. The key is that the FXP files are present since that's what actually executes if the files are not in the project. The advantage of the external FXP files is that they can potentially be updated without uploading a full EXE again.

+++ Rick ---

Rick,

First of all, I want to thank you. Even after two days of training in Phoenix I was not completely convinced that I would ever be able to produce a FoxPro Westwind application. Now, against all odds, I have questions for you about how to deploy the thing. I think you should add M.W. (or miracle worker) to your signature from now on.

At my client site I have a bright shiny new Windows server 2003 running IIS 6.0. I have uploaded and successfully installed the runtime for VFP nine and Westwind connection 5.5. The data resides on another server along the same local network so I have no issues with that location. My code points to the appropriate server.

When I installed Westwind and created the project on my development machine, the PRG that starts the Westwind server was installed in C:\wconnect along with some DLLs, some .h files and a few other things. The rest of my application ended up in c:\inetpub\wwwroot\albat. In this folder are both some .alb (the extension I chose in setting up the project) and their companion .prg files.

I produced an EXE file from the project created for me in the C:\Wconnect. That project and the related exp did not include any of the PRG files found under every wwwroot.

I have read the help file about deploying, but I still can't figure out where these files go and whether or not the PRG files in wwwroot have to be bound into an exe.

Thanks,

Potter