A critical vulnerability was discovered in React Server Components (Next.js). Our systems remain protected but we advise to update packages to newest version. Learn More

Darren Stahlhut
Jul 13, 2019
  6035
(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
Scheduled job for deleting content types and all related content

In my previous blog post which was about getting an overview of your sites content https://world.optimizely.com/blogs/Per-Nergard/Dates/2026/1/sche...

Per Nergård (MVP) | Jan 30, 2026

Working With Applications in Optimizely CMS 13

💡 Note:  The following content has been written based on Optimizely CMS 13 Preview 2 and may not accurately reflect the final release version. As...

Mark Stott | Jan 30, 2026

Experimentation at Speed Using Optimizely Opal and Web Experimentation

If you are working in experimentation, you will know that speed matters. The quicker you can go from idea to implementation, the faster you can...

Minesh Shah (Netcel) | Jan 30, 2026

How to run Optimizely CMS on VS Code Dev Containers

VS Code Dev Containers is an extension that allows you to use a Docker container as a full-featured development environment. Instead of installing...

Daniel Halse | Jan 30, 2026

A day in the life of an Optimizely OMVP: Introducing Optimizely Graph Learning Centre Beta: Master GraphQL for Content Delivery

GraphQL is transforming how developers query and deliver content from Optimizely CMS. But let's be honest—there's a learning curve. Between...

Graham Carr | Jan 30, 2026

Optimizely Graph Best Practices - Security, Access Control and Performance Optimisation

Introduction Building on Part 1's content modeling and querying practices , this Part 2 focuses on the security and performance considerations...

Jon Williams | Jan 29, 2026