Dynamics Community Forum Thread Details

Using a custom version of a DLL

Hi Community,

I'm writing a custom DLL that requires DocumentFormat.OpenXml.dll v 3.1.0.0,

So I added both in my bin folder and added 2 references in AOT

First, I notice my reference OVERRIDES (rather than extend) the standard reference to DocumentFormat.OpenXml in a lower version.

Is that a good idea? What happens when MS updates their version?

Is there another way to load a newer version of a DLL already used in the system?

Is there anychance the new assembly may not work 100% where D365 expects the old version, and therefore this might break another standard feature without being aware?

It's not uncommon even in standard code for DLL overrides, there are plenty of them:

Microsoft.Dynamics.ApplicationPlatform.Environment is in both application platform and application foundation

When I call the new DLL from X++ code, I get the following errors:

Could not load file or assembly 'DocumentFormat.OpenXml, Version=3.1.0.0, Culture=neutral, PublicKeyToken=8fb06cb64d019a17' or one of its dependencies.

The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT:

Last, do I need to sign my assembly? the new openxml assembly?

Thanks

Categories:

Integrations

Development / Customization / SDK

Quick Links

Leaderboard