Why do we have versions in API .NET Client library.
21 views
Skip to first unread message
Mounica Chitte
unread,
Jul 8, 2016, 1:19:42 PM7/8/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to AdWords API Forum
What is the reason behind maintaining different versions of Client library? Every time a release is being made to Library, is it mandate that we need to make code changes in our Application?
Thanet Knack Praneenararat (AdWords API Team)
unread,
Jul 11, 2016, 1:43:58 AM7/11/16
Reply to author
Sign in to reply to author
Forward
Sign in to forward
Delete
You do not have permission to delete messages in this group
Copy link
Report message
Show original message
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to adwor...@googlegroups.com
Hi Mounica,
Generally speaking, for all Google ads client libraries, we make a new release when
a new AdWords API version, e.g., v201605, has been released.
an old AdWords API version will be sunset.
a new feature is released during the above version boundary.
a bug is fixed.
You can check the purpose of each lib release in the ChangeLog file in GitHub repository.
For a specific issue about .NET client lib, I recommend to ask in the issue section of the repository.
There will be the lib owner answering your question more specifically.
Every time a release is being made to Library, is it mandate that we need to make code changes in our Application?
You don't always need to do so.
But I recommend to use the latest version as soon as possible, so that you can avoid any known bugs and can use the latest available features.