Take the community feedback survey now.

Darren Stahlhut
Jul 13, 2019
  5826
(2 votes)

Introduction - Blazor + Episerver blog series

Following my presentation and demo of Blazor + Episerver Content Delivery API in Sydney at the Episerver Developer Meetup - July 2019. I've decided to start a series of blog posts to share the content with the global community. 

For those that attended the Sydney meetup, thank you, I had a great time building the proof of concept and I'm keen to expand on it over the coming weeks.

Here is the Blazor slide deck from the meetup: http://bit.ly/2LmbP3N 

This first post in the series is mostly just to announce the series, share the slide deck, and get some general interest going.

In the next post, I'll share some code (via github) including Client-side and Server-side Blazor running against Episerver Content Delivery API

I'm particularly interested in expanding the solution to add Episerver Routing (to the Server-side app) and demonstrate how Javascript interop works, to keep the front-end JS developers happy 😁.

Anyone eager to get a headstart can have a look at these references (included in the slide deck);

Blog Series Updates: 

2019-07-27 - Code available on GitHub - https://world.episerver.com/blogs/darren-s/dates/2019/7/code---blazor--episerver-blog-series/

Jul 13, 2019

Comments

Darren Stahlhut
Darren Stahlhut Jul 14, 2019 02:49 AM

Sorry if anyone caught an authentication error trying to access the link to the Slide Deck, that was my bad 😞, it's been fixed now. The new link is http://bit.ly/2LmbP3N 

Jul 15, 2019 07:45 AM

I don't think any front end JS developer is going to be happy when running Blazor 😂. If they can't use the JS framework flavour of the month and learn a new framework every 3 months they are bloody miserable 😂😂😂. 

Darren Stahlhut
Darren Stahlhut Jul 16, 2019 10:59 AM

@scott haha! I don't know what's more fun. Watching C# devs realise they can write front-end compiled code, or watching JS devs realise that C# devs can write front-end code 😂. 

More seriously, I think Blazor running as a SPA on the client-side will get limited usage in C# community. But I think once we have a hosted CMS able to run on .Net Core, server-side Blazor will become very popular, and can still serve whatever JS framework your front-end developers want to use this month.

Please login to comment.
Latest blogs
Optimizely CMS Mixed Auth - Okta + ASP.NET Identity

Configuring mixed authentication and authorization in Optimizely CMS using Okta and ASP.NET Identity.

Damian Smutek | Oct 27, 2025 |

Optimizely: Multi-Step Form Creation Through Submission

I have been exploring Optimizely Forms recently and created a multi-step Customer Support Request Form with File Upload Functionality.  Let’s get...

Madhu | Oct 25, 2025 |

How to Add Multiple Authentication Providers to an Optimizely CMS 12 Site (Entra ID, Google, Facebook, and Local Identity)

Modern websites often need to let users sign in with their corporate account (Entra ID), their social identity (Google, Facebook), or a simple...

Francisco Quintanilla | Oct 22, 2025 |

Connecting the Dots Between Research and Specification to Implementation using NotebookLM

Overview As part of my day to day role as a solution architect I overlap with many clients, partners, solutions and technologies. I am often...

Scott Reed | Oct 22, 2025