You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pkcs11Interop 3.1 throws exception with hard to understand message "Unable to load library: %1 is not a valid Win32 application" when there is an attempt to load 32-bit PKCS#11 library in 64-bit runtime or 64-bit PKCS#11 library in 32-bit runtime. This problem seems to be hit quite frequently (e.g. in #25).
Code generating this message was removed in 4e45617 as a side effect of adding support for netstandard1.1 compatible platforms so this message should never appear in the exception again but I still believe such frequent error deserves its own exception type or at least exception message.
ERROR_BAD_EXE_FORMAT error code returned by Marshal.GetLastWin32Error() seems to be a natural choice for detection whether there was an attempt to load PKCS#11 library with incorrect bitness but I am not sure whether the same error code is returned on all supported platforms so I will need to investigate this further and "manually" check the code (or find other solution) on all platforms.
Pkcs11Interop 3.1 throws exception with hard to understand message "Unable to load library: %1 is not a valid Win32 application" when there is an attempt to load 32-bit PKCS#11 library in 64-bit runtime or 64-bit PKCS#11 library in 32-bit runtime. This problem seems to be hit quite frequently (e.g. in #25).
Code generating this message was removed in 4e45617 as a side effect of adding support for netstandard1.1 compatible platforms so this message should never appear in the exception again but I still believe such frequent error deserves its own exception type or at least exception message.
ERROR_BAD_EXE_FORMAT error code returned by
Marshal.GetLastWin32Error()
seems to be a natural choice for detection whether there was an attempt to load PKCS#11 library with incorrect bitness but I am not sure whether the same error code is returned on all supported platforms so I will need to investigate this further and "manually" check the code (or find other solution) on all platforms.Following table tracks my progress:
The text was updated successfully, but these errors were encountered: