Shared Library o DLL?
-
For an item of hardware I have written a Shared library to make it easy to use the API for this hardware. The library sets up data structures and handles, buffers etc for simple program use. For example to arrange data to be transmitted I call routines like:-
UINT16 TransmitData( UINT unit, UINT addr, TXBUFFER * tx_buffer );
However in VS2008 I used C++ in a MFC dialog application, which all worked well. Having moved to VS2010, I now see that the intellisence does not work with this product for C++. So my thoughts were to use C# for the Windows forms and link in the Shared Library. My question is do I need to general a DLL rather than a Shared Library so that I can use C++, C# and perhaps VB. Is this correct and what are the procedures to follow. The libray is built using C. I include the API.lib and API.h along with the DLL that came with the API s/w environment. Many thanks, Andy
-
For an item of hardware I have written a Shared library to make it easy to use the API for this hardware. The library sets up data structures and handles, buffers etc for simple program use. For example to arrange data to be transmitted I call routines like:-
UINT16 TransmitData( UINT unit, UINT addr, TXBUFFER * tx_buffer );
However in VS2008 I used C++ in a MFC dialog application, which all worked well. Having moved to VS2010, I now see that the intellisence does not work with this product for C++. So my thoughts were to use C# for the Windows forms and link in the Shared Library. My question is do I need to general a DLL rather than a Shared Library so that I can use C++, C# and perhaps VB. Is this correct and what are the procedures to follow. The libray is built using C. I include the API.lib and API.h along with the DLL that came with the API s/w environment. Many thanks, Andy
Intellisense should still work, look at this to see if it helps clear up the problem: http://www.codeproject.com/Tips/180150/Including-stdafx-h-in-a-non-default-location.aspx[^]