We normally don't try to resolve these issues unless it can be shown that DevForce is at fault. However, since the 3rd party vendor is Microsoft, I think I should try to give some explanation of what may be happening.
The Micro Framework appears to be another version of the Compact Fraamework. The Compact Framework is a subset of the complete framework, and does not support many of the features that DevForce requires such is Remoting and Serialization. Even if we could prevent the exceptions from being thrown, it would almost certainly be the case that you could not get DevForce to interoperate with the MicroFramework.
We may have a solution in mid 2008 that would support compact devices using VS2008 and WCF, but I can't commit to this at present.