<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Blazor on Favian Flores</title>
    <link>https://hugoblog.favianflores.com/tags/blazor/</link>
    <description>Recent content in Blazor on Favian Flores</description>
    <image>
      <title>Favian Flores</title>
      <url>https://hugoblog.favianflores.com/website-banner.webp</url>
      <link>https://hugoblog.favianflores.com/website-banner.webp</link>
    </image>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Tue, 19 Sep 2023 00:00:00 -0400</lastBuildDate>
    <atom:link href="https://hugoblog.favianflores.com/tags/blazor/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>How to use JS Interop with Blazor</title>
      <link>https://hugoblog.favianflores.com/posts/2023/how-to-use-js-interop-with-blazor/</link>
      <pubDate>Tue, 19 Sep 2023 00:00:00 -0400</pubDate>
      <guid>https://hugoblog.favianflores.com/posts/2023/how-to-use-js-interop-with-blazor/</guid>
      <description>&lt;p&gt;One of the main benefits of working with blazor is that you can use C# both server side and client side. It allows frontend and backend developers to share a single codebase (something that was only possible with javascript before). This feature is possible because of Web Assembly which gives .NET a low level language to target when compiling C#.&lt;/p&gt;
&lt;p&gt;One issue with Web Assembly is that it is still in development and doesn&amp;rsquo;t have direct access to the DOM like javascript does. So calls to the DOM need to be handled with an &lt;em&gt;IJSRuntime&lt;/em&gt; interface which allows developers to call JavaScript functions from .NET methods and vice-versa.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
