Hi, thank you both for your kind answers!
My first thought also was to make sure that all imports are v201109-based to be on the safe side. But then I realized that there are more references to the library then just the imports. I'm using the Java-library and there are also methods that reference the library on a call-basis, for example AdGroupCriterionServiceInterface adGroupCriterionService = user.getService(AdWordsService.V201101.ADGROUP_CRITERION_SERVICE); Since the current library also includes the older versions of the API, the compiler doest not complain, the includes only reference v201109 but still this code will to my understanding not work after Feb 29th. After realizing this I was insecure if I have overseen something else, so I wondered if there is kind of a checklist for these cases, or, if there is a way to find out about such inconsistencies by testing my code against the post-Feb29th-API. Another question that bothers me is the expression "deprecated". To my understanding this means that these calls should not be used but there is a chance that they still might work (if they don't interfere with design-changes like the new AdHoc-Reports). But if I got Google right, "deprecated" in this context means that _all_ pre-v201109-calls will unconditionally throw an error. Has anybody any further informations about that? Thanx again and kind regards, -Wolfram -- =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ Also find us on our blog and discussion group: http://adwordsapi.blogspot.com http://groups.google.com/group/adwords-api =~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~ You received this message because you are subscribed to the Google Groups "AdWords API Forum" group. To post to this group, send email to adwords-api@googlegroups.com To unsubscribe from this group, send email to adwords-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/adwords-api?hl=en
