<story><title>Using WebAssembly from .NET with Wasmtime</title><url>https://hacks.mozilla.org/2019/12/using-webassembly-from-dotnet-with-wasmtime/</url></story><parent_chain><item><author>kirse</author><text>I really like the approach of Blazor wrt WASM, but really dislike having to dump whole code blocks into CSHTML files like I&amp;#x27;m writing old ASP.NET Forms again.  Something just feels off.&lt;p&gt;Is there any way to isolate those code blocks and import them?&lt;p&gt;EDIT: To answer my own question, this appears to be the solution:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.telerik.com&amp;#x2F;blogs&amp;#x2F;using-a-code-behind-approach-to-blazor-components&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.telerik.com&amp;#x2F;blogs&amp;#x2F;using-a-code-behind-approach-t...&lt;/a&gt;</text></item><item><author>jcmontx</author><text>I know MSFT technologies get a lot of hate here, but ASP.NET Core is pretty awesome. Blazor (the wasm based framework) is innovative and a positive step forward frontend web development.&lt;p&gt;You should leave your prejudices aside and give it a try if you haven&amp;#x27;t yet.</text></item></parent_chain><comment><author>manigandham</author><text>The latest release (.Net 3.1) finished the partial classes implementation so now you can create a `Comp.razor` template file and a separate `Comp.razor.cs` code-behind file that only contains the code. These are automatically compiled together on build.</text></comment>
<story><title>Using WebAssembly from .NET with Wasmtime</title><url>https://hacks.mozilla.org/2019/12/using-webassembly-from-dotnet-with-wasmtime/</url></story><parent_chain><item><author>kirse</author><text>I really like the approach of Blazor wrt WASM, but really dislike having to dump whole code blocks into CSHTML files like I&amp;#x27;m writing old ASP.NET Forms again.  Something just feels off.&lt;p&gt;Is there any way to isolate those code blocks and import them?&lt;p&gt;EDIT: To answer my own question, this appears to be the solution:&lt;p&gt;&lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.telerik.com&amp;#x2F;blogs&amp;#x2F;using-a-code-behind-approach-to-blazor-components&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.telerik.com&amp;#x2F;blogs&amp;#x2F;using-a-code-behind-approach-t...&lt;/a&gt;</text></item><item><author>jcmontx</author><text>I know MSFT technologies get a lot of hate here, but ASP.NET Core is pretty awesome. Blazor (the wasm based framework) is innovative and a positive step forward frontend web development.&lt;p&gt;You should leave your prejudices aside and give it a try if you haven&amp;#x27;t yet.</text></item></parent_chain><comment><author>SigmundA</author><text>Blazor supports components: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;docs.microsoft.com&amp;#x2F;en-us&amp;#x2F;aspnet&amp;#x2F;core&amp;#x2F;blazor&amp;#x2F;components?view=aspnetcore-3.1&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;docs.microsoft.com&amp;#x2F;en-us&amp;#x2F;aspnet&amp;#x2F;core&amp;#x2F;blazor&amp;#x2F;componen...&lt;/a&gt;</text></comment>