Make performance data available via the client library

What steps will reproduce the problem?
1. Do a product query with a projection request for performance data
2. Inspect the feed ... the performance data is present
3. The are no methods/objects in the client library to get the data out of the 
feed, so it has to be done manually

What is the expected output?

We need the client library to provide the performance data. Right now, the data 
has clicks and dates. I've submitted a feature request to the Content API team 
to add impressions.

Current product entries come back with these nodes:
<sc:performance xmlns:sc="http://schemas.google.com/structuredcontent/2009">
    <sc:datapoint clicks="0" date="2012-04-01" />
    <sc:datapoint clicks="0" date="2012-04-02" />
    <sc:datapoint clicks="0" date="2012-04-03" />
    <sc:datapoint clicks="0" date="2012-04-04" />
    <sc:datapoint clicks="0" date="2012-04-05" />
    <sc:datapoint clicks="0" date="2012-04-06" />
    <sc:datapoint clicks="0" date="2012-04-07" />
</sc:performance>

I'm asking them to add impressions, such that the datapoint nodes look like 
this:
<sc:datapoint clicks="0" impressions="0" date="2012-04-04" />

I'm asking the .NET client library team to make these node values available in 
the client library. Right now, I have to load the product entry into Xml, walk 
the nodes, pull the child nodes of sc:performance, then walk the sc:datapoint 
nodes pulling out the click attribute data. I can do it ... in fact I am doing 
it, but I was hoping that you could roll something into the client library to 
take care of all of that for us. Give us some kind of performance data object 
of datapoint objects ... each datapoint object providing .Date and .Clicks ... 
hopefully with .Impressions coming soon.

What version of the product are you using? On what operating system?
.NET Client Library 1.9

Original issue reported on code.google.com by lglath...@gmail.com on 7 Apr 2012 at 11:26

x252618759 / google-checkout-dotnet-sample-code

Make performance data available via the client library #64