Describe the bug
WireUpControls for android throws exception.
Line 38 gets the wrong assembly. Causes line 39 First() to throw an exception. No matching element.
In VS 2017 it gets the right assembly.
I have tested this on two machines.
Steps To Reproduce
Expected behavior
No exception thrown
Environment
Hey @danielvistisen :wave:,
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 backing us.
https://opencollective.com/reactiveui
PS.: We offer
prioritysupport for all backers. Don't forget to addprioritylabel when you start backing us :smile:
An advanced, composable, functional reactive model-view-viewmodel framework for all .NET platforms!
Seems Visual Studio "fixed" this and it broke the way we were loading assemblies.
In case others run into this and want to use VS2019 before this gets fixed:
For a temp workaround I copied the class to my android project. Replaced line 38 with:
var assm = Assembly.GetExecutingAssembly();
Also renamed WireUpControls to WireUpControlsLocal and changed code to call this method instead to avoid ambiguous methods.
Fixed by #2050
Most helpful comment
In case others run into this and want to use VS2019 before this gets fixed:
For a temp workaround I copied the class to my android project. Replaced line 38 with:
var assm = Assembly.GetExecutingAssembly();
Also renamed WireUpControls to WireUpControlsLocal and changed code to call this method instead to avoid ambiguous methods.