in short, there are 2 reasons:
1. the first one is that we've been using adwords api since v1. the
aw .net client library appeared several versions/years later.
2. i am not familiar with the aw api .net library, but i suppose it's
a good one. we are a 'do-it-ourselves' company. that is, the more
Hi Albert,
I'm glad you were able to implement a solution to this problem. Anash
would be better able to answer these questions, but I believe the
AdWords API .NET client library is build on .NET 2.0 to allow for the
widest adoption, as many developers haven't yet switched to .NET 3.0
(yourself i
thanks Eric Koleda,
i got help on this from Anash. he offered 2 resolutions:
1. the wsdl dummy one
2. and modifying the generated by wsdl.exe code
i choosed to use the second one, here it is:
-quote from Anash's email---
Search for all variables in your stub file, that looks like:
[S
Hi Albert,
I am not an expert on the topic, but from what I know the .NET 2.0
WSDL generator (wsdl.exe) is to blame in this case. When it is
creating classes from the WSDL, if it finds an array of arrays it will
collapse the entire structure into one flat array. The error is
caused when the arra
