This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
Hello,
We have a web API that has been running smoothly for 3-4 years. Now I want to upgrade it to Core Web API. I use logging, basic authentication, OAuth, and Unity in my Web API. Will I have a lot of problems with the upgrade? May I have your advice and suggestions? What should I pay attention to?
Thank you.
What should I pay attention to?
The openly published migration documentation.
Migrate from ASP.NET to ASP.NET Core
Migrate from ASP.NET Web API to ASP.NET Core
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(211.20000000000002, 61%, 30%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EBS%3C/text%3E%3C/svg%3E)
common issues I have run into:
1) stricter binding rules
2) no xml request / response support by default
3) 3rd party library doesn't have .net standard or core support
4) use of HttpContext.Current (migrated to middleware)
5) session not locked (should not be using with webapi anyway)
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(73.60000000000001, 90%, 17%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EZL%3C/text%3E%3C/svg%3E)
Hi @Cenk ,
.NET Core is a cross-platform rewrite of .NET Framework. There are many breaking changes between the two frameworks. You can refer to this article to understand the differences between ASP.NET and ASP.NET Core.
Then, when migration, you could refer to the following articles to set the configuration, API controller and so on.
Migrate from ASP.NET to ASP.NET Core
Migrate from ASP.NET Web API to ASP.NET Core.
Besides, since you are using logging, basic authentication, OAuth, and Unity. For this package or class library, you also need to change. In many cases, a replacement NuGet package exists to fill in any gaps left between .NET Framework and .NET Core. In rare cases, you may need to find a third-party solution or implement new custom code to address incompatibilities.
[Note] When using or install the package, you'd better to check the package target framework, make sure it apply to the project version.
Here are some relates articles about logging, authentication, and Identity, you can refer to them:
Logging in .NET Core and ASP.NET Core
Introduction to Identity on ASP.NET Core
Simple authorization in ASP.NET Core
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
Best regards,
Dillion
In my ASP.NET Web API, I used a generic repository, unit of work and unity dependency injection. Can I use them in Core?
generic repository and unit of work are just a design patterns and will work fine with asp.net core. If you used nuget packages for them, just be sure there is a .netstandard or core version.
Unity has support for asp.net core.
Can I log into the SQL Server database?
core has several libraries for accessing sqlserver
I am planning to use Serilog (how-to-implementation-serilog-in-asp-net-core-5-0-application-with-database) but I wonder if I can just log exceptions from a central from a single point?
I want to improve at the same time as upgrading. In my Asp.net Web API application, I was using class libraries for Business Entity, Business Service, and DataModels. If I change all these class libraries as folders within the new API project, will I gain anything besides reducing the complexity?
this is probably an anti-pattern, and allows easy breaking of separation of concerns.
In the Business Entity class library, there are 30 entities. I want to use them in my new core 6 API. Should I create them one by one which is disappointing or can I import them all?
the api should not use entities for parameters or responses. the api should only use them when accessing the data layer.
In my Asp.Net Web Api, I used code first with EF. I want to use the same database and the entities, should I use the database first approach? Can you help me?