Rick,
I finally got off my butt and decided to install your latest and greatest (6.21). I am installing on an old win 7 pc that is my main wwwc dev box. IIS has various test sites installed using a wc.dll from 5.63.
Installation went fine without errors, but a few comments that you might want to deal with in the setup.
- After install you try to open https://localhost (i had no httpS) available so this resulted in an error.
- The app pool created by setup did NOT activate 32 bit.
- The shortcut that you generate for my new project did NOT properly call the prg to load up my new app. As such, the demo pages did not work.
Once I fixed the above, all was fine.
A few more things I noticed that I wanted to share.
- The Web Connection DLL Version: Web Connection 6.20 (ISAPI Handler) (should be 6.21 i would think?)
- When using the admin page, it says "You are accessing this request unauthenticated!" - This is not true. It did a 'basic auth' and i logged in with my usual OS admin creds...
- I noticed this file bld_Sophioftp.prg was created by setup, but when i run it fails, because setup did not create a project for me. I created a project in the 'deploy' folder named Sophioftp and then added SophioFtpMain to it and tried again. This time I got an error. I then opened the project, poked around, and then figured i would try again, and it worked fine the second time.
- I wanted to play with the hot swapping feature. I copied the newly created exe for my test project to Temp... and then placed the server in COM mode. I clicked hot swap and got "Can't find or open page UpdateExe.wc"
The HTTPS Url I believe is browsers now forcing https as the default. There's no way to automatically install a certificate so this is likely always going to be broken going forward.
App Pool: Not sure. That's likely because the app pool already existed. When a new one is created it'll set the flag, but it won't change it if it's already there.
PRG file loading? Not sure on that either. What was it calling?
+++ Rick ---
What I should have said was that the config.fpw file is calling 'do wcstart' - For some reason I assumed that the shortcut generated in my project folder would start 'my project', so i was thinking it would point me to the exe or the mainline prg you generate something that actually starts wwwc listening for web requests.
For a first time user it would not have been obvious how to use the setup stuff you just built for them.
I suspect you are thinking 'had this been a totally green machine' my experience would have been different.
config.fpw
isn't meant to start your application - it's supposed to just set up your environment to run your application. It would be rude to have the application start.
You do need to follow the directions to get started. The new Project Wizard shows information on what to do to start your project after creating a new project and if you look on the Web Connection menu you can start the demo from there.
+++ Rick ---