When using RDVBA and code signing within Access VBA the signature will be discarded if RDVBA Loads

[hecon5]

Rubberduck version information
The info below can be copy-paste-completed from the first lines of Rubberduck's log or the About box:

Rubberduck version (tested with several, and with 2.5.92.6381 mostly)
Operating System: Win11
Host Product: MSAccess

Description
When loading RDVBA in the VBAIDE (not even running to parse, simply loading RDVBA), the HelpFileName variable will be reset from time to time by RDVBA. This resets the VBA Code Signature and causes mayhem, much weeping and knashing of teeth because the dev doesn't realize what's happening.

Disabling RDVBA from loading during VBAIDE startup appears to fix this issue.

Realizing I know the variable is used to track RDVBA instance, fixing this may be a bit of a doozie, but it's quite frustrating.

To Reproduce
Steps to reproduce the behavior:

1. Open VBA IDE.
2. Sign Code with Code Signing Cert.
3. (Optional) restart Access. Your code should run as if signed.
4. Open VBA IDE.
5. If it is not loaded, Load the RDVBA Addin.
6. RDVBA will load.
7. Save the VBA IDE. This appears to be optional; but will make it more likely to happen.
8. Restart Access.
9. When restarting the program, you will likely become frustrated that you have done nothing, changed nothing, and your code won't run because the code signature is not valid / has been tampered with.
10. You will, after much consternation, discover that actually, RDVBA set an instance pointer w/ the HelpFileName.
11. Disabling RDVBA from autostart upon loading of the VBAIDE will cause this behavior to stop, because the HelpFileName variable is no longer shifting.

Expected behavior
Loading the VBA IDE and RDVBA does not cause you to chase something else. AKA: doesn't cause signature tampering.

Screenshots
n/a (for now).

Logfile
Rubberduck generates extensive logging in TRACE-Level. If no log was created at %APPDATA%\Rubberduck\Logs, check your settings. Include this log for bug reports about the behavior of Rubberduck.

Additional context
Add any other context about the problem here.

[retailcoder]

The project ID will only be overwritten if it's empty in the first place. There's no way that'll be removed, it's way too embedded at this point, but it was designed to not interfere with anything that might already be using that field for whatever reason.

[hecon5]

That's what I thought (and had been my experience until recently). However, I'm finding that if I have the code project signed with a code cert, the value will be overwritten if RD VBA wrote it in the first place.

What I haven't determined is if I put some value (random long value) if this continues to be the case.

[retailcoder]

Yes, if there's already a value, RD runs with it and hopes it's unique across opened projects. Otherwise it comes up with a random value and uses that.

[INOPIAE]

@hecon5 : Are you sure that this works:

• Sign Code with Code Signing Cert.
• (Optional) restart Access. Your code should run as if signed.

To my knowlegde the Code Signing for Access is not availbale.

[hecon5]

It does, has for almost a year now :)

https://www.isladogs.co.uk/vba-project-signing/