Google API and .NET Compact Framework

I am developing a Windows Mobile 6.5 (.NET Compact Framework 3.5) application that will sync device PIM data with Google Calendar and Google Tasks services. I obviously want to use the Google API for .NET ( ), but apparently it is only designed for the standard desktop version of the .NET Framework ...

Attempting to compile a CF3.5 project referencing the official API.dll failed with messages like "Type" System.Uri "is defined in an assembly that is not referenced. You must add a reference to assembly" System, Version =, Culture = neutral, PublicKeyToken = b77a5c561934e089 "." This will of course be .NET Framework 2.0.dll, which cannot be referenced in the CF project.

When I downloaded the API sources and tried to build them myself under CF3.5, it failed again due to references to a few functions that are only included in the standard .NET framework.

So my question is, what are my options here? Is there a version of Google APIs developed for the Compact Framework that I have so far largely overlooked? And if it doesn't, should I try changing the API to remove the conflicting features, hoping they won't be needed for my application's functionality? Should I instead bundle the finished API together and use it for educational purposes only to create my own? Or do you have any ideas?

Any input is greatly appreciated.




source to share

1 answer

Let me just answer this for future reference by others.

  • Currently, there seems to be no Google API client libraries in the CF version. He searched for it thoroughly for some time without any results.
  • Trying to modify the client libraries yourself and place them in the Compact Framework's capabilities is impossible (at least not within a reasonable time frame). There were just too many (often interrelated) features that would need to be removed or significantly changed (or rewritten).
  • So the correct answer is the third option - create your own libraries to access the API using the well-documented REST access link (in case of using the Calendar API reference / ). It turned out to be much more complicated and demanding than I expected.


All Articles