Shareware version limitations and issues
Web Connection is available in a Shareware version that allows you to use Web Connection to build and test your applications locally. It's not suitable for deploying running applications.
The shareware version provides most of the features of the full version but there are a number of differences.
The shareware version provides the Web Connection libraries as a
wconnect.app file that wraps all the libraries. This means you can't directly look at or modify the source code of the base libraries. It also means you can't compile your application into a deployable EXE file.
Even without source code you can run your Web Connection applications locally from the FoxPro IDE by running your PRG files directly which allows you to check out and use all of Web Connection's features and build and test your application.
Shareware dialogs pop up when you start the Web Connection server and when you run your server for 15 minutes or so to notify you that you are using the Shareware version. This is to prevent putting the application into production in shareware mode. However, for development this is fully sufficient.
Due to the inability to create an EXE from the shareware version there are a number of administration features that won't work in the shareware version:
- No project file is created when creating a new 'project'
- COM Mode doesn't work - you have to run in File mode
- Remote Server unloading doesn't work (requires EXE)
- Application hotswapping doesn't work
- Build processing (build.bat) will miss files in shareware mode
All of these features are considered 'deployment' related features and so not supported in the shareware version.
Again, this is not critical when you are building your application during development, which works fine in shareware mode, but when you are ready to deploy the application you'll want to upgrade to a full Web Connection license.
Comment or report problem with topic