Can I install WebConnect 6.00 Beta using Setup to configure the .NET Handler so that both will work?...

of course I do not want to loose my current WC work environment...

pls advise...

thx...

Each Web Connection installation is separate and doesn't interfere with other installations. Same with individual projects.

You can configure (and switch between) ISAPI and .NET Module just by changing settings in web.config. You'll want to use the module in IIS 7 unless you have multiple virtuals being served by a single EXE.

+++ Rick ---

Are you running both 5.72 and 6.0 B2?
That is, you are serving up pages as you always had under 5.72, and, you have an instance of 6.02 B2 running as well so as you can test?

Sg

I asked Rick this very question at the Web Connect Training Session in AZ this year...

his reply was "yes I could"... then he later replied to the message board...

I am running WC 5.xx on my laptop running wc.dll and I have the WC 6.xx running his demo Web App through the .NET handler...

my only issue was that I have INETPUB on C: and my WC 6.xx on W: which is c:\developw shared as W...

I had to set the physical path of the wconnect web site in IIS7 to c:\developw\wconnect6... from w:\wconnect6... so as to not get a HTTP Error 500.19 0x80070003...

HTH... cheers...

Ian,

Are you running both 5.72 and 6.0 B2?
That is, you are serving up pages as you always had under 5.72, and, you have an instance of 6.02 B2 running as well so as you can test?

Sg

Web Connection 6.0 makes it easy to reconfigure an application for a new path using the new auto-configuration scripts that get generated as part of a new project by running <yourApp>_ServerConfig.prg.

.NET Module and ISAPI can run interchangably - nothing really needs to change. The only exception is if you have multiple virtual folders mapped to a single instance of a handler (for example, Web Connection Samples and Message board running out of separte virtuals, but served from a single EXE) - that doesn't work with the .NET handler as each handler is tied to a specific virtual directory (you'd have to have Message Board and Samples served from two separate EXEs).

+++ Rick ---

Thx for the updated information - and in fact the two frameworks work perfectly side by side each managing independent client sites: as directed the virtuals are different as is the case for folders.

In this case, I have most of my sites in 5.72 where WC lives in c:\wConnect; I have installed 6.0 B2 in d:\wConnect (with project in the default path of c:\webconnectionprojects). Naturally if I was to run both WC demo sites I am sure there would be chaos - but running client applications simultaneously there has been no issues what so ever. I've re-configured the sites to run the IIS .Net Handler (rather than IIS 7) and all app's run quick as bunny (no delays - no data related issues).

Should there be any unforeseen issues that you might be aware of given how I've structured things up - please send a note.

thx.

Serge