asp.net - Run duplicate IIS websites on same database -


I need some guidance in the "best practice" for the following scenario: I have a product that has an ASP.NET Website and native smartphone app for android / ios / wp that use website urls to call web pages.

We want to transfer the website from "www.ourdomain.com" to a subdomain like "www.login.ourdomain.com"

This means that we need to update The app is going to point to the new URL which is not a problem. But as we all know, not all users update their app instantly, so we want a "cross over period", where we operate a website on both URLs.

This will use the same database, but the ASP.NET site code will be slightly altered to the new subdomain site.

Is there any problem in crossing this kind, where 2 ASP.NET sites share the same database? (All IDs in DD have been automatically increased, or GUIDs)

Any help, suggestions or concerns are greatly appreciated

I have no problem using the separate service URL for the existing Mobile App (Old URL); Mobile app update (new url) and website I'll call it a proxy.

There is a regression test with the latest changes for the important app mobile app (the old one and the new one).

It would be great if the deployment is completely involved.

Comments

Popular posts from this blog

Pass DB Connection parameters to a Kettle a.k.a PDI table Input step dynamically from Excel -

multithreading - PhantomJS-Node in a for Loop -

c++ - MATLAB .m file to .mex file using Matlab Compiler -