MVC5 project turn .Net Core 2.2 Learning and filled pit recording (1)

Process all their own way, just correct me wrong places. . .

Old project too bloated, and all requests are submitted to a api, so when api hang, basically all projects paralyzed out.

In the end of April, the project will be determined with a micro-rewrite service, the beginning of time, hoping to find .net framework of micro-service solutions, and finally found, not one. . . And the development of a person, rewrite time is difficult to control, we decided to use .Net Core to rewrite based, focusing on the code migrated, so you can save a little time.

New project uses Ocelot do apigateway, be forwarded api, IdentityServer4 authentication.

ORM old project using NHiberante, but always felt NHiberante too bloated, new project development time, found a new ORM sqlsugar, but great differences in syntax and grammar of sqlsugar NHiberante, for the project for the migration project is too big , we do still use NHiberante, so when retired and sit and then re-wrote sqlsugar, grammar and then try to synchronize replaced with sqlsugar.

 

Guess you like

Origin www.cnblogs.com/wangpengzong/p/11102764.html