Like Ignacio mentions, the same concepts apply. Two books do a good job of
explaining it though, Wigley and Wheelwright's Compact Framework Core
Reference and Fergus and Roof's Definitive Guide to the compact framework.
While the concepts may be the same as the full framework or desktop, keep in
mind that not all functionality is available in the .NET Compact Framework
so you should consider this when designing your architecture. Check through
the Threading namespace and verify that any methods you are relying on are
supported by the Compact version of the .NET Framework.
As specific examples, Thread.Abort and Thread.Join are not available so
account for this!
You may want to search the FAQ for "thread" and check out MSDN articles:
While the concepts may be the same as the full framework or desktop, keep in
mind that not all functionality is available in the .NET Compact Framework
so you should consider this when designing your architecture. Check through
the Threading namespace and verify that any methods you are relying on are
supported by the Compact version of the .NET Framework.
As specific examples, Thread.Abort and Thread.Join are not available so
account for this!
Even more importantly (to my mind), there's no way (that I've seen) of
exiting the process completely, there's no way of creating background
threads (which don't prevent the process from terminating) and even
Monitor doesn't have Wait or Pulse.
I recently posted some code to address the last issue, but I don't know
about the other two - you basically need to be very careful that
terminating the UI doesn't leave other threads around.
Want to reply to this thread or ask your own question?
You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.