Not surprisingly some geeks were able to extract the .NET Compact Framework 3.7 version which was contained in one of the latest Windows Mobile 6.5 ROMs. The .NET Compact Framework 3.7 is now available on some sites for download as CAB file. Unfortunately the extracted run-time environment is without a change log which let’s us developers in the dark what really was improved.
Not long ago I posted the first part of this article under: Part I: Mimic SynchronizationContext behaviour on .NET CF The article was intended to give the reader a better feeling of the purpose of the SynchronizationContext and the importance of the class on behalf of synchronization between different apartment threads. Unfortunately the SynchronizationContext is not available on the .NET compact framework which is especially annoying when you want to port existing code which uses the...
Before I got into the details of the problem I want to briefly describe what the SynchronizationContext class really does and what it’s main purpose really is in the first part of the article. From that perspective I’m going to show how the basic functionality of the SynchronizationContext class can be implemented for the .NET compact framework in the second part of the article..
As you might already know I’m a certified windows mobile application developer. My speciality is hybrid application development for applications which target both the full .NET framework platform and also the mobile platform. Of course nobody wants to write the same code for each platform again so you have to come up with some tricks and solutions to overcome some limitations on the compact framework.