Hey Rick,

I'm looking at the prospect of a major WC application redesign and I'd like to know your recommended strategy.
The existing app needs to stay intact with the ability to make minor updates while I work on the new app. Once in place, the new app will use the same script map extensions as the existing app.

Would the best approach be to make a new project? Then I'd have different script maps would I not?

Since this is the only WC app I've ever done, I'm not sure what problems I need to watch out for.
Thanks.

If you create a new project you can use the same script maps. Script maps are site specific so while testing you're working on a different site/virtual then when you're ready to cut over - assuming you're using the same scriptmap endpoints - you can just cut over to the new version.

If you need to run side by side in the same app then that won't work and in that case you probably need to use a new scriptmap unless you create the new functionality in the same process class - script mapping is basically 1-1 from URL to process class method (or at the very least to the process class).

If you need something different it is also possible to have logic in the YouServer::Process method to decide how to route requests. You could for example use a custom prefix or a partial path segment in new requests or some other identifier and based on that decide where to route.

Lots of options.

For me - I would probably opt for a new script map because that's the easiest and built-in way to separate logic. Unless you are attached to the particular script map I think that's the way to go. If that doesn't work you can use a new scriptmap during dev until you're ready to cut over - renaming scriptmaps is pretty easy to do with a Find in Files type replace operation.

+++ Rick ---

Thanks Rick. I appreciate it.

Carl

Thinking about this further, I'm considering redesigning the app using WC6.19. With the UserSecurity table structure change I figure this is as good a time as any to do that.

It looks like I can install 6.19 along with my current version 6.0 but in a different directory but when it comes time to replace the old app with the new app, I would like to get back to having a single C:\WConnect directory just to keep things clean and simple.

WC6.0 is currently installed in C:\WConnect. If I install WC6.19 in C:\WConnect619 and start a new project with new script maps, are there any gotchas I need to be aware of when I it comes time to replace the old app with the new app?

Thanks.

Web Connection versions can sit side by side - you just need to make sure that the paths in your projects point to the right version to find dependencies.

For deployed apps it doesn't matter because deployed apps need to ship their own set of dependencies (mainly the depedendent DLLs)...

+++ Rick ---

OK. Thanks Rick.