1. The simplest method is to deploy the entire Smart Device Framework using the CAB files provided. When you deploy a project including a reference to an OpenNETCF dll this will occur automatically. The device gets the whole framework installed into the Global Assembly Cache (GAC) and an entry in the remove programs applet in control panel.

2. An alternative is to deploy only those dlls which you use in your project within your own custom CAB file. Be aware that there are dependencies between the libraries so if you use OpenNETCF.Windows.Forms, then you need OpenNETCF.Drawing.dll and OpenNETCF.dll also. I think some kind of dependency diagram would be useful to illustrate all the dlls in the SDF, I’ll follow up with this in a later thread.

3. The third method (which is the most flexible and more complex) is to cherry-pick the classes you use from our source code and either build your own dll, or place it directly in your exe. If you are a VB.NET developer you’ll need to use a dll project since most of our code is in C#. As with method 2 you need to take care to include any dependencies of the class(es) you use, if they are not present in your project (or referenced) then you’ll get build errors. We don’t have a definitive reference of dependencies for each class, however I’m sure it’s something we can eventually phase into our documentation. In many cases related classes are contained in the sale code file – e.g. Registry and RegistryKey.

About the Author Peter Freeman Foot

Microsoft Windows Development MVP