I have a VBA code which accesses a function inside a VC++ DLL. That function itself calls another function inside another DLL which is a C# DLL (I modified the IL code to export the function and then built the DLL so that unmanaged code can use it.)
I have two notebooks. My application (one executable and two DLLs) runs there perfectly as I intend. But when I try to run the app after copying the code to another user's machine, it doesn't work. On investigations, it seems that eveything is OK with the VC++ DLL. (It writes logs with various steps and variable values). Further it is even able to load the C# DLL using LoadLibrary. But it is not able to get the C# function address by GetProcAddress. Please help me what could be the problem. Has this problem anything to do with administrative rights or lock level or anything? (It is working perfectly on my two notebooks where I am the administrator.)
Thanking in advance,
Viral
I have two notebooks. My application (one executable and two DLLs) runs there perfectly as I intend. But when I try to run the app after copying the code to another user's machine, it doesn't work. On investigations, it seems that eveything is OK with the VC++ DLL. (It writes logs with various steps and variable values). Further it is even able to load the C# DLL using LoadLibrary. But it is not able to get the C# function address by GetProcAddress. Please help me what could be the problem. Has this problem anything to do with administrative rights or lock level or anything? (It is working perfectly on my two notebooks where I am the administrator.)
Thanking in advance,
Viral