Lance Roberts
Posts: 5
Joined: 2010-01-27
|
Problem found with version: Professional 2009.5.2.2024
Workaround: Uninstalling .net 4 solved this. (Can you fix please so my customers won't have to do this)
Additional problem: After successfully registering the adxloader is keeping some of the dlls for my add-in locked in the filesystem - I haven't resolved this - what else can I dispose of below?
Basic Code used:
IntPtr dllHandle = IntPtr.Zero;
IntPtr procAddress = IntPtr.Zero;
try
{
dllHandle = LoadLibrary(dllPath);
string proc = "DllRegisterServer";
procAddress = GetProcAddress(dllHandle, proc);
IntPtr callResult = CallWindowProc(procAddress, IntPtr.Zero, 0, UIntPtr.Zero, IntPtr.Zero);
if (callResult == IntPtr.Zero)
{
return (true);
}
else
{
// here is where I got the 0x80131022
}
}
finally
{
if (dllHandle != IntPtr.Zero)
{
FreeLibrary(dllHandle);
dllHandle = IntPtr.Zero;
}
procAddress = IntPtr.Zero;
GC.Collect();
} |
|
Sergey Grischenko
Add-in Express team
Posts: 7233
Joined: 2004-07-05
|
Hi Lance.
What the build of .NET v4.0 did you install?
Please run regsvr32.exe tool to register the add-in from the .NET code. |
|