Rick;

I need to migrate a few procedures from a long-in-the-tooth WebConnect 5.x application to the current version, but that horse is too big to eat in one bite.

I assume I can have WC 5 and the current, modern version running on a different defined IIS website on the same Windows 2008 server?

I realize I will have to pass adequate information to the new server on the URL or within the HTML form to identify the environment... and that the domain name of the new pages will be different.

I just need to be able to share the same live DBFs while I replace a few procedures and squash a few bugs at a time...

TIA

Yes - you've always been able to run multiple Web Connection sites side by side since deployed applications are completely isolated from each other - there are no shared components.

For development pre-6.0 there was some shared stuff because of the way Web Connection installed, but with 6.0 and project folder separate 99% of that goes away with only path references back into the Web Connection framework - and you can control via pathing which framework is accessed.

The main thing you want to watch out for:

• Copying Application Project Folders
• COM Object ClassIds

Due to the way COM works you have to make very sure you don't duplicate COM ClassIds accidentally. If you copy a project file to create 'new' project, you're in effect copying the ClassIds along with project and you'll end up hosing your COM configuration. So if you copy make sure to wipe out the project's COM servers first. Likewise make sure that any of your servers have unique names that don't match existing COM ProgIds.

Other than that - projects are completely separate both on client and server in newer versions.

+++ Rick ---

Gotcha. I'll be creating a new project from scratch, so it sounds like I'll be OK.

Thanks, Rick!