InfoQ Homepage ASP.NET SPA Content on InfoQ
Articles
RSS Feed-
/articles/dotnet-spa-templates-proxy/en/smallimage/ASP-NET-SPA-templates-proxy-changes-small-1683016303172.jpg)
ASP.NET SPA Templates Proxy Changes from .NET 5 to .NET 6, .NET 7, and on
From .NET 6 the communication between front-end Single Page Applications (SPA) in ASP.NET and back-end .NET API was changed, with the SPA templates using the front end’s proxy solutions. A proxy for the development servers enables readable and debuggable code for both the front and back end, with the new approach resulting in a more independent back end.
-
/articles/Angular-Core-3/en/smallimage/Angular-Core-3-l-1571999054218.jpg)
Angular & ASP.NET Core 3.0 - Deep Dive
While there are many advantages to using Angular for building SPAs, some parts including trivial, static content such as Contact As, Licensing, etc. don’t need the extra complexity. In this article Evgueni Tsygankov shows how to build reusable Angular components that can be hosted in ASP.NET Core pages, allowing you to choose the right tool for each page.