VersionOne API Client vs .NET object Model

Question

I'm creating a dashboard which will display data from many sources including VersionOne.

The basic high level data which I plan to display in dashboard is :

sprint burndown chart release burndown chart open/closed stories for current sprint etc...

All the data is basically for reporting purposes.

My confusion here is which of the two techniques to be used for development.

I remember reading in one of the forums that .NET object model is basically used to create assets and not all reporting metrics can be obtained using .NET object model and we have to use api client.

Any information before I start my design and coding will be appreciated.

Thanks, -Dilip M

Answer 1

The Object Model libraries for both Java and .NET are in sunset now. For support reasons, I recommend against the Object Model. Also, the main reason for sunsetting the Object Model was poor performance that would require significant, breaking changes to fix. So for performance reasons, I also recommend against using the Object Model.

I do recommend using our query.v1 endpoint with standard HTTP and JSON libraries. There are a number of recipes that already explain how to extract the data, including one for burndown data.

You didn't mention whether you were an on-premise or hosted customer. On-premise customers have the option of accessing a datamart using SQL.