[BUG] Splat.DryIoc UseDryIocDependencyResolver throws NullReferenceException in ViewStackServiceBase ctor

[xplatsolutions]

[BUG] Splat.DryIoc UseDryIocDependencyResolver throws NullReferenceException in ViewStackServiceBase ctor

[open-collective-bot]

Hey @xplatsolutions 👋,

Thank you for opening an issue. We will get back to you as soon as we can. Also, check out our Open Collective and consider contributing financially.

https://opencollective.com/reactiveui

PS.: We offer priority support for all financial contributors. Don't forget to add priority label once you start contributing 😄

ReactiveUI - Open Collective

An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms!

[RLittlesII]

I had a chance to look at this over the weekend. Seems this is not a bug with Splat.DryIoc or Sextant. Unless it has been inadvertently fixed through changes since the time this bug was reported.

The following information on DryIoc Documentation on Register and Resolve

Though powerful, registering delegate may lead to the problems:
Memory leaks by capturing variables into delegate closure and keeping them for a container lifetime.
Delegate is the black box for Container - which makes hard to find type mismatches or diagnose other potential problems.
Therefore, try to use it only as last resort. DryIoc has plenty of tools to cover for custom delegate in more effective way. The ultimate alternative would be Factory Methods.

A working example of Sextant using Splat.DryIoc can be found https://github.com/RLittlesII/Reactive.Sandbox/tree/master/xamarin/forms/Sextant139

GitHub

RLittlesII/Reactive.Sandbox

This is a sandbox where I can build amazing sand castles with Reactive Extensions and ReactiveUI - RLittlesII/Reactive.Sandbox