Error 0x80131040 in custom build

[playduin]

Error 0x80131040 in custom build. Please explain the reason.

[Crypt32]

The error stands for The located assembly's manifest definition does not match the assembly reference. This can be because of incorrect COM object registration or missing strong name signing. Did you build sources or used compiled binaries from release section?

[playduin]

Compiled binaries from release section works fine, but I want to create custom Policy Module.

[Crypt32]

Then you need to use strong name signing and update COM registration to match your assembly.

[playduin]

What is COM registration?

[playduin]

I use PowerShell script from compiled binaries from release, auto-generated strong name signing and my certificate signing.

[Crypt32]

AD CS and its components is a COM server. Policy Module is a COM object that runs on a server and implements ICertPolicy COM interface. You have to register COM object to make it visible to other applications (in given case, visible to AD CS). Supplied installation script registers COM objects I'm releasing in this repo. If you change sources and compile your own binaries, then you need to update installation script to match your assembly and managed ICertPolicy and ICertManageModule interfaces implementations:

• interface ProgID
• interface UUID
• assembly where these interfaces are implemented
• threading flags
• exact implementation (full class name definition)
• runtime version
• runtime execution engine (for .NET it is mscoree.dll)
• location of your compiled assembly

[playduin]

After renaming all filenames and fields in the project and installation script, I see same error.

[Sleepw4lker]

If you want to build a custom module from scratch, here is a "stub" project. Here is a "production ready" one with build instructions.

[Crypt32]

Closing because of inactivity.