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:
[System.Xml.Serialization.XmlArrayItemAttribute("operationResults",
typeof(OperationResult), IsNullable = false)]
public OperationResult[][] operationStreamResults {
...
}
and change them to
[System.Xml.Serialization.XmlArrayItemAttribute("operationResults",
typeof(OperationResult[]), IsNullable = false)]
public OperationResult[][] operationStreamResults {
...
}
Note the extra [] on XmlArrayItemAttribute. This change will allow
code to
compile and run fine, though I haven't verified if the server results
will
still be deserialized properly.
...
-----end quote----------------------------
i've encountered several more issues, most probably due to wsdl.exe
(bugs?). i've solved them - some with people's help and others alone.
could it be that wsdl.exe has swithes/options which are misused or not
used at all?
the other strange thing for me is why aren't there other .net users
asking those questions?
could it be that they are using .net3+ with the new wsdl tool (don't
recall it's name - wcf or something), and all those issues are solved
there? and if that's so, why is the adwords client library team
for .net not using .net3+? i am not pro-.net3+, just asking,
thanks in advance,
albert
--
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.
