Scripting Error when interop dll

Started by pagesoft, November 02, 2011, 11:00:22 AM

Previous topic - Next topic

pagesoft

For got to mention I added vb6 dll to .net project and recompiled so I got the interop.HMILogger.dll name and that is what I loaded into script to verify it works.

pagesoft

Okay!  I recompiled and named the vb6 dll the same name as the intenal project name and added it to the file list after deleting the old one and it created the script just fine.
 
So! it has somthing to do with the internal vb6 project name and the DOS name being different.
 
Create as small vb6 dll with the internal project name and the dll file name being different and see if you get the same results.
 
Have a good day

Randem

The file name should be the same name as it appears on the hard disk on the computer. If the file name is interop.HMILogger.dll then the HMILoggerVB.dll should go in the unsafe file list or be removed via a template.

pagesoft

I do have the file with the address added.  I just deleted the file and then re-added it using Add Files and it still does not work.
 
I still get red line!  I have another file in the same folder and it is getting added with no problem.  I believe if I changed the Inner project name to the dos name it would work.
I will check it and let you know.

Randem

The reason you get the red line is because the HMILoggerVB.dll file was not found by InnoScript. You either have to include the path where it can be found in the Search Folders or add the file in the Add Files area.
 
Any file in red will not have a path because it was not found in the search of your computer.

pagesoft

vb.net 2008  
I have a .dll that has a dos file name of HMILogger.dll
 
Vb.net uses the interop name of interop.HMILoggerVB.dll which is the internal vb6 Project Name
 
when I compile the script I get red line  
Source:  HMILoggerVB.dll; DestDir: {sys} Flags:
restartreplace sharedfile;
 
Unless I put the HMILoggerVB.dll in the Unsafe Files I get create script error.
 
I have the interop.HMILogger.dll going {app} directory which is not the {sys} directory.
 
I have another file with the same dos name as the internal vb6 Project name and it is okay in the create script log