Do you mean memory-mapped file?
In any case you need to write client code in C. Different drivers require different client code - using CreateFile or Setup SDK functions, ReadFile, WriteFile, DeviceIoControl etc. - this must be written in driver documentation. If you are working together with driver developer, he must know this.
C/C++ client talks with driver and reads values using functions like DeviceIoControl. Having these values C/C++ can make them available for VB clients. Placing variables to shared memory is possible, but this is not straightforward and requires adding PInvoke code to VB .NET client.
I think the best way is writing managed C++ wrapper which talks with driver and provides pure .NET interface for VB .NET clients.
Main Topics
Browse All Topics





by: PockyMasterPosted on 2006-04-01 at 01:59:52ID: 16348981
I think the easiest solution would be:
let your c driver do the I/O stuff.
Create a c/c++ DLL to read the stuff from your memory and handle the management for your memory and link this to your VB.NET project.
According to my humble opinion, you cannot, or very hard, do it from VB.NET without the help of unmanaged code.