Community Forums
Page 1 of 2 12 LastLast
Results 1 to 5 of 6

Thread: DotNetCoCreateObject Error in IS 2012

  1. #1
    Join Date
    Jun 2012
    Posts
    1

    DotNetCoCreateObject Error in IS 2012

    My installer cannot call DotNetCoCreateObject.
    It gives error number -2147219705.
    I've read through as many articles and posts on this error as I can and done all of the fixes but it's still not working. I must be missing something.
    The assembly is ComVisible.
    The DLL is in the SUPPORTDIR at IS runtime.
    The assembly uses the 4.0 framework but I've upgraded to IS 2012 so that shouldn't be an issue, either.

    Here's the code:
    set helper = DotNetCoCreateObject(SUPPORTDIR ^ "RunSQLScripts.dll","RunSQLScripts.ScriptHelper","");

    What am I missing?

    Thanks in advance for any help.

  2. #2
    Join Date
    Jul 2012
    Posts
    1

    DotNetCoCreateObject Installshield 2012 - .NET 4.0

    I have exactly the same problem. We built the installer originally in Installshield 2009 with .NET framework 2.0 and have been using it for 3-4 years.

    We have now updated our software to utilize .NET framework 4.0 and upgraded to Installshield 2012. The same DotNetCoCreateObject method that has worked should work now from what I have read, but we now get the error number -2147219705. If anyone figures out how to make this work, please let me know. Thanks in advance for any help.

  3. #3
    Join Date
    Oct 2010
    Posts
    64
    I am also running into the issue where DotNetCoCreateObject is failing. Has anyone else found a solution to this problem.

    Thanks,
    Robert M.

  4. #4
    Join Date
    Apr 2008
    Location
    Albuquerque NM USA
    Posts
    42
    I'm also running into the same error.
    --Greg

  5. #5
    Join Date
    Jan 2002
    Location
    San Diego, CA
    Posts
    164

    Same problem here

    There is conflicting information on various posts about whether UseDLL is required before DotNetCoCreateObject. Either way, it does not work for me. I have ComVisible set to TRUE, the DLL exists in the path.

    Can someone from Flexera jump in here?
    www.SoftwareReleaseGroup.com

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •