Open Collective
Open Collective
Loading
Fody
Contribute
Budget
Connect
About
Fody Version 4 released
Published on February 11, 2019 by Simon Cropp

Fody Version 4 has been released.

Milestone containing all issues and PRs: https://github.com/Fody/Fody/issues?q=is%3Aclosed+milestone%3A4.0.0

This is mostly a bug fix release. There two breaking changes which justified the major version bump

  • InSolutionWeavers are no longer detected by convention but must be declared explicitly: https://github.com/Fody/Fody/issues/644
  • Legacy weavers that do not provide a .props file with a <WeaverFiles> entry are no longer supported: https://github.com/Fody/Fody/issues/643

The majority of users should not be affected by the above as they do not affect the consumers of weavers. The majority of weavers have been updated and smoke tested as part of updating https://github.com/Fody/FodyAddinSamples to Fody version 4. If you are producing a weaver that is publicly available on NuGet, and actively maintained, you should submit a PR with a sample for that weaver to FodyAddinSamples. This way your weaver will got smoke tested with every Fody release.

If you hit any issues with version 4, revert back to your previous version, and raise an issue https://github.com/Fody/Fody/issues


suttleantonuccison

on

Fody Version 4 has been released with important updates, including bug fixes and two significant breaking changes that prompted the major version bump. The changes include InSolutionWeavers no longer being detected by convention and requiring explicit declaration, as well as legacy weavers that do not provide a .props file with a <WeaverFiles> entry no longer being supported. These changes should not impact most users, as they mainly affect weaver creators. If you are producing a publicly available, actively maintained weaver, it's recommended to submit a PR to FodyAddinSamples to ensure your weaver is smoke tested with each release. For any issues with version 4, users are encouraged to revert to a previous version and report problems on GitHub. If you're familiar with  mygreenbucks net kenneth, you’ll understand how critical it is to ensure these updates are handled properly.