如何使用Invoke调用应用程序的importCase方法并传入参数？

It looks like you’re already set up with the IDispatch pointer to your SGNSAutomation.SGNSApplication instance—great start! Here’s how to extend that code to call the importCase method with a local file path parameter:

Step 1: Retrieve the DISPID for the importCase method #

First, you need to get the dispatch ID (DISPID) of the method you want to call. This tells COM which method to invoke on the object.

// Define the method name we want to call
LPOLESTR methodName = OLESTR("importCase");
DISPID dispidImportCase = 0;

// Get the DISPID for "importCase"
HRESULT hr = pWMPDispatch->GetIDsOfNames(
    IID_NULL,
    &methodName,
    1,
    LOCALE_USER_DEFAULT,
    &dispidImportCase
);

if (FAILED(hr)) {
    // Handle error (e.g., method doesn't exist)
    MessageBox(NULL, L"Failed to get DISPID for importCase", L"Error", MB_OK);
    // Cleanup existing resources before exiting
    pWMPDispatch->Release();
    CoUninitialize();
    return hr;
}

Step 2: Prepare the input parameter #

The importCase method expects a string (local file path), so we need to wrap this in a VARIANT as a BSTR (COM’s Unicode string type). Use SysAllocString to safely create the BSTR.

// Replace with your actual local case file path
LPCWSTR caseFilePath = L"C:\\Your\\Case\\Directory\\CaseFile.ext";

// Initialize a VARIANT to hold the parameter
VARIANT param;
VariantInit(&param);
param.vt = VT_BSTR;
param.bstrVal = SysAllocString(caseFilePath);

// Check if BSTR allocation succeeded
if (!param.bstrVal) {
    MessageBox(NULL, L"Failed to allocate memory for file path", L"Error", MB_OK);
    VariantClear(&param);
    pWMPDispatch->Release();
    CoUninitialize();
    return E_OUTOFMEMORY;
}

Step 3: Set up DISPPARAMS for Invoke #

When using IDispatch::Invoke, input parameters are passed in reverse order in the DISPPARAMS structure. Since importCase takes one parameter, this is straightforward:

DISPPARAMS dispparams = {0};
dispparams.cArgs = 1; // Number of input arguments
dispparams.rgvarg = &param; // The array of arguments
dispparams.cNamedArgs = 0; // No named arguments needed here
dispparams.rgdispidNamedArgs = NULL;

Step 4: Call IDispatch::Invoke #

Now invoke the importCase method, capturing any return value or exceptions thrown by the COM object:

VARIANT result;
VariantInit(&result);
EXCEPINFO excepInfo = {0};
UINT uArgErr = 0; // Index of a faulty argument (if any)

hr = pWMPDispatch->Invoke(
    dispidImportCase,
    IID_NULL,
    LOCALE_USER_DEFAULT,
    DISPATCH_METHOD, // We're calling a method, not a property
    &dispparams,
    &result,
    &excepInfo,
    &uArgErr
);

// Handle success or failure
if (FAILED(hr)) {
    if (excepInfo.bstrDescription) {
        // Show the detailed error from the COM object
        MessageBox(NULL, excepInfo.bstrDescription, L"Invoke Error", MB_OK);
        SysFreeString(excepInfo.bstrDescription);
    } else {
        MessageBox(NULL, L"Failed to execute importCase", L"Error", MB_OK);
    }
} else {
    MessageBox(NULL, L"Case imported successfully!", L"Success", MB_OK);
}

Step 5: Clean up all resources #

Always release COM resources to avoid memory leaks:

// Clear the parameter and result variants
VariantClear(&param);
VariantClear(&result);

// Release the IDispatch pointer
if (pWMPDispatch) {
    pWMPDispatch->Release();
    pWMPDispatch = NULL;
}

// Uninitialize COM (if you initialized it earlier with CoInitialize/CoInitializeEx)
CoUninitialize();

Key Reminders: #

• Parameter Order: For methods with multiple arguments, input parameters must be reversed in the rgvarg array. This is a common gotcha with IDispatch::Invoke.
• BSTR Management: Never use regular C++ string functions with BSTRs—stick to SysAllocString and SysFreeString (or VariantClear) to manage their memory.
• Error Details: The EXCEPINFO structure will often contain specific error messages from the COM object, which is far more useful than just checking the HRESULT.

内容的提问来源于stack exchange，提问作者mahdi Lotfi