C-Hook - Technical question

[rm_titus]

Hello,

 

I have a technical question for you guys that I hope you can answer for me.

I'm working to implement a mechanism that mix native and managed code, something like

C-Hook (C++) <-> Wrapper (C++) <-> Managed Library (C#).

The reason I'm doing that is because, basically the main part of the job is completed within a C# library.

First of all, I'm creating an interface to the C++ wrapper (IManagedCodeWrapper)

Then I create the class factory ManagedCodeWrapper : IManagedCodeWrapper that creates a static instance of the class itself and call

the desired method from the managed library.

 

All this stuff works well in my testing so far, however I can't make it turn out within Mastercam.

 

I don't know why Mastercam doesn't like the code snippet who creates the wrapper

code:

---

IManagedCodeWrapper *wrapper = IManagedCodeWrapper::CreateInstance()

---

Would someone be kind to have a look this please ...

Thanks a lot !

 

--Titus

[Roger Martin from CNC Software]

rm_titus,

 

"doesn't like" ~~~> what happens?

 

Details, more details will be needed to even be able to attempt a guess.

[rm_titus]

Hello,

 

When I'm trying to load the C-Hook, I'm getting the error message "Could not load file or assembly <...> or one of its dependencies. The module was expected to contain an assembly manifest."

 

After clicking on "Ok" again, another messagebox "The appropriate Mastercam .NET Support dll could not be found" is popping up

 

Commenting out that line of code afterwards everything goes well again...

 

Thanks a lot for your assistance!

 

--Titus

[Roger Martin from CNC Software]

Are these 'other' DLLs properly referenced (in the References branch) in your Solution?

[rm_titus]

I'm not able to reproduce the hang in my test environment because everything works wonderful.

 

All references are there. Now I'm using just a simple c# DLL that is popping up a "Hello" messagebox.

 

The wrapper is there as well. I don't see anything wrong with this...

 

Thanks !

[rm_titus]

Hello guys,

 

Everything works like a charm now.

 

When you encounter an assembly loading problem,

consider using the Assembly Binding Log Viewer

tool that comes with the .NET Framework

(fuslogvw.exe) to determine which dependency

failed to load and why.

 

Here what I did:

- compile without /clr option (not sure if this could be a potential issue...)

- link with /fixed:no additional switch.

- put all other DLLs in my McamX2 directory (Thanks Roger to pointing this out !!! The DLLs was properly referenced but wasn't placed in the proper directory).

 

Thanks Roger again for answering !

 

--Titus