Hi,
I guess you can do as Frans did with the ORMSupportClasses:
the same source files make up both the .Net 2.0 and CF.Net 2.0 dlls.
2 different makefiles compile to the target plateform while referencing the corresponding dlls.
I guess you could also make it with two class libs projects referencing the same files.
Then you also have explicit instructions in the source code to switch when the core cf system libs can't provide the same syntax.
ex from entitybase2:
#if CF
_objectID = GeneralCFUtilities.CreateNewGuid();
#else
_objectID = Guid.NewGuid();
#endif
Now, you may also use OpenNetCf.Net which should compensate for most of what the core CF lacks.
Cheers