When updating nugets to 10.0.44 I recieve an error about Strong Name Validation on the SystemUser.Extension_DC

[Mark_Edwards]

I updated installed the latest 3.4.9.2 package from docentric and updated my devbox to 10.0.44. The models compile fine on my devbox but when checking in the models to the GIT repo I receive an error on the SystemUser.Extension_DC.

Error: AxSecurityRoleExtension/SystemUser.Extension_DC - "An unhandled exception was thrown while validating SystemUser.Extension_DC with callstack System.IO.FileLoadException: Could not load file or assembly ‘Microsoft.Dynamics.ApplicationPlatform.Flighting, Version=7.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35’ or one of its dependencies. Strong name validation failed. (Exception from HRESULT: 0x8013141A)

[BlazJ (Blaž Jensterle)]

Hello @Mark_Edwards and welcome to the Docentric community!

It sounds like the issue occurs during check-in to the GIT repo and not during local build on your devbox since it Docentric works fine on your devbox.

You can try few steps to help troubleshoot and resolve the issue:

1. Check file versions:
   Compare the file versions locally on your devbox and the one in the GIT repo. Make sure both files are referencing the same version and haven’t been somehow overwritten or mismatched.

2. Recreate the extension object:
   Try the following clean-up steps:

• Delete the object from your project.
• Commit the deletion to GIT.
• Re-add the extension object (this will regenerate the file correctly).
• Commit the new file again.

Since your models compile fine on your devbox, this means that the code itself is correct. The error might therefore be linked to some metadata or file integrity issues during check-in.

I would kindly like to suggest that you check out our installation guidelines for DevOps environments:
How to Add Docentric AX Models to TFS/Azure DevOps

[Mark_Edwards]

Hi @BlazJ thank you for the response. I did remove the base model from the repo and then reinstall it. I had the same result. In addition, I had a co-worker receive the same error on a different project.

As for the build on the pipeline, the package built properly with no errors until I updated the nugets to the latest version. Once the nugets were updated that is when I started seeing this error.

Nuget versions:

[PhabioLenzarini (Fabio Lenzarini)]

I also have the same problem.
I solved it by creating the PipeLine with the HotFix package, but it is a solution that then involves extra work during installation on the production machines.

[Mark_Edwards]

@PhabioLenzarini did you just update the compiler nuget or all of them?

[PhabioLenzarini (Fabio Lenzarini)]

Hi Mark,
I’ve created a new Pipeline, based on a new artifact with the new hotfix

ciao
Fabio

[aariste (Adrià Ariste)]

Hi @Mark_Edwards, I’d suggest updating all the NuGets to the latest version as Fabio says.

There are new packages that were published yesterday, 11 June, by Microsoft.

[Mark_Edwards]

Thanks all, I finally got it to work with the versions published on 6/12/25

[NatasaKA (Nataša Koščak Antić)]

Hi Mark,
We’re glad to hear you’ve resolved the issue. If you need anything else, we’re here to help.

[Joham_Pareja]

Hi Mark, did you get this message trying to apply the package?

[Mark_Edwards]

Hi Joham,
You need to take the latest Cumulative Updates on the environment so the environment version is higher than the nuget versions.

[Markus (Markus Gasser)]

Thanks Mark, I had the same issue today!

[Markus (Markus Gasser)]

Thanks Fabio, I had the same issue today.