[RESOLVED]Migrating classic ASP site to ASP.NET MVC page by page

We have a large site written in ASP/VBS and we’d like to
migrate it step by step into ASP.NET MVC. We decided to do the migration page by page. This means that we have to use the two technologies in parallel and some pages would run on the original site others would run inside an ASP.NET MVC application. These two
sites would link to each other invisibly to the user. If we were able to implement this system, we could migrate the ASP application from page to page keeping the original functionality intact.

Our
biggest problem is session handling – more specifically keeping two sites’ session data synchronized. What would be the best solution for this? Are there any already existing ways?

Our
approach is using named pipe binding. This means that we have the original ASP application (having as little change in the code as possible) and a WCF application in parallel. Both have their own sessions and they don’t have access to each other’s. The session
handling of the original ASP site will be replaced with a COM component which will communicate with the WCF service via named pipe binding. These two components would be responsible for keeping the sessions in sync.

There are some open questions we would like to ask

  • Are
    there any better solutions than this?

  • If
    there isn’t, then is this approach reasonable?

  • Is
    this solution scalable enough for being used in a site serving 3000 concurrent users?

    • What
      are the limitations of named pipe?

    • Do
      we have to expect performance problems?

  • Is
    it possible to keep session timeout in sync? (I mean are we able to avoid the situation when one of the two sessions expires while somebody browses the other site? Can we solve this without using any workarounds? )

  • Is
    there a way to replace named pipe by using WCF for instance?

  • Do you know any other risk factors?

Leave a Reply