Why is angular template needed in asp.net core project?

Question

ASP.NET

Good day to all.
The question is: What's the difference between creating a standalone client application in angular (which is separate from the backend) and an angular template that is created along with the asp.net core application?

From the beginning it seemed to me that it was needed for server rendering, but there is no such thing out of the box and you also need to shamanize it to make it work. As a result, it seems to me that it makes no sense to drag an asp.net core application into angular as well. It would be better if there were 2 different projects in different folders and they knew about each other, only through api and nothing more.

Knowledgeable people, please explain
Thanks in advance)

Answer 1

Honestly I do not know. I came to the conclusion that it's better to keep separate webapi and angular projects, while the angular release build is built in the wwwroot of the asp.net project. There is no profit in mixing in one project, especially when using large vs.