Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.

If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!

Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you may not be able to execute some actions.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Topics created by a.m_8178

A

Cannot push ruby gem
Support • proget feeds ruby • 11 Jan 2019, 10:07 • a.m_8178 7 Feb 2019, 04:09

3

0
Votes

3
Posts

21
Views

? 7 Feb 2019, 04:09

Upgrading to v5 seems to have fixed this
A

Dates returned by NugetV2 API in JSON
Support • proget nuget api • 21 Jun 2018, 10:46 • a.m_8178 22 Jun 2018, 15:48

2

0
Votes

2
Posts

19
Views

? 22 Jun 2018, 15:48

This is actually an artifact of the OData specification from when ProGet was first developed - that was actually the preferred format specified, and NuGet.org didn't support $format=json, so we just followed the OData spec. Anyway, those are just .NET DateTime Ticks in there (and the +0 just indicates UTC), so in your example it would just be: new DateTime(636650168208570000, DateTimeKind.Utc) Of course, if we had it to do over again, it would be something more sensible like ISO-8601.

Inedo Website Home • Support Home • Code of Conduct • Forums Guide • Documentation

Topics created by a.m_8178

Cannot push ruby gem Support • proget feeds ruby • 11 Jan 2019, 10:07 • a.m_8178 7 Feb 2019, 04:09

Dates returned by NugetV2 API in JSON Support • proget nuget api • 21 Jun 2018, 10:46 • a.m_8178 22 Jun 2018, 15:48

Cannot push ruby gem
Support • proget feeds ruby • 11 Jan 2019, 10:07 • a.m_8178 7 Feb 2019, 04:09

Dates returned by NugetV2 API in JSON
Support • proget nuget api • 21 Jun 2018, 10:46 • a.m_8178 22 Jun 2018, 15:48