SDK & Satellite Assemblies

0

Hello Nikolaus,

This warning means that we found an assembly with exactly the same full assembly name but with different content (based on the hash of the file) in a different package.

.net works by simply loading one assembly with a specific full assembly name, when trying to load another it assumes the package is already loaded and will skip it.

However, there's a good chance that the packages will still work fine despite this warning, but you have to remember that always the first plugin you run will determine which file has been loaded. And if both of these files are compiled with different code, it can cause errors or malfunction, such as missing some method or different logic.

Updating references with NuGet shouldn't cause this problem, most packages are versioned there.

Hi Kamil!

Thanks for the answer.

So that would mean we have the same assembly with the same version in different packages with different MD5?? That's interesting ;-)

Since version is also contained in Assemblies full name, we can assume that plugins will work with different versions of the same assembly, since the loader would load 2 assemblies here right?

Example:

Package1 : System.Text.Json, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51
Package2 : System.Text.Json, Version=6.0.0.4, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51

Best regards, Nik

Hi Nik,

there's also the option, that you are adding a assembly which is already used by BPS Portal.

For example there's the System.TextJson. 6.0.6..... file in the BPS portal

That's the reason why I'm trying to use the same versions as they are deployed by BPS portal and I don't copy those assemblies to the generated .zip file.
I'm using this script to get get the file names, so that I can exclude them:
# update array by executing this on the server to ignore all existing files.
# $files = Get-childitem -Path "C:\Program Files (x86)\WEBCON\WEBCON BPS Portal\*.dll"
# $files | % {"'$($_.Name)',"} | clip

The only problem one can encounter if one is using a third party SDK which uses the same assemblies but in a different version.
Up until now, I didn't ran into any issues.

If you would have been on the WEBCON Day you could have gone to the Expert Zone with this and other questions. ;)

Best regards,
Daniel

Hi Daniel!

Thanks a lot for the info. It is good to know that there are other ways. Unfortunately I don't have access to all systems, because some of them are running in SaaS-mode. So I have no control over the installed versions of these assemblies, that's why I am providing them by myself, this seems to be safer for me.

> If you would have been on the WEBCON Day you could have gone to the Expert Zone with this and other questions. ;)

Yes, sorry this time that was no option, but I am sure we will see us next time ;-)

Best regards, Nik