SummaryĪ common approach to porting large apps from. If your app requires single sign-on between different sites or apps within IIS, refer to the documentation on how to share authentication cookies among ASP.NET apps for detailed instructions on supporting this scenario. Rewrite rule to rewrite subfolder requests to another web site. Figure 5-2 shows the rewrite rule as configured in IIS with the separate web site.įigure 5-2. NET, but they can be made to appear to the Internet as one web app. With this in place, separate sites on the same IIS server can coexist running separate versions of. The MVC routes include many different paths based on functionality and all start from the root of the app using the standard / in the rewrite URL will ensure the rest of the path gets used with the new URL. The app is a mix of MVC views and API endpoints. Within the large app, functionality is segmented into different routes and/or directories. Split a large web appĬonsider the common scenario of a large web app that currently is hosted on IIS in a single web site. In this chapter, you will see how different deployment scenarios can be achieved when there is a need to maintain the original app in production while migrating portions of it. NET Framework apps to ASP.NET Core in phases. In previous chapters, you learned a number of strategies for migrating large. Large apps may require a phased or side-by-side approach when porting to ASP.NET Core. Existing ASP.NET MVC and Web API apps run on IIS and Windows.
0 Comments
Leave a Reply. |