Closed GoogleCodeExporter closed 8 years ago
I forgot the link with the announcement of deprecation, please see here:
https://developers.google.com/google-apps/calendar/v2/developers_guide_dotnet?hl
=de-DE
Original comment by Saller....@gmail.com
on 10 Mar 2014 at 5:08
See also following link for some hints how to migrate:
https://developers.google.com/google-apps/calendar/migration?hl=de-DE
Original comment by Saller....@gmail.com
on 10 Mar 2014 at 5:12
The Calendar API v3 is built on Google's new APIs infrastructure and already
supported by the corresponding library:
https://code.google.com/p/google-api-dotnet-client/
Original comment by ccherub...@google.com
on 10 Mar 2014 at 4:05
Does this mean, that the Client library 2.2.2 already is based on Calendar Api
v3?
https://code.google.com/p/google-gdata/downloads/detail?name=Google_Data_API_Set
up_2.2.0.0.msi&can=2&q=
Because I found several things, that are in conflict with what was mentioned in
the comparison between v2 and v3 (what are the differences ): still EventEntry
(should be Event), still CalendarService (should be CalendarRequest),...
Original comment by Saller....@gmail.com
on 13 Mar 2014 at 4:42
No, to use the Calendar API v3 with .NET you need to download a different
library, available at https://code.google.com/p/google-api-dotnet-client/.
That library is the one to be used for all new APIs.
Original comment by ccherub...@google.com
on 13 Mar 2014 at 4:09
Are These .net libraries compliant with the latest Google Data API you provide
within this Homepage? Because we are not only using Calendar API, but also
Contacts and Documents api. Up to now, we were using just the downloaded dlls
from this Homepage. A Contacts API is not available in the v3 Downloads. So
what to do? mix the Calendar v3 API with the Contact/Documents v2 Api? Or will
you merge the v3 APIs into your libraries (highly appreciated)?
Original comment by Saller....@gmail.com
on 16 Oct 2014 at 5:04
We are also using the GData .NET library, and we're confused about this as
well. It looks like to get API v3 support for calendars you have to use a
whole new .NET library which is not compatible with code using the older GData
.NET library. This is a real bummer, as much source code is built around the
older library. Would have been nice to keep the interface the same...
We also use GData .NET library for contacts, and interestingly it appears the
contacts stuff does use API v3. There isn't even a contact API interface in
the new .NET library, only in the old .NET library.
This is all very confusing, a nice explanation of the versions/issues between
old/new .NET libraries would be helpful.
Original comment by mbei...@gmail.com
on 17 Oct 2014 at 10:38
I would be also interested in this, because v2 stopped to work on 17-Nov
Original comment by Saller....@gmail.com
on 19 Nov 2014 at 11:45
Muy mal, aplicaciones completas estan rotas por un cambio tan abrupto.
Lo minimo al hacer actualizaciones tan drasticas es introducir los cambios de
modo gradual y proporcionar soporte a las viejas versiones en el proceso.
Original comment by DanielPV...@gmail.com
on 20 Nov 2014 at 6:41
The deprecation of the Calendar API v2 was announced in 2011, giving 3 years
for developers to update their apps:
http://googleappsdeveloper.blogspot.com/2011/11/introducing-next-version-of-goog
le.html
Original comment by ccherub...@google.com
on 20 Nov 2014 at 8:21
Original issue reported on code.google.com by
Saller....@gmail.com
on 10 Mar 2014 at 5:07