Adding Blazor to an Existing MVC Application: Carl Franklin's Blazor Train ep 22

[@jawidhassim8856]

Your comment about it bringing us back to a productivity paradigm closer to Webforms is spot-on AF. I've even had this thought.

[@bendunaway8296]

Great video. I LOVE Blazor. I complain when my employer won't let me use it for new projects. I hope others embrace it as well.

[@DeveloperExpress]

We hope so too Ben! Thanks for watching!

[@JerrodVolzka]

What if I just want to use components and no routing? Pretty clean then, right?

[@mohamedhajjaj2014]

That's awesome , will be some tips for webassembly with authentication inside MVC project?

[@riaanswart5155]

Any reference that can be used for connecting to mvc controller that has auth? Got the component working and using http client to call mvc controller to get some data for component as user interact but authentication is missing when calling from component

[@hqcart1]

will regular .net core pages download any of the blazor js/WebSockets or related files?

[@JacobSnover]

Hi Carl, love the vids! I am currently in a weird spot with a Blazor WASM application. I was using Okta as an auth provider using oidc PKCE, and calling Okta directly from the WASM app. Needless to say we are being asked to change this to have or auth service in the back-end with cookie auth instead. My question is if I can leave the WASM app as standalone, and use a web api project, or an MVC project that can handle all the auth, the redirect's and token retrieval, and then only pass the required info back to the WASM app? I'm asking because I tried to move most of the code to the web api, and tried to redirect the WASM app to the login for the PKCE retrieval, but this resulted in a CORS error due to understandable securrity reasons. Someone suggested hosting the WASM app in another app, but this project is 8 months in, and I am not sure how easy it would be to move it. This is why I stumbled on this video, which unfortunately is hosting a server side app. So again just wonderin if I can call an MVC app from the WASM app, let it handle all the auth, and then once the token is retreived return back to the WASM app, set my auth state and be on my way? Any help is appreciated, thank you for your time.

[@orchardskills5799]

Hey Brian. If you use a component you can just integrate the counter directly into the MCV Web Application. For me, it was much easier. So, in Index.cshtml just call Please see the example: github.com/OrchardSkills/OrchardSkills.BlazorComponentsMVCWebApp Thank You.

[@DeveloperExpress]

Thanks for the Shortcut!

[@GetkinetiqPlus]

Thanks for this. You make a good point that it is possible to embed Blazor components directly into any MVC page, bypassing a lot of the standard Blazor infrastructure. There are scenarios where this may be appropriate. For instance, I found that in order for my Blazor-based pages to look like the rest of my site, I had to make a Blazor version of the menu which is fairly involved in my case (role-based menu items, a search box with autocomplete, etc). I've been thinking it might make sense to actually replace the MVC version of the menu with the new Blazor component so that I only have to maintain one version of it. That should work because it is self-contained. But that's where I will likely stop. In general, I prefer not to mix Blazor and MVC. In particular, I feel that adding Blazor components to existing MVC pages can result in extra complexity unless you are very careful. I suspect the pattern will coalesce around either re-working the whole controller in Blazor or sticking with MVC. My intention here is to show people how to use a fairly vanilla Blazor setup side-by-side with MVC in the same project, in a way that can scale and is compatible with most of the help available online.