Costura not updating fodyweavers.xml correctly

[GeertvanHorrik]

I was installing it to an existing project which already had a few weavers. Then VS suddently asked me: do you want to overwrite FodyWeavers.xml?

It seemed that it created a brand new fodyweavers.xml instead of adding the weaver to the existing list of weavers.

[SimonCropp]

do you have the latest nuget beta installed?

[distantcam]

I had the same thing happen with PropertyChanged. Because I was using a custom event name upgrading to a new version of PropertyChanged nuked that setting in fodyweavers.xml.

I suspect this might be an issue when switching from the plugin version of fody to the nuget version.

[SimonCropp]

that could make sense.
With the pre nuget fody "fodyweavers.xml" was injected with powershell.
So moving from the VSIX fody to the nuget fody could cause a loss of the fodyweavers.xml contents

The question is "is this worth fixing"?

[distantcam]

Hmmm. I don't know.

How many support hassles is it causing you?

Does this only happen when going from pre-nuget to nuget fody? Are we sure it doesn't happen when going from version to version of nuget fody?

[SimonCropp]

unless anyone objects I am going to close this as "not worth fixing"

[GeertvanHorrik]

Agree.