version numbers of .net and native dlls

[DanAvni]

Up until version 7.14 were the native dll was renamed and separated into a different project, the version number of both dlls (native & .net) was the same. I used this fact to make sure during build of my installation files that both dlls are of the same version (to prevent a case that happened every now and then that VS did not publish the native dll for some reason)

now on version 7.14 the versioning is different between the DLLs. could you please keep them in sync or have some other suggestion how to make sure the native dll is the same version the .net dll expects to find?

[dlemstra]

The code of the Native library has been moved to a new project because the code of that library could also be used in a WASM project. And this means that the library will have its own version numbering. And it now uses the version number of the ImageMagick library. I cannot restore the old behaviour because the Native library has no clue what the next version of the Magick.NET library will be. I don't really have any other ideas on how you could check the verson number. Your best option would probably be to figure out why your process sometimes doesn't copy the dll. I have never had this issue with the MagickViewer application that I created. Is your checking process automated? Maybe we could use the AssemblyInformationalVersionAttribute or ProductVersion for this? If you have an other ideas that would help you then feel free to suggest it here.

[DanAvni]

I remember something about the root cause of the native dll issue I have is switching between code branches using different versions of the dll but I haven't tried to study it too deeply.

What if the .NET assembly would contain an attribute specifying which native dll version is required for it to function? I could then extract that out of the .NET dll and work with that comparing it to the native dll version

The other option I was thinking about is adding a "Unit Test" that takes the native dll version and writes it to a text file which will be committed along with other source code into git. assuming all my other unit tests pass, when I would compile an installation, it will then compare the native dll version with the one stored on file known to be passing all tests. This way whenever I update the nuget package and run the tests (which I will do anyway after each nuget update) the file will be updated and it will all run "automatically" without me having to modify the installation script or anything else

[dlemstra]

Just pushed a patch that will set the TrademarkAttribute to ImageMagick x.x.x.x with the version of the Native library. Would that work for you?

[DanAvni]

I will make that work on my side. Many thanks!

[dlemstra]

I just published a new release where the library contains a TrademarkAttribute that you could use to get the version.