Many thanks!

I was able to reproduce the issue with your project. For whatever reason, the FileVersionInfo.FileDescription returns a string with a single space character in it, and when we attempted to use it as the certificate common name, it did not go well.

In QuickOPC 2024.2 this will be fixed (will not require you to set the ApplicationName in the code).

Best regards

Hello,

interestingly enough, I could not reproduce the issue, in order to do the internal fix I wanted. In fact it looks like that the CN is perhaps not empty, but it might consist of some invisible special characters - but that is just a wild guess. Can you perhaps send me the project that shows the problem, or one of the improperly generated certificates, or both? If deemed confidential, you can email to support09 (at) opclabs.com.

Thank you, and best regards

Thank you. I was heading in this direction; I just wanted to collect enough information upfront.

I still consider this a problem in QuickOPC, and we will look into it and fix into the next version. The expected behavior is that although you can always configure the subject name, you should not be required to do so, and QuickOPC should automatically come up with some non-empty, and generally valid name.

Thank you for reporting this.
Best regards

Hello.

Thank you for the additional information. If your project is a Class Library, it cannot be run standalone. So, my question actually is, what type of project is the the actual top-level application that is experiencing the problem? Is it Windows Forms application, or something else?

Best regards

Hello,

thank you for the detailed report. I can *guess* that the problem is coming from the fact the the certificate common name (CN) is actually empty. The fact that this causes some subsequent issues isn't surprising that much; we need to determine why the common name came out empty, and how to rectify that, first.

Can you please answer some additional questions:

1. Which programming language are you using? C#? VB.NET?
2. Is the main ("true") project also Windows Forms app?
3. Are you setting any parameters inside QuickOPC ApplicationManifest? (opclabs.doc-that.com/files/onlinedocs/OPCLabs-OpcStudio/Late...%20Application%20Manifest.html )
4. What are the settings of the assembly-level attributes (in C#, usually in Properties/AssemblyInfo.cs ), if any - such as [AssemblyTitle] - can you post them here?
5. Are you starting your application normally (e.g. from VS IDE, or clicking on the EXE in the File Explorer), or in some special way?

Thank you