Hi, I wouldn't classify this problem as a bug with the AdWords API. There is a name conflict between a built-in .NET class and a class generated from the AdWords API WSDLs, and .NET's WSDL code generator (wsdl.exe) doesn't handle the conflict well. A detailed analysis of the issue, as well as the work around, is available here:
http://code.google.com/p/google-api-adwords-dotnet/wiki/MakingCSharpWorkWithv200909 Best, - Eric Koleda, AdWords API Team On Jan 26, 4:30 am, Soapy <[email protected]> wrote: > Are there any plans to fix the bug, where the new version of the api > is not compatible with desktop .net applications? > > Seehttp://groups.google.com/group/adwords-api/browse_thread/thread/fcde4... > > There's now less than 100 days left before V13 is dropped, we have 3 > desktop applications that need converting and this bug is a real show > stopper for us. > > We are using VB (express 2005) so the .net c# library is not suitable -- You received this message because you are subscribed to the Google Groups "AdWords API Forum" 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/adwords-api?hl=en.
