if you use React, be sure to think about it in a front-end way. Previously, our background management was developed with Ant.Design + .NetCore, and our solution is to separate the front and rear ends. uses this scheme, which means that the front-end related code does not need to be managed in a .net project, but can be separated from a separate project directory . Therefore, we do not use .NET 's View view layer for template rendering. .net only implements the interface, and the front end is called through Ajax. Then using the static resources of the Nginx hosting front end, when it is detected that the access route belongs to the back-end interface, the request is forwarded to .NetCore and deployed using Docker.

because using React must involve build tools such as webpack, the front-end code must be compiled before it can be used. Therefore, the use of front-end separation can effectively decouple the front-end and back-end development process. This is a more recommended option.

of course, if you have to use the .net View view layer, the development environment can consider changing the webpack memory read and write to the hard disk read and write, and write the compiled code to the .net view directory. However, this plan is not recommended.