In a web project i would use the RequestScope when binding the DbContext to my real DB context. But in WPF should i go for singleton or transcient scope ? Does it really matter which one over the other i choose ?
Depending on the complexity of your app I would start with PerThreadScope. That way you have one for the apps main thread and for each background thread. They are tracked by ninject and properly disposed. If your app gets complexer you can switch to NamedScope or InCallScope and thereby scope the db context per RootView.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With