Transferring the client to the web. ASP.NET Core MVC or ASP.NET Core Web API + Angular?

Question

Angular

Now in the project, the server is WCF services, and the client is a WPF application.
We decided to move the project to the web. Services are easy to migrate, but there are doubts about the client architecture.
We see two options: ASP.NET Core Web Api + Angular / ASP.NET Core MVC. We only consider the .NET stack, as the experience is mainly on it. While the client is one window with a bunch of fillable forms. In the future, we are planning something like a drag and drop interface.
Explain the pros and cons of one and the other approach

Answer 1

Depends on experience with APIs, building applications with "responsive" frameworks like Angular.
Try to implement 2 approaches on trial applications with a few interface elements and a small part of the logic and independently draw a conclusion about the applicability of these technologies.

Answer 2

I recommend reading it - https://habr.com/company/epam_systems/blog/429766/
however, I myself would support Roman Mirr 's advice - try both approaches on a small breadboard application. so you will feel better and understand what suits you