[mono bindings] Do not bump AssemblyVersion on every release

try installing banshee-extension-soundmenu and also enable it in banshee
preferences. I cant try as banshee crashes here on start

On Sun, Sep 12, 2010 at 2:23 PM, Daniel Planas Armangue <
<email address hidden>> wrote:

> Public bug reported:
>
> banshee not work on new maverick sound menu
>
> ** Affects: indicator-sound
> Importance: Undecided
> Status: New
>
> --
> banshee not work with sound menu
> https://bugs.launchpad.net/bugs/636253
> You received this bug notification because you are subscribed to The
> Sound Menu.
>
> Status in Sound Menu: New
>
> Bug description:
> banshee not work on new maverick sound menu
>
>
>

I can confirm this, with the extension installed and enabled in Banshee.

** (Banshee:12732): WARNING **: The following assembly referenced from /usr/lib/banshee-1/Extensions/Banshee.SoundMenu.dll could not be loaded:
     Assembly: indicate-sharp (assemblyref_index=9)
     Version: 0.4.1.0
     Public Key: 2e8e49ba7d172cb0
The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/usr/lib/banshee-1/Extensions/).
** (Banshee:12732): WARNING **: Could not load file or assembly 'indicate-sharp, Version=0.4.1.0, Culture=neutral, PublicKeyToken=2e8e49ba7d172cb0' or one of its dependencies.

indicate-sharp (libindicate0.1-cil) 0.4.2 is installed, so it's possible this just needs a rebuild.

This is caused because the AssemblyVersion in AssemblyInfo.cs is bumped on every release.

The AssemblyVersion is used to declare ABI compatibility; if the major or minor releases are changed from those a reverse dependency was built against then mono will refuse to load the dll and will most likely crash the application with an execption like the one we are seeing here.

You should only bump the version when the ABI of your library really changes; there's entirely no need to force depending applications to rebuild for every upstream release you guys do. Generating it automatically from @VERSION@ like happens now is surely wrong.

Don't hesitate to ask the #debian-cli guys if you have any questions with mono library packaging. We're more than happy to help you get these things right in advance of upload/release. Come see us if you need assistance: #debian-cli @ OFTC.

Cheers,
Iain