Rick -

Using Web Connection 7, there is a problem if you use something other than the default value for the Virtual when creating a new project with the Management Console.

Doing some testing, I ran the Console and selected 'Create New Project'. I set the 'New Project Name' to MyProject. On the next screen, the 'Virtual' entry defaults to MyProject but I changed it to MyVirtual.

I finished the process and the test hit works fine using the default file-based .NET handler. However, if I try to switch to COM mode from the module administration page, the test page then shows..

Unknown application error
Invalid Com Server ProgId: MyVirtual.MyVirtualServer

The new web.config file gets created with ComServerProgId using the virtual name, instead of the project name. If I manually change it to MyProject.MyProjectServer, then COM mode works.

- Mike McDonald

Thanks Mike.

Yup - the template is wrong.

This in templates\ProjectTemplate\Web\web.config is:

<add key="ComServerProgId" value="<%= pcVirtual %>.<%= pcVirtual %>Server" />    

but should be:

<add key="ComServerProgId" value="<%= pcAppName %>.<%= pcAppName %>Server" />    

Fixed for the next update which will be soon.

+++ Rick ---

Rick -

In \Templates\wconnect_override.h you have a few commented settings to demonstrate how the defines can be reset. However, there is no UNDEFINE for the BOOTSTRAP_VERSION..

*!* #UNDEFINE DEFAULT_HTTP_VERSION
*!* #DEFINE DEFAULT_HTTP_VERSION	"1.1"

*!* #UNDEFINE DEFAULT_HTTP_VERSION
*!* #DEFINE BOOTSTRAP_VERSION       3

- Mike McDonald

Thanks fixed.

Next update should go out by next week that'll have these fixes in it.

+++ Rick ---