C# WPF UI Tutorials: 38 - Replacing NInject with .Net Core DI

Part of a series of tutorials on creating WPF applications in C#

It's time to move on to better things. In this video we ditch NInject for the newer, lighter, better (opinionated) DI system built into .Net Core, thought the use of Dna Framework which makes the process super easy.

We have some fun with some unexpected debugging near the end of the video too, for extra fun.

[Galal]

Luke, the decreasing amount of views/likes with every video clearly shows how advanced and legendary this series is. Your videos truly show honest geniune content covering advanced topics which do not interest all the Hobbyists and fakers out there. You are not like all those commercial channels where they post the same boring videos every year like "Should you learn Java in 2019" or "Why I switched from x to y" and with half-baked tutorials with ZERO attention to architecture and design patterns, eventually raking in millions of views. So please never be discouraged by the amount of subscribes/likes/views, and know well that there are people out there that know exactly what you are doing and appreciate it! Also the fact that you take us with you throughout your thought process, is simply priceless. Hats off to you sir and keep them coming!

[Schwooo]

Always awesome content!

I love the raw videos. Even though you have a clear goal in mind (and most likely it's clear to you how you're going to get there), for some reason unrehearsed videos make it feel so much more like we're working through our best options to accomplish the goal. I feel that most structured tutorials just show you the one way to get there and maybe touch on why you wouldn't do it another way. Keep it up! Hopefully one day I can store as much knowledge as you...

[tomas]

I'm really surprised at the level of quality you've reached. You do an excellent job. I have a suggestion. Maybe you can make videos when you edit the Dna.Framework project, to show us how do you develop it.

*EDIT* Can you tell me in what videos you make the TaskManager and FileManager? I think I forgot to see them lol

[TheMohsell]

Even though still not watched the vdu, but thank you for the awesome stuff ...

[fictionos]

Finally my brother but still I'm waiting for the explanation on how to manage those .NET CORE DI without Dna framework....

Nice haircut man, you look like a scientist, lol :D

[Kattarina_S]

hello Luke, can you help me?
As I was following this tutorial I got stuck with an error at a point where your project could already run, i just figured out that since i could not find a fix, it would just be easier to check if you know about a fix for it. My code builds just fine but im getting an exception at -> AddClientDataStore -> UseSqlite -> ArgumentNullException for the connectionString`` everytime i run it. I have tried to check and build your code to maybe find the reason behind this, but when i try to build your code it always fails giving "Error: Missing Metadata" for each project.

[kellecierion]

Thank you for the amazing tutorials, when will you publish the next video :)

[TheDanderle]

So I finally finished my WPF app and now am faced with a new problem. The app is running on an embedded device and is only accessible with USB. How can I perform Software updates? I was thinking of having an option, in the app, to check if a USB-Stick is connected and then check if the Version on it is newer than the one running. Then it would restart and load the new version into the bootloader and restart the app. Have you done something like this before and can point me into the right direction? Thank you by the way for all your other helpful tips and advice.

[urlgreen]

can you do a video about making a splash screen that would be really hepful, since i couldnt find any good videos about that and thank you a lot for all the effort you putting in those videos

[one-uioj]

i have a question! wpf better than qt(c++) or not ?

[frankhaugen]

Drop the DNA stuff, remove the comments, (unless you are making a framework/library), and don't spread your code out like this!

Three projects per solution:
Logic (core)
Communication (wpf, api, console)
Tests

This is so messy and all over the place, it's almost as bad as mediator pattern

[persoulrpg]

Gah.. Two things:

1. I'm not a fan of the 'using static' thing to be honest. It's very misleading and intelisense does not seem to like that either. It was kind of better with IoC... things were separated nicely. Right now it's a little bit mixed together and not really sure what is where. Can we work something out here?
2. At the time you created the Fasetto.World.Core project you said that it's important to separate the logic from the UI and move the view models there, now you are doing the opposite - which is very misleading as well. In my opinion the view models should never be located inside our UI project, just to not fall in the trap and not use a component from the WPF .NET Framework inside them, we don't want that and having a .NET Standard project is a good way to stay away from that!


Regarding last 20~ minutes: it was good to see you in action, can learn much from that :-)