nerdculture.de is one of the many independent Mastodon servers you can use to participate in the fediverse.
Be excellent to each other, live humanism, no nazis, no hate speech. Not only for nerds, but the domain is somewhat cool. ;) No bots in general. Languages: DE, EN, FR, NL, ES, IT

Administered by:

Server stats:

1.2K
active users

#ASPNET

2 posts2 participants0 posts today
Isaac Levin<p>Discover the advantages of Blazor WebAssembly and Ahead-of-Time (AOT) compilation. <a href="https://fosstodon.org/tags/Blazor" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>Blazor</span></a> <a href="https://fosstodon.org/tags/dotnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>dotnet</span></a> <a href="https://fosstodon.org/tags/aspnet" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>aspnet</span></a> </p><p> <a href="https://isaacl.dev/ghf" rel="nofollow noopener noreferrer" translate="no" target="_blank"><span class="invisible">https://</span><span class="">isaacl.dev/ghf</span><span class="invisible"></span></a></p>

How can we use NUnit to test ASP.NET Core?

In this article, I explain how to leverage NUnit in ASP NET Core tests with simple code examples.

xUnit has been my preferred testing framework, but I felt like it was important to dive back into NUnit as well. While I still need to dedicate more time to it, I wanted to document some of the process so that you can see how to leverage NUnit in your ASP NET Core tests!

Check out the article:
devleader.ca/2024/02/16/nunit-

I don't want to generate a full (hierarchical) graph of all pages in my #AspNet #SSG, but it looks like I have no choice.
Also, I have to load all Markdown files upfront, before I can even think about building the graph as a whole.
Upside, all Markdown files are loaded once, and then accessed from memory.

Adding to my #SSG ramblings. This is roughly the layout I'm thinking of.
Whether /content/Home will be there, I don't know yet, that is how Grav does it.
Keeping the wwwroot and Views/-structure, as that is configured by-default in ASP.NET.

The Views are all runtime-compiled and then rendered based on files inside the content-folder.