Calling a native DLL from managed code

We have a native DLL called WN99.DLL, which has a number of programs named WN99???.  Our application is mostly native but we are starting to add managed functions to it.  When we start up our application, we load WN99.DLL  in our native driver program with:

SET PROC-POINTER TO ENTRY "WN99.DLL"

All of our object, both native and managed, is output to the same directory.  I was able to call a native WN99 program from a managed project without doing any further handling.  When another programmer ran the same managed code, he got an error 173 on the call to the WN99 program.  We fixed this in one of two ways, either by adding a reference in the managed project to WN99.DLL or by doing  the above SET PROC-POINTER statement in the first managed program that got run (we have a little managed program which is run when we start our application and its purpose is to do any necessary preloads of DLL'S). 

Is it true that native DLL's that are called from both native and managed have to be preloaded from both native and managed code ?  It's odd that I didn't have to preload WN99.DLL from managed code whereas the other programmer did.  I only had to preload it in the native driver program.

We have a native DLL called WN99.DLL, which has a number of programs named WN99???.  Our application is mostly native but we are starting to add managed functions to it.  When we start up our application, we load WN99.DLL  in our native driver program with:

SET PROC-POINTER TO ENTRY "WN99.DLL"

All of our object, both native and managed, is output to the same directory.  I was able to call a native WN99 program from a managed project without doing any further handling.  When another programmer ran the same managed code, he got an error 173 on the call to the WN99 program.  We fixed this in one of two ways, either by adding a reference in the managed project to WN99.DLL or by doing  the above SET PROC-POINTER statement in the first managed program that got run (we have a little managed program which is run when we start our application and its purpose is to do any necessary preloads of DLL'S). 

Is it true that native DLL's that are called from both native and managed have to be preloaded from both native and managed code ?  It's odd that I didn't have to preload WN99.DLL from managed code whereas the other programmer did.  I only had to preload it in the native driver program.

We have a native DLL called WN99.DLL, which has a number of programs named WN99???.  Our application is mostly native but we are starting to add managed functions to it.  When we start up our application, we load WN99.DLL  in our native driver program with:

SET PROC-POINTER TO ENTRY "WN99.DLL"

All of our object, both native and managed, is output to the same directory.  I was able to call a native WN99 program from a managed project without doing any further handling.  When another programmer ran the same managed code, he got an error 173 on the call to the WN99 program.  We fixed this in one of two ways, either by adding a reference in the managed project to WN99.DLL or by doing  the above SET PROC-POINTER statement in the first managed program that got run (we have a little managed program which is run when we start our application and its purpose is to do any necessary preloads of DLL'S). 

Is it true that native DLL's that are called from both native and managed have to be preloaded from both native and managed code ?  It's odd that I didn't have to preload WN99.DLL from managed code whereas the other programmer did.  I only had to preload it in the native driver program.

We have a native DLL called WN99.DLL, which has a number of programs named WN99???.  Our application is mostly native but we are starting to add managed functions to it.  When we start up our application, we load WN99.DLL  in our native driver program with:

SET PROC-POINTER TO ENTRY "WN99.DLL"

All of our object, both native and managed, is output to the same directory.  I was able to call a native WN99 program from a managed project without doing any further handling.  When another programmer ran the same managed code, he got an error 173 on the call to the WN99 program.  We fixed this in one of two ways, either by adding a reference in the managed project to WN99.DLL or by doing  the above SET PROC-POINTER statement in the first managed program that got run (we have a little managed program which is run when we start our application and its purpose is to do any necessary preloads of DLL'S). 

Is it true that native DLL's that are called from both native and managed have to be preloaded from both native and managed code ?  It's odd that I didn't have to preload WN99.DLL from managed code whereas the other programmer did.  I only had to preload it in the native driver program.

We have a native DLL called WN99.DLL, which has a number of programs named WN99???.  Our application is mostly native but we are starting to add managed functions to it.  When we start up our application, we load WN99.DLL  in our native driver program with:

SET PROC-POINTER TO ENTRY "WN99.DLL"

All of our object, both native and managed, is output to the same directory.  I was able to call a native WN99 program from a managed project without doing any further handling.  When another programmer ran the same managed code, he got an error 173 on the call to the WN99 program.  We fixed this in one of two ways, either by adding a reference in the managed project to WN99.DLL or by doing  the above SET PROC-POINTER statement in the first managed program that got run (we have a little managed program which is run when we start our application and its purpose is to do any necessary preloads of DLL'S). 

Is it true that native DLL's that are called from both native and managed have to be preloaded from both native and managed code ?  It's odd that I didn't have to preload WN99.DLL from managed code whereas the other programmer did.  I only had to preload it in the native driver program.