After October 2 - Can not use the AdWords API any more

[Nadav De Bruin]

As stated here "on October 2, 2017. After this date, all v201609 API requests will begin to fail."

The recommendation is to migrate to newer version.

We use:

Google.AdWords v18.34

Google.Ads.Common v3.18

I've tried to migrate but get error that the .Net 4.5 Framework is not supported by the new version.

We can not upgrade the framework for this project because other dependencies and it is very sensitive project in the production environment. 

So it seems that we are going to stop using the AdWords API.

If someone can help here we'll be happy. 

[Peter Oliquino]

Hi Nadav,

Could you tell me more about the dependencies that you are considering that might be affected when you migrate to the latest version? Our release notes and migration guide should provide you with the information you need regarding the changes that have been applied in the latest version so you can also make the necessary adjustments in your code if applicable.

As for the the configuration of your .NET client library, you may get in touch with the library owners via this link as they are more equipped to assist you with this concern.

Thanks and regards,

Peter

AdWords API Team

[Nadav De Bruin]

This is a big scheduler project that hosts many integration APIs implementations for many systems not just to AdWords.
No one will take the risk here to upgrade to v4.5.2 

[Zweitze]

A few years ago I was in a similar situation, when Google moved the framework from 2.0 to 4.0 - but my software was closely tied to SharePoint v3 (2007) which is .NET 2.0.

To stay on .NET 4.0 you have a few options:

• Stop using the library, and add webservice references in Visual Studio directly. VS will study the webservices itself and come up with something. So you'll miss all the library stuff like ReportUtilities but at least you got something workable.
  
• Build your own version of the library.
  

I did the second. I downloaded the sources of the library from the OLD framework. Then I downloaded the sources of the next version, on the newer framework. I compared all sources and made up my own library, which essentially was the old library plus handpicked improvements of the new library.
After that, I downloaded the sources of the oldest version of the library that was supporting a newer AdWords API. I compared those sources with the sources of what I call "next version" above, and applied the changes to my library. Then I had a library supporting a newer version.

This method only works when the library developers don't apply very big changes. It bought me 18 months (!) and then we were finally ready to move to the newer .NET version. You probably have less time because the library developers are trying to have the library support .NET Core and other things, which implies big changes.

Oh, one more thing: On 2 October v201609 will not completely disappear. It will keep working, but every now and then you get a sunset error. If you retry you may get the right answer. This works for another few days, maybe weeks. Disclaimer: this was the behavior about 2-3 years ago, I don't know if it's still the case and I can't predict how Google will handle this on October 2 and onwards.

[AdWords API Advisor]

Hi Nadav,

I'll second pretty much what Zweitze said. I'll ask my colleague to follow up on the bug you filed on the issue tracker with details, but the short summary is that you can take the github snapshot, compile it for .NET4.5 and use that binary for approximately 8 more months -- until v201708 sunsets. We might continue making changes to the library, but it shouldn't matter as long as you are looking for a specific bug fix, which we will resolve as appropriate.

Please don't stay on v201609, upgrade to v201708 and we will help you out on the issue tracker thread. 

For the long term, try moving to .NET 4.5.2 or a newer version. We moved to .NET 4.5.2 since the lifecycle for .NET 4, 4.5 and 4.5.1 ended last year. See https://support.microsoft.com/en-us/help/17455/lifecycle-faq-net-framework for additional context.

Cheers

Anash P. Oommen,
AdWords API Advisor.

[Nadav De Bruin]

Thanks,

Downloaded the source project from GitHub and build it with v4.5.

Hope that will work for for a while until we'll upgrade framework to 4.5.2