Closed ibuchanan closed 10 years ago
The API Client methods for this are in 14.0, which is not yet in the public NuGet repo. So far, this project has only depended on the latest public from NuGet (12.5), not the latest "cutting edge" from MyGet (14.0). Let's do a bit of research to see how this project reacts to the 14.0 libs before we decide to implement this.
From HipChat, it looks like upgrading the libs will work, so let's do it.
After Josh fixed the issues related with the test and he updated the versions of the dll in myget, I can build the visual studio client and all the test was passed ok. and this is a line in the log on one server in amazon:
2013-12-09 20:18:41 10.180.169.253 GET /VersionOne/meta.v1/Scope/Schedule.EarliestActiveTimebox.Name - 80 - 190.183.255.242 VersionOne.SDK.APIClient/14.1.0.243+(VersionOne.SDK.APIClient,+Version=14.1.0.243,+Culture=neutral,+PublicKeyToken=null)+VersionOne.Client.VisualStudio/9.0.0 - 200 0 0 171
at the end appears the User-Agent String.
As an administrator for VersionOne, I want to know what clients are consuming API traffic so that I know what's valuable to my end-users and what may be misbehaving. A simple approach is just to monitor IIS logs for HTTP traffic and use the User-Agent string to filter. The API Client already has a facility for declaring a User-Agent string.
Acceptance Tests