Closed jcmm33 closed 9 years ago
It sounds like the weaver isn't kicking in. Can you change your build verbosity (Tools | Options | Projects and Solutions | Build and Run | MSBuild project build output verbosity) to "diagnostic", rebuild your project, and then attach the entire log file here? Alternatively, if you zip up your sample project, I'd be happy to take a look at it on my side. There could be a variety of potential reasons in terms of project setup that could cause this plugin to not activate. Thanks!
Log file is here : http://1drv.ms/1FAdQ27
As I said I did have to change the name of the assembly and remove the .net45 otherwise the 'weaving' wouldn't execute and generated an error.
Hmm, it's definitely activating the reactiveui.fody plugin. I'll try to create your console app from scratch and see if I can repro. Admitedly I had been donig most of my testing in Xamarin.Ios. If I can't repro, I'll hit you up for that zip file, but let me get back to you first.
The application project is here http://1drv.ms/1bYU30S
On this subject, I'm looking to use in a PCL which targets both Xamarin & WP8.1/WinRT . Currently the package won't install within a PCL targeting the above.
Hey, thanks again for reporting this. The bug was due to the embarassing fact that I was neglecting to account for nested types. The latest version in nuget should fix this bug for you. I'm going to go ahead and close out this issue and create a new one (https://github.com/kswoll/ReactiveUI.Fody/issues/2) for the PCL problem. (I'll investigate that one next)
I'm done a small test console application which compiles correctly (after changing the assembly name for the net45 build for the fodyhelper) but I don't appear to be seeing property values changing.
Simple app :
Which produces the output : value1 =0 value2 =0 value2 =2 value2 =3
which is clearly not right.