Programmers Stack Exchange is a question and answer site for professional programmers interested in conceptual questions about software development. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I plan on migrating a website from PHP to ASP .NET MVC. However, since the website is large and this migration can't be done in a short time I plan to use both MVC and PHP pages together. So the idea is to replace each PHP page or group of pages with an MVC equivalent.

I have to refactor each page and rewrite it overall anyways so I thought I might as well move to the ASP .NET MVC framework for various reasons.

The question is, does anyone know what are some of the problems I will face while doing this?

Here are some I thought of: - Logins - I plan to overcome this with an ajax request to the ASP .NET website on the background and keeping the login information separately for asp .net. - Sessions - I'm not sure how I can share sessions or if I will even need to.

Other than that, I'm not sure if anything else will arise.

Anyone experienced that have a few things to say?

share|improve this question

closed as not constructive by Jim G., MichaelT, Yusubov, Glenn Nelson, gnat Feb 11 '13 at 7:38

As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance.If this question can be reworded to fit the rules in the help center, please edit the question.

Yikes, you plan to do this in production? Is there something preventing you from writing it again in ASP .NET and then switching over? Serving both concurrently sounds like a very disaster prone scenario to me. – Tim Post Feb 11 '13 at 1:54
This worries me greatly... – Simon Whitehead Feb 11 '13 at 3:28

I'd recommend that you develop the ASP .NET MVP as a sub-service layer to the existing PHP, and then slowly replace all functionality in the ASP. Once that is done you can then build a new top layer in .NET and switch over.

You do this by having the ASP.NET service listen to the localhost on a different port (i.e. 1080). Each time a request comes into the PHP code, you can slowly replace chunks by passing the call to the ASP.NET service as a REST API request.

Over time the majority of the business logic will be moved to the ASP.NET service, and then you can switch over with a new layer that doesn't use the REST API.

share|improve this answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.