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 we can do alone, we do. we've fine tuned our aw api layer so that it contains many features and intricate details which we won't be able to get out of the box from any library. we are doing our best to eventually get rid of the .net framework. i really appreciate the help and high professional level of the adwords api team, and especially the forum and email support. both have saved us several times, thanks -- 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.
