We experienced that within a solution a ProjectA referencing properties from ProjectB (weaved by virtuosity) might emit call instead callvirt instructions when using the coalesce operator. Is this a known issue?
Just ran into this because EF lazy loading was not triggering for something like
Installed the packages Fody/ReactiveUI/ReactiveUI.Fody and added the FodyWeavers.xml to the root of project with the content : <?xml version="1.0" encoding="utf-8" ?>
</Weavers> Am i missing something else?
When I run my Fody weaver on net472, I get the following in build output:
Fody/RuntimeNullables: Reference to attribute library not found - references remain unchanged.
I tested it with NullGuard and a similar issue happens:
Fody/NullGuard: No reference to 'NullGuard.dll' found. References not modified.
And the bin output folders contain the attribute assemblies. This does not happen on netstandard or netcore projects.
public override bool ShouldCleanReference => true;in your
ReferenceCopyLocalPathsproperty of your weaver)
Can anyone help explain why my nuget package for my new fody plugin isn't being created? I'm following the instructions at https://github.com/Fody/Home/blob/master/pages/addin-development.md and it sounds like i just need to run the following
dotnet build .\MyTest.Fody.sln --configuration Release
And it should be created in a "nugets" folder at the root of the solution but that is not what i see