Only update Unbroken.LaunchBox.Plugins version on major releases

Issue #5947 new
fraganator created an issue

The combination of a strong name and incrementing minor versions of Unbroken.LaunchBox.Plugins.dll means plugins built against later versions of the assembly will not load in older versions of LaunchBox. For example, a plugin built against 11.9.0.0 will generate this exception when loaded with LaunchBox 11.8:

Could not load file or assembly 'Unbroken.LaunchBox.Plugins, Version=11.9.0.0, Culture=neutral, PublicKeyToken=558191e84f56affc'. The system cannot find the file specified.

The version of this assembly was originally fixed at 1.0.0.0 per Jason’s explanation on the forum:

Yeah, the version number stays the same in order to ensure effortless compatibility with previous plugins. That's the best way to do it in .NET; I just have to be careful to only add new interfaces and methods, and not change existing ones.

I can understand that it needed to be updated from 1.0.0.0, but it shouldn’t be updated on every minor revision to help maintain plugin compatibility across LB versions. Microsoft recommend only updating strong named assembly versions to a major versions.

Comments (0)

  1. Log in to comment