![]() ![]() ![]() The interaction between the XAML compiler, our analysis engine, and various shared generic delegate instantiations will need to be. In this case, we end up stripping the controls of their necessary members and ReactiveUI cannot find them at runtime to do the binding. When everything is working nicely, this means your app is smaller, your builds are a faster, and you'll be none the wiser. Unfortunately, if we end up relatively unsure that a property/event/etc of a control isn't going to be used we'll end up stripping it off. So at the end of the day we're not able to properly track which properties on the base XAML controls are going to be necessary for binding at runtime. If it's ever useful, the number is 406415. I've opened a bug in our internal database about this issue. Update to 5.3.2 (this will pull down v1.6 of.Select the package for (aka the UWP metapackage).Install VS 2017 RTM and pick the UWP workflow at install.Here’s some instructions on how to get to latest of everything: One thing that may help get you unblocked is to see if this issue still reproduces on the latest set of. The repro file takes a bit longer for me to dig through but may be less work on your end. ![]() If someone can share a GitHub link to a project that demonstrates the issue that's ideal but an ilcRepro.zipfile will also work. As I'm (more or less) completely ignorant of ReactiveUI I'll probably need a bit more detailed info to produce a local repro (if it's really just those lines above an a few nuget references please just tell me I'm being dense). This definitely seems like something we'd like to investigate. There is a result on the PasswordBox when accessed directly on the UI without Reactive Only PasswordBox seems to have this problem. stacktraces, related issues, suggestions how to fix) Build is 圆4 Debug or Release, compiled with. Windows 10 (UAP), SDK build 10.14393, ReactiveUI-Core version was initially 6.5.0 but an upgrade to 7.2.0 did not change the situation. Which versions of ReactiveUI, and which platform / OS are affected by this issue? Did this work in previous versions of ReativeUI? Please also test with the latest stable and snapshot ( ) versions. NET Native Toolchain to upload to the store What is the motivation / use case for changing the behavior?Īpp must be compiled with. This works in any use-case when not compiled with. NET native Toolchain: Viewmodel receives empty string NET Native Toolchain: Works with input passwordĬompile with. If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problemĭ(this.Bind(ViewModel, x => x.Password, x => x.password.Password)) ĭ(this.WhenAnyValue(x => x.password.Password).BindTo(this, x => x.ViewModel.Password)) Ĭompile without. NET Native, binding PasswordBox.Password will only pass an empty string. Do you want to request a feature or report a bug? ![]()
0 Comments
Leave a Reply. |