What is best practice organize a MVC project with backend, frontend and web api?
I have a question about organizing a ASP.NET MVC project.

I have 3 different main area. Front and backend, and I have a Web API.

I want to know what is best practice for organizing such a project?

What I have done so far is to make 3 different projects so I could separete the area of which they worked on, but I have a problem with the Web API for cors.

So my question would be, is it possible to have 3 projects, or should I have to use areas? I still want to be able to separete the "concerns" (web api, frontend, backend)

Thanks in advance for any replies.
What is best practice organize a MVC project with backend, frontend and web api?
===

I have a question about organizing a ASP.NET MVC project.

I have 3 different main area. Front and backend, and I have a Web API.

I want to know what is best practice for organizing such a project?

What I have done so far is to make 3 different projects so I could separete the area of which they worked on, but I have a problem with the Web API for cors.

So my question would be, is it possible to have 3 projects, or should I have to use areas? I still want to be able to separete the "concerns" (web api, frontend, backend)

Thanks in advance for any replies.