Type a page name and press Enter. You'll jump to the page if it exists, or you can create it if it doesn't.
To create a page in a module other than ole32, prefix the name with the module name and a period.
[System.Runtime.InteropServices.DllImport("ole32.dll")]
public static extern int CoInitializeSecurity( IntPtr pVoid, int
cAuthSvc,IntPtr asAuthSvc, IntPtr pReserved1, RpcAuthnLevel level,
RpcImpLevel impers,IntPtr pAuthList, EoAuthnCap dwCapabilities, IntPtr
pReserved3 );
VB .NET Signature:
Declare Function CoInitializeSecurity Lib "ole32.dll" (pVoid As IntPtr, _
cAuthSvc As Integer, asAuthSvc() As SOLE_AUTHENTICATION_SERVICE, _
pReserved1 As IntPtr, dwAuthnLevel As Integer, dwImpLevel As Integer, _
pAuthList As IntPtr, dwCapabilities As Integer, pReserved3 As IntPtr) As Integer
You shouldn't call CoInitializeSecurity from managed code. That's because the CLR will almost 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 will usually return 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.
Besides the fact that CoInitializeEx has replaced CoInitialize, you shouldn't need to call this in managed code via PInvoke because the CLR already initializes COM when appropriate.
RPC_E_TOO_LATE (Update from Yahor Sinkevich):
Usually RPC_E_TOO_LATE happens when CoInitializeSecurity already called (implicitly or explicitly, it does no matter). When you using Visual Studio, it use so called "Visual Studio Hosting Process" where CoInitializeSecurity already called. Turn off Visual Studio hosting process and have fun, now you can debug your application that calls CoInitializeSecurity with no RPC_E_TOO_LATE error.
Tips & Tricks:
Please add some!
Sample Code:
/// <summary>
/// The main entry point for the application.
/// Do not set STAThread since CoInitializeSecurity is called
/// with to high security automatically (and it can only be called once).
/// </summary>
//[STAThread]
static void Main()
{
// Set threading apartment
System.Threading.Thread.CurrentThread.ApartmentState = ApartmentState.STA;
CoInitializeSecurity( IntPtr.Zero, -1, IntPtr.Zero,
IntPtr.Zero,RpcAuthnLevel.None ,
RpcImpLevel.Impersonate,IntPtr.Zero, EoAuthnCap.None, IntPtr.Zero );
Please add some!
Application.MainForm = new MainForm();
System.Windows.Forms.Application.Run(Application.MainForm);
}
Alternative Managed API:
Do you know one? Please contribute it!
An IntPtr is a pointer to a memory location (unmanaged) that adapts to the platform it is running on (64-bit, etc.) UNLIKE a standard int/Integer. You should always use this type for unmanaged calls that require it, even though an int will appear to work on your development machine.
1/13/2008 4:00:13 AM - Damon Carr-72.43.165.29
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
CoInitializeEx initializes the COM library for use by the calling thread, sets the thread's concurrency model, and creates a new apartment for the thread if one is required. Values for the dwCoInit parameter are taken from the COINIT enumeration. However, since pinvoke is a dotNET construct you should be aware that dotNET already does a COM initialization and therefore calling a CoInitializeEx function most likely will not do what you expect. This problem occurs when trying to instantiate a COM object from within dotNET where the COM objects threading model is different from dotNETs. Search on Common Language Runtime or CLR and COINIT_APARTMENTTHREADED to find posts on this issue.
7/25/2015 5:25:25 PM - -5.202.143.191
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
The mechanism provided by the CLR that enables managed code to call static DLL exports.k
10/27/2022 9:24:28 PM - 114.37.143.20
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
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
Please edit this page!
Do you have...
helpful tips or sample code to share for using this API in managed code?
corrections to the existing content?
variations of the signature you want to share?
additional languages you want to include?
Select "Edit This Page" on the right hand toolbar and edit it! Or add new pages containing supporting types needed for this API (structures, delegates, and more).
Revisions