Has anyone managed to use Application.RegisterXLL on an ExcelDna add-in from within a VSTO add-in?
I've signed and code-signed everything that could possibly be signed (incl. manifests)...next step is getting a Papal Bulla for the DLLs! :-)
And yet, the first time the unmanaged ExcelDna C++ crosses into the managed ExcelDna.Loader with
hr = pXlAddInType->InvokeMember_3(CComBSTR("Initialize"),...
I get the dreaded
That assembly does not allow partially trusted callers. (HRESULT 0x8013150A)
The singing certificate shows up in Excel's Distrust Center (as trusted).
I granted FullTrust to the publisher certificate with the following
caspol.exe -q -machine -addgroup 1 -pub -cert "my.cer" FullTrust
But if I check, then I get the following
c:\>CasPol.exe -rsg ExcelDna.xll
WARNING: The assembly at VTB.QR.xll cannot be loaded. Caspol can make a partial determination of what evidence would be
associated with this assembly. The results of the following operation are not necessarily accurate or complete.
...the rest of the output says FullTrust...
Incidentally, after adding the following (signed) manifest to ExcelDna, the XLL does not load into Excel stand-alone anymore (so without VSTO). I guess this is the first problem I should solve, right?
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<assembly xmlns="urn:schemas-microsoft-com:asm.v1" manifestVersion="1.0">
<assemblyIdentity name="ExcelDna.xll" processorArchitecture="x86" type="win32" version="126.96.36.199"></assemblyIdentity>
<requestedExecutionLevel level="asInvoker" uiAccess="false"></requestedExecutionLevel>
I appeal to the VSTO/manifest/religious experts out there, as I'm running out of options, hope and faith altogether...desperate, really :-)
Thanks very much in advance!