SFletch
March 6th, 2009, 12:16 PM
I wrote, some time ago, a C++ dialog app that communicates via sockets with some specialist hardware/software, really just as a demo.
I need to re-write it to act as a comms layer between said hardware and a new VB app.
It needs to be permanantly loaded and receiving comms from the hardware (onto a queue) and pass those messages on to the VB when requested (pop off the queue).
I imagine the VB will..
Startup
Load MyApp
every n seconds MyApp.GetMessages()
UnLoad MyApp
End.
I'm really struggling as to how to even approach this. Any advice / pointers would be gratefully received.
The existing app uses MFC and STL::Queue. I'm assuming all that would be wrapped up in the dll and any app that uses it wouldn't care?
The example dll's I've looked at just seem to be function calls; pass in an int and it passes back double that int, for example. I'm sort of confused about the life of the object.
I need to re-write it to act as a comms layer between said hardware and a new VB app.
It needs to be permanantly loaded and receiving comms from the hardware (onto a queue) and pass those messages on to the VB when requested (pop off the queue).
I imagine the VB will..
Startup
Load MyApp
every n seconds MyApp.GetMessages()
UnLoad MyApp
End.
I'm really struggling as to how to even approach this. Any advice / pointers would be gratefully received.
The existing app uses MFC and STL::Queue. I'm assuming all that would be wrapped up in the dll and any app that uses it wouldn't care?
The example dll's I've looked at just seem to be function calls; pass in an int and it passes back double that int, for example. I'm sort of confused about the life of the object.