Blazor Code Separation - Easily Moving Code to a Code Behind File 

Another added benefit of using code behind is that at the moment razor Intellisense is pretty wonky, using code behind restores your access to the much needed Intellisense.

Oh my goodness!!. I was doing it manually. Thanks a lot Tim.

You CANNOT use contstructor injection with Blazor: It will throw this error: Cannot dynamically create an instance of type 'CodeBehindInjectionTest.Pages.FetchData'. Reason: No parameterless constructor defined. If you want to inject in the code behind you do it like this: [Inject] public WeatherForecastService ForecastService { get; set; } = default!;

Great video. This concept of quikly explaining a task/subject in 10 minutes is awesome, i like your 50+ minutes explainer video's aswell but this is a much more accessible time format to quikly learn something useful. keep them comming!

Hello Tim, another Tim here and I would like to report a mistake in this video. At 6:20 you say that we can create a constructor in code-behind file and inject the service there, but that's a mistake. We can't use Constructor DI in Blazor pages, because it produces an error: MissingMethodException: Cannot dynamically create an instance of type 'FetchData'. Reason: No parameterless constructor defined. So DI in Blazor can only be done via @inject in the view or with [Inject] attribute over a property in code-behind.

Woo just saved me about 7 hours work refactoring. Cheers Tim

Hi Tim! Thanks so match for your great tutorial 💯💥

Brilliant. Thanks a lot. You remember me with webforms.

Always great!

Thanks Tim, I didn't know this feature in blazor, I think is very usefull when you have a big razor component html code + c# code.

Thanks needed this!!

Another big advantage is code analyzers like StyleCop don't work on a .razor page, but do in the .cs files. It took [Inject] for me to able to finally separate my code completely, which is awesome.

We can create component class for each razor file and inherit from ComponentBase class and use it in razor file right. Is there any advantages in without using ComponentBase class for separating code?

Hi Tim! Thanks for the great video again. I've been using this feature for almost a year now. We can also create a css file for each razor file (e.g Counter.razor.css).

This is awesome! Is there any easy way to undo it?

very useful indeed. is there any html equivalent, I think you just make a razor component and call it like and that way you can call on bits of html/markup without them having to be in the same file. Sorry I am new to all this trying to make it neater :)

Oh! Thanks! I was creating it manually. Additionally, here we don't need to use ViewModel architecture. Don't we?

thanks, i was doing it manually took me ages

Awesome vids, Video Idea: Can you talk about the issue with Blazor client DLLs beeing block by Antivirus, and If your customers are Companies with internal security layers most likely default Blazor WASM will not work. This would be nice to know before I started to build My App with Blazor and maybe other beginners would Like to know this aswell.

How many partial classes can l create in component??

Good video.. but, injection of the weatherforecastservice from the code behind also should have been covered..

how about the css? of the component?

Been wishing for this feature. Turns out my ReSharper settings was set to hide the VS quick actions... :( Had an issue though. I tried this on a couple of my razor files and started getting errors in the code behind saying there is no suitable method to override for OnInitalized, and it doesn't see anything else from the parent classes I was inheriting from. I have also seen this when manually moving code to code behind so it's probably a VS bug (17.5.3). After checking my Git changes, I found out that VS was adding an ItemGroup with Compile statements for the code behind files to my other project in VS that I use for the web server side and not the Blazor WebAssembly project that I was actually editing in. Removing the ItemGroup seemed to fix things up. Just in case anyone else runs into this :^)

I like this idea, but what about code that needs to be on more than one page? Is there a way to have a common "code behind" page that can be shred by multiple pages?

Is it wrong to call web API in Blazor Server or is it wrong using controllers to use web API in Blazor Server?

I just love how C# has gotten so much less verbose with implicit usings and file-scoped namespaces. File-scoped namespaces should really be the default! I hope that in the coming years we will just refer to them as simply namespace declarations. Though I'm a bit disappointed that som tooling, like VS for Mac, still defaults to block-scoped namespaces for new class files.

Can add DI to code behind [Inject] NavigationManager NavigationManager { get; set; } = null!;

Honestly, I have never liked this approach of dividing the markup and the code. Having your markup and behavior code in the same file give you that sense of component (unit) which at least for me is a more natural path for the web. Also, there is a hidden advantage: you can easily see when your component is getting out of control (in terms of complexity) I guess it narrows to habits, traditionally c# dev separates this thing (even in different folders, which for me is even more painful) and then rely on tooling to navigate around

Please how to create admin panel and link my website to my admin panel. ? There’s no answer to it on internet…

Worth nothing that the "Creating constructor in the code behind file" actually doesn't work. Would be better to test before making a video about it.

Hi, just a little question. Should i use the dependencyinjection over the constructor, or using the [Inject] Attribute in the Codebehind? whats your thoughts? @iamtimcorey