November Happy Hour will be moved to Thursday December 5th.

Darren Stahlhut
Jul 13, 2019
  4870
(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 SaaS CMS + Coveo Search Page

Short on time but need a listing feature with filters, pagination, and sorting? Create a fully functional Coveo-powered search page driven by data...

Damian Smutek | Nov 21, 2024 | Syndicated blog

Optimizely SaaS CMS DAM Picker (Interim)

Simplify your Optimizely SaaS CMS workflow with the Interim DAM Picker Chrome extension. Seamlessly integrate your DAM system, streamlining asset...

Andy Blyth | Nov 21, 2024 | Syndicated blog

Optimizely CMS Roadmap

Explore Optimizely CMS's latest roadmap, packed with developer-focused updates. From SaaS speed to Visual Builder enhancements, developer tooling...

Andy Blyth | Nov 21, 2024 | Syndicated blog

Set Default Culture in Optimizely CMS 12

Take control over culture-specific operations like date and time formatting.

Tomas Hensrud Gulla | Nov 15, 2024 | Syndicated blog

I'm running Optimizely CMS on .NET 9!

It works 🎉

Tomas Hensrud Gulla | Nov 12, 2024 | Syndicated blog

Recraft's image generation with AI-Assistant for Optimizely

Recraft V3 model is outperforming all other models in the image generation space and we are happy to share: Recraft's new model is now available fo...

Luc Gosso (MVP) | Nov 8, 2024 | Syndicated blog