Dear Frank,

thanks a lot for your answers. I have sent you the code via email.

Regards,

Philip

On Jun 19, 7:56 am, Frank Mantek <[EMAIL PROTECTED]> wrote:
> The first thing (the Uri assignment) is a restriction of the mobile  
> version. The Uri assignment is parsing the Uri into it's properties,  
> the code doing that uses Uri helper classes that do not exist in .NET  
> CF, hence on mobile the Uri property is read only.
>
> The Redirect exception is, again for mobile, normal for the calendar.  
> The calendar redirects all the time, but gives out a cookie for that.  
> There is no cookie parsing code on CF, hence we can not deal with the  
> cookie, so we have to live with the redirects in that case.  I  
> probably add something for the calendar/mobile specific case, but have  
> not done so yet.
>
> The Uri format exception is the one that is unexpected. Can you zip up  
> your solution and send it directly to me so that i can have a look?
>
> Thanks
>
> Frank Mantek
> Google
> On Jun 18, 2008, at 8:23 PM, Philip wrote:
>
>
>
> > Hi,
>
> > I am trying to connect to Google calendar using the .NET APIs in VS
> > 2008.
>
> > First the good news: I have copied the snippet "Retrieving all
> > calendars" 
> > fromhttp://code.google.com/apis/calendar/developers_guide_dotnet.html#Ret...
> > to test the setup; using the dlls from "Google Data API SDK\Redist" as
> > references this works fine in a normal C# Console Application on
> > Windows Vista. It prints out my calendars without any exceptions.
>
> > However, when using the dlls from "Google Data API SDK\Redist\Mobile
> > \WindowsMobile" in a Windows Mobile .NET Compact Framework 3.5
> > application (which I run on a Windows Mobile 2003 Emulator and
> > Device), I run into various problems. First of all, the snippet does
> > not compile - the line starting with "query.Uri" fails with "Property
> > or indexer 'Google.GData.Client.FeedQuery.Uri' cannot be assigned to
> > -- it is read only". However, I can use the URL directly in the
> > constructor of the line above ( CalendarQuery query = new
> > CalendarQuery("http://www.google.com/calendar/feeds/default/
> > allcalendars/full");)  and get the code working. However, now I get a
> > massive amount of exceptions which I did not get in the console
> > application (see below). I have Internet connectivity in the emulator.
> > Sometimes the code manages to get the calendars despite exceptions,
> > sometimes not.
>
> > I am sure I am missing something vital... but what?
>
> > Thanks a lot!
>
> > Philip
>
> > Exceptions:
> > A first chance exception of type 'System.UriFormatException' occurred
> > in System.dll
> > The thread 0xed68dd7e has exited with code 0 (0x0).
> > The thread 0xdec8c06 has exited with code 0 (0x0).
> > The thread 0xdec8c06 has exited with code 0 (0x0).
> > The thread 0xed68dd7e has exited with code 0 (0x0).
> > A first chance exception of type 'System.UriFormatException' occurred
> > in System.dll
> > The thread 0xad845a86 has exited with code 0 (0x0).
> > The thread 0x2dec8c06 has exited with code 0 (0x0).
> > The thread 0xad845a86 has exited with code 0 (0x0).
> > A first chance exception of type
> > 'Google.GData.Client.GDataRedirectException' occurred in
> > Google.GData.Client.dll
> > A first chance exception of type 'System.UriFormatException' occurred
> > in System.dll
> > The thread 0xed68dd7e has exited with code 0 (0x0).
> > The thread 0x2dec8c06 has exited with code 0 (0x0).
> > 'Cora.exe' (Managed): Loaded 'e:\code\vs\cora\cora\bin\release
> > \Google.GData.AccessControl.dll'
> > 'Cora.exe' (Managed): Loaded 'e:\code\vs\cora\cora\bin\release
> > \Google.GData.Extensions.dll'
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Calendar Data API" group.
To post to this group, send email to 
[email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-calendar-help-dataapi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to