You can't call CoInitializeSecurity from managed code. That's because the CLR will always call CoInitialize upon startup before execution enters your main method, and CoInitialize will implicitly call CoInitializeSecurity if it hasn't already been called. Therefore, calling this from managed code returns RPC_E_TOO_LATE.
The workaround is to write an unmanaged "shim" that will call CoInitializeSecurity, then activate and call into managed code. You can do this via an export from a mixed-mode C++ DLL, by registering a managed component for use by COM, or by using the CLR hosting API.
Tips & Tricks:
Please add some!
Sample Code:
Please add some!
Alternative Managed API:
Do you know one? Please contribute it!
Registers security and sets the default security values for the process, but this can't be directly called from managed code.
3/19/2008 7:53:21 AM - RobertChipperfield-212.44.26.236
Identifies an authentication service that a server is willing to use to communicate to a client.
3/16/2007 8:20:07 AM - anonymous
Registers security and sets the default security values for the process, but this can't be directly called from managed code.
3/19/2008 7:53:21 AM - RobertChipperfield-212.44.26.236
Registers security and sets the default security values for the process, but this can't be directly called from managed code.
11/17/2010 12:47:58 AM - -71.32.39.4
Registers security and sets the default security values for the process, but this can't be directly called from managed code.
11/17/2010 12:47:58 AM - -71.32.39.4
Registers security and sets the default security values for the process, but this can't be directly called from managed code.
3/19/2008 7:53:21 AM - RobertChipperfield-212.44.26.236
Registers security and sets the default security values for the process, but this can't be directly called from managed code.
3/19/2008 7:53:21 AM - RobertChipperfield-212.44.26.236