Hi!

Nice idea. From first versions of West-Wind WEB Connection to current version it is enhanced and contains so much files, that beginers easy get lost.

I would like also to add another suggestion - make system more user-friendly from the application deployment point of view. For example, install the basic modules of West-Wind WEB Connection, register a COM object for WC.DLL as a component that WC.DLL can run, then in the browser you can run ANY function of that component using following URL:

http://somehost/SomeDir/WC.DLL?Component=SomeComponentName&Method=SomeMethod&Param1=Value&Param2=Value...

After that, it will be MUCH more easy to deploy WWC applications on other computers - just register component, install basic version of WWC on the server and thats enough. Yet I need to re-configure a lot of options, as well as program COM object to make some sort of processing handler (that could be programmed in generic way to call COM object methods by described way).

In addition, it would be good to make a basic project template for the COM object creating using WWC tools. Not a demo app project, just a project that contains all WWC modules required for creating aplication, and component basic structure definition where programmer can just start coding of custom methods without any preliminary actions and changes. This will be useful, for example, to use such tools as Fournier Transformations Lists, that are not really a WEB application, but just a procedures that could be used in WWC. Yet to start programming new project, require to make a lot of configuring, changes and keep in mind a lot of things.

The point here is to split system to 2 parts - basic components required always, and add-ons. It would be good if installation and files organized by another way - that you quickly can see and work with base components, and touch only add-ons when it is really needed.

Just a suggestions, though I did not worked with WWC much enough and do not know latest version, so maybe I missed something or these ideas are not new already...

>I've been in the situation that at several occasions, I only wanted to run the setup of WWC to setup the base configuration. Which means, after the setup is done, I am removing all installed files under the wconnect directory as I don't need them. I would like also to have a setup which does not copy any file on disk. So, this would be a small setup to only apply what is necessary on the Web server and registry settings.
>
>Basically, when we do such install, this is because this is part of a server setup thus we only copy the COM VFP EXE manually, register it and apply the DCOMCFNG settings. Then we also copy the wc.dll, wc.ini and admin.asp files in the script directly.
>
>Am I the only one who would benefit of such a small setup?