Skip to content

Instantly share code, notes, and snippets.

Working on Blazor: .NET for the web via WebAssembly

Daniel Roth danroth27

Working on Blazor: .NET for the web via WebAssembly
Block or report user

Report or block danroth27

Hide content and notifications from this user.

Learn more about blocking users

Contact Support about this user’s behavior.

Learn more about reporting abuse

Report abuse
View GitHub Profile

Get started building .NET web apps in the browser with Blazor

Blazor is an experimental web UI framework based on C#, Razor, and HTML that runs in the browser via WebAssembly. Blazor promises to greatly simplify the task of building fast and beautiful single-page applications that run in any browser. It does this by enabling developers to write .NET-based web apps that run client-side in web browsers using open web standards.

If you already use .NET, this completes the picture: you’ll be able to use your skills for browser-based development in addition to existing scenarios for server and cloud-based services, native mobile/desktop apps, and games. If you don’t yet use .NET, our hope is that the productivity and simplicity benefits of Blazor will be compelling enough that you will try it.

Why use .NET for browser apps?

Web development has improved in many ways over the years but building modern web applications still poses challenges. Using .NET in the browser offers many advantages that can help ma

danroth27 /
Last active Jun 12, 2017
ASP.NET Core with Application Tokens

ASP.NET Core Identity with Application Tokens

Problem statement

Migrating ASP.NET Core apps that use ASP.NET Core Identity for authentication to Azure AD B2C is difficult:

  • The app is not setup to use OIDC for authentication
  • The identity model, views, and controllers are intermingled with the application code
  • The app data is tied up with the IdentityDbContext
View repeater_view.html
int i = 1;
<repeater count="5">
<h2>Value @(i++)</h2>
View repeatertaghelper.cs
public class RepeaterTagHelper : TagHelper
public int Count { get; set; }
public override async Task ProcessAsync(TagHelperContext context, TagHelperOutput output)
output.TagName = null;
for (int i = 0; i < Count; i++)
output.Content.Append(await context.GetChildContentAsync(useCachedResult: false));
danroth27 /
Created May 8, 2014
Templates for filing ASP.NET bugs


A short description of the bug that becomes the issue title
e.g. Long polling transport tries reconnecting forever when ping succeeds but poll request fails*

Functional impact

Does the bug result in any actual functional issue, if so, what?
e.g. If poll request starts working again, it recovers. Otherwise, it sends many requests per sec to the servr.

Minimal repro steps

What is the smallest, simplest set of steps to reproduce the issue. If needed, provide a project that demonstrates the issue.

You can’t perform that action at this time.