Hi all
I have a wrapper to a driver and it is being used by multiple applications.
Can somebody advise me what would be a standard design for a C# wrapper a .cs file or a shared dll.
Thanks in advance
Standard Design for a C# Wrapper to Native functions
Hot Topic
- How to Assign the Context Menu to WebBrowser Control
- Device Emulator 1.0 can not fire user notifications!
- Initializing COM in Cpp VS 2005
- Mobile 5.0
- POOM import/export vCard
- Can't debug CF v1.0 on WM 5.0 device or emulator.
- deploy "non-exe" files
- Rotating app in vb.net
- Getting the Location of phone
- is Thumb same as Arm?
Smart Device
- SslStream Pocket Pc
- How to convert a WM5.0 Project to PPC 2003 project
- How to test mobile application with internet browser
- Environment SpecialFolder invalid operation
- how to automatically insert text at caret position
- VS2005, .NET CF 1.0, .NET CF 2.0 and WindowsCE 5.0 questions
- List the all the file name on Pocket PC
- How can I create a Smartphone Home plug-in project for both WinCE 2003 and Win Mobile 5.0 ?
- coredll.lib
- "the new connection uses a data provider that is not supported"
Standard Design for a C# Wrapper to Native functions
lars corneliussen
Both ways have advantages and disadvantages. If you’re planning to share library, you can ship if with, say, new version of a driver so your applications can be updated without any changes. You might save some space as well. However, you would need to strong name sign that library and GAC it. Also it would expose your driver as its all public.
Sharing source file makes it harder to update, but it less maintenance as you don’t need to handle DLL.
So the answer is: whatever’s convenient for you.