<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - ASP.NET SPA</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ ASP.NET SPA feed</description>
    <item>
      <title>Article: ASP.NET SPA Templates Proxy Changes from .NET 5 to .NET 6, .NET 7, and on</title>
      <link>https://www.infoq.com/articles/dotnet-spa-templates-proxy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=ASP.NET+SPA</link>
      <description>&lt;img src="https://res.infoq.com/articles/dotnet-spa-templates-proxy/en/headerimage/ASP-NET-SPA-templates-proxy-changes-header-1683016303172.jpg"/&gt;&lt;p&gt;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.&lt;/p&gt; &lt;i&gt;By Tamás-Márk Furó&lt;/i&gt;</description>
      <category>ASP.NET SPA</category>
      <category>.NET 7</category>
      <category>.NET</category>
      <category>.NET 6</category>
      <category>.NET 5</category>
      <category>Architecture &amp; Design</category>
      <category>Development</category>
      <category>article</category>
      <pubDate>Thu, 04 May 2023 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/dotnet-spa-templates-proxy/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=ASP.NET+SPA</guid>
      <dc:creator>Tamás-Márk Furó</dc:creator>
      <dc:date>2023-05-04T09:00:00Z</dc:date>
      <dc:identifier>/articles/dotnet-spa-templates-proxy/en</dc:identifier>
    </item>
  </channel>
</rss>
