2 replies to this topic

[deramor]

Hello-

 

I am trying to call a C# dll from a deferred custom action.

The assembly is marked as COM visible.

 

When I try to set an object with DotNetCoCreateObject, I get the error number 2147219705.

 

Does anyone know what this error number refers to?

 

I have done similar operations in the past but in custom actions that were triggered through the UI sequence.  I'm wondering if the fact that the execute sequence is involved is giving me this issue.

In this implementation and the other that works, I can see no differences except those associated with a different dll name and class name. 

[deramor]

Turns out, the class was static which was causing the call to fail.

[deramor]

I now have a working assembly when I have a local copy of the assembly.  My situation is the following:

I have an installer that installs my Com Visible assembly into the GAC.

I have another installation that attempts to call this assembly by just saying:

 

set object = DotNetCoCreateObject(szMyDllNamewithExtention, szMyAssemblyandClassName, "");

 

After running through the debugger, I ended up noticing that the dll could not be found.

I ran it once with just the dll name in the first argument. (expecting the function to use the GAC)

I ran it again with a fully qualified path and it worked fine. 

 

My question is, is there a function that can load a .Net assembly in Installscript that will or can load the assembly from the GAC?