I received a question recently about my post on Checking for a Valid Strong Name Signature. The person who was using the code I presented there to run some tests under NUnit. The format of the tests was to use the Microsoft.Win32.Registry classes to set the skip verification list up, and then call StrongNameSignatureVerificationEx. However, he found that this wasn’t working.
The reason behind this is that the CLR is free to cache any settings that it looks up in the registry and environment. This could occur at any point from the time that the CLR is first spun up, to the point that you request the value of the setting. In order to ensure that the settings you are creating are honored by the CLR, you need to kick off a new process. So the NUnit tests should use the following algorithm:
- Set the appropriate registry keys with Microsoft.Win32.Registry
- Kick off another process that runs the actual test with System.Diagnostics.Process
- Wait for that process to exit, and have it tell you if the test passed or failed. One way would be to read the ExitCode property of the process, another would be through a named pipe, or a shared file.