ok thanks for looking in to this.
fyi: I think I found out what kind of feed ist used. It seemed to be a Chocolatey Simple Server https://github.com/chocolatey-community/simple-server/tree/master
So it is V2 API based, but with some chocolatey customizations. This project seems to be deprecated by the chocolatey team.
d.mischke_3966
@d.mischke_3966
Best posts made by d.mischke_3966
Latest posts made by d.mischke_3966
-
RE: ProGet 2025.12 Published date is default value on packages from connector feed
-
RE: ProGet 2025.12 Published date is default value on packages from connector feed
I do not know exactly witch api version the feed is hosted on. I guessed it by the Version in the URI and that the feed is xml based.
This is the landing page when I type the feed URI in my browser.
Everything else seems to work just fine. But if you say it is out of support, then I gonna pull all packages from the connector to my feed.
Also I am trying to convince the owner of the feed to update his server and hope that I don’t run out of disc space.Thanks,
Dirk -
ProGet 2025.12 Published date is default value on packages from connector feed
Hello there,
I use a Connector to access packages from a third party V1 Nuget Feed.
the published date shown in the package metadata page defaults to "01.01.0001 01:00:00" on all packages that are not pulled to the feed.
If I connect a nuget client to the proget feed I get exceptions when the client tries to query the available package versions.
The exception thrown is:
The UTC time represented when the offset is applied must be between year 0 and 10,000
The Screenshot is from NuGet Package Explorer, but other clients show this error as well.
I hoped to use this approach to get Nuget V3 API functions on a legacy feed.