I find that there are two approaches to sharing library classes between .NET and .NET CF code bases.
Code is identical
Often libraries can be identical, especially if they are base libraries that have calculations, or business classes that are identical. For libraries other than the UI, this often happens, since .NET CF is basically a subset of .NET.
In this case, you can simply create a device project and enable it for your project with a full window. You will receive a warning that you are loading a device project, but if you have not used any CF code, this is normal.
The code is very similar but different
In this case, I create two projects and, therefore, two assemblies. I make one of these assemblies the main one and include all the files that are used. In the second, I add files as links to include them as links, so any updates are reflected. Then I use ifdefs for any special cases where they may differ.
skeeve
source share