How to connect front-end to Angular and back-end core?

Many heard that uses angular for the front and core for buck. On what basis is data uploaded? I suspect that the c front throw requests the web api? This is the only way?
Thank you!
PS. I know that the Studio has a ready-made template, but it doesn't fit.
April 3rd 20 at 17:17
3 answers
April 3rd 20 at 17:19
MS specifically created the water, trying to your framework to adapt to SPA.
Think differently.
If you need a web application, a web application consists of two parts (at least) front and back.
The front is a mountain of scripts that the user receives from the static web server. Backing logic, which is able to communicate with the database and responds according to the Protocol available for the front.
Since it's such a big enterprise thing, and the framework for the front MS chose large, enterprisey Angular and tried integrirovatsya with him as I could. (It is strange that MS has not found another fatal flaw and didn't cut its own web frame)
Thank them of course, but in fact they are two different relatively nezavisnih apps still dock Angular you're talking about you will not find anything.

And returning to the subject matter, Yes, the front makes http requests to back. Asynchronous requests in both directions is also possible via a websocket.
They have there own SPA framework - Blazor. - isador commented on April 3rd 20 at 17:22
@earnest.Bergnaum, put CLR in WebAssembly to make it work in a browser until it looks like a game and experiment with the mutants. And the last time I watched it, it was really sluggish.
And I suspect in this field, if it does take off, there will be other, more elegant solutions. - Trevor.Kiehn commented on April 3rd 20 at 17:25
@earnest.Bergnaum, but there is still Bazel - Assembly of angular forces C# - Trevor.Kiehn commented on April 3rd 20 at 17:28
Thank you, Google. - isador commented on April 3rd 20 at 17:31
@earnest.Bergnaum, well, the essence does not change, just the collector of the other. - Trevor.Kiehn commented on April 3rd 20 at 17:34
Well, the project template with Angular is not integration, this is the same pattern there is to React, even as much as two. He's just a curve, it is easier to have two projects, one net Web api, the second SPA. Now just so 2 different project, added workspace vscode, one using dotnet cli to be born, another ng using the cli. Without any fictional integrations. - Lolita.V commented on April 3rd 20 at 17:37
April 3rd 20 at 17:21
And about the Studio, as they have not. Much more convenient to keep a separate project for the client in the Visual Studio Code.

And the design of the api to run
dotnet watch run
April 3rd 20 at 17:23
1. Create application ASP.NET.CORE as the Web.API. No ANGULAR there is no need. This is a separate project in Visual Studio. He can communicate with the MySQL database and work under Linux. I'm using VPS server with UBUNTU
2. In Visual Studio Code to create a separate project using Angular CLI.
3. Two separate independent projects.

On the client I use ng-swagger-gen. It automatically generates all of the services access from the client to the backend.

In the Beck (in the project ASP.NET.CORE) to connect the library Swashbuckle.AspNetCore
using Swashbuckle.AspNetCore.Swagger;
using Swashbuckle.AspNetCore.SwaggerGen;
Website Swagger
Documentation ASP.NET.Core - Swagger

This approach gives the possibility:
You make changes on the server in the controller. On the client, start the generator and all the services the machine has been updated.

Access to the backend can be done from anywhere (not only from the Angular project). It is possible for example, Windows applications written in any language or any framework...

Find more questions by tags .NETAngular