Customization in LDAP solution

[shaimaafarouk9]

Hi Yvand, I installed the wsp the first time without any modification and i need to customized the wsp so when downloading the developer file ,the .snk is highlighted with yellow sign that the file not found and when we create a new .snk file in the solution the public key token of the LDAP feature became different from the original deployed feature public key token of source code and this cause issues after deploying the customized solution with update powershell command so what is the best practice for deploying the customization with update command in this case?

[Yvand]

@shaimaafarouk9 it is expected that you sign the .DLL with your own signing key. This will sign your custom assembly with your custom signing key, but ldapcp.dll is still signed with the LDAPCP signing key.

If you deploy both LDAPCP.wsp and your CustomLDAPCP.wsp, you need to realize that both eventually deploy the same DLL LDAPCP.dll, so be mindful that if you retract/update 1 solution, it may impact the other

But tbh I don't really understand how you ended up with a different feature

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

Stale issue message