Skip to main content
We currently have two dll installed one for pdf creation and one for qr creation, we did both of them back in 2012.   And of course our notes from then are spars.  

We'd like to add another dll for excel creation.   I'm assuming that in 2015 we were using Visual Studio 2012 to compile and link the C code.   We're using VS2019 to do the same for the new dll.   dumpbin for the original two dll's shows linker version 11 (which I believe is VS2012).  

When we manually install the dll into bin and add the entry to gci.admin (and confirm the addition to the registry).   we can't get the new dll to show up in GCI.NTMAP.B (the exist two dll's do, with there functions listed).

My question(s).   Is there any log file that shows any hint of why the new dll wouldn't load?    Or if VS2019 would not work on win2012r2 or universe 11.2.4?

I also, walked through the auto creation of the multiply example (ie gci.admin, step 1-2, then made the dll, added it with step 6, confirmed with step 7), but it isn't listed in the GCI.NTMAP.B either and of course declare gci says that the dll isn't found.  Again using VS2019.

Which makes me think there's something different between vs2015 and vs2019.

Any thoughts would be greatly appreciated.

Thanks
Eric D

Windows 2012 R2, Universe 11.2.4
We currently have two dll installed one for pdf creation and one for qr creation, we did both of them back in 2012.   And of course our notes from then are spars.  

We'd like to add another dll for excel creation.   I'm assuming that in 2015 we were using Visual Studio 2012 to compile and link the C code.   We're using VS2019 to do the same for the new dll.   dumpbin for the original two dll's shows linker version 11 (which I believe is VS2012).  

When we manually install the dll into bin and add the entry to gci.admin (and confirm the addition to the registry).   we can't get the new dll to show up in GCI.NTMAP.B (the exist two dll's do, with there functions listed).

My question(s).   Is there any log file that shows any hint of why the new dll wouldn't load?    Or if VS2019 would not work on win2012r2 or universe 11.2.4?

I also, walked through the auto creation of the multiply example (ie gci.admin, step 1-2, then made the dll, added it with step 6, confirmed with step 7), but it isn't listed in the GCI.NTMAP.B either and of course declare gci says that the dll isn't found.  Again using VS2019.

Which makes me think there's something different between vs2015 and vs2019.

Any thoughts would be greatly appreciated.

Thanks
Eric D

Windows 2012 R2, Universe 11.2.4
Check thn as was used to build UniVerse Visual Studio compiler options used to create the DLLs - make sure they match the UniVerse machine model in use - e.g. 64bit, try to avoid 'Any CPU'.

It is possible there is a VS version compatibility issue, though those are rare they do occur, Ideally use the same VS version as in the 'port.note' text file shipped with UniVerse. 

Regards

JJ