With Fiddler comparison I have found that our feed was configured to expose nuget with v2 apis only. (ODATA v2)
Enabling JSON-LD (v3) api and appending v3/index.json to api url solve my issue and all is working as expected.
I think that something is missing on Proget on v2 only implementation. Not a big deal for me, but maybe is something to consider for the product.
Hi @Dan_Woolf,
we have upgraded the system.
Now we can see connector infos via web UI, and we can perform some operations like manual download and proget pull.
But we are hitting a new issue when we are trying to install a new version of a package that is not already pulled into ProGet: it seems it not exists.
In example package manager console returns this:
Install-Package Package.Name -Version 1.2.3.4
Package 'Package.Name 1.2.3.4' is not found in the following primary source(s): 'http://proget.mydomain.internal/nuget/test/'. Please verify all your online package sources are available (OR) package
id, version are specified correctly.
Via both VS2022 and Nuget Package Explorer we are also unable to list available versions from Connectors: we only see pulled versions.
I'm not sure is related, but on connector page the counter still count 0
Hi @Dan_Woolf ,
thanks for your quick feedback and fix, I'm going to reset Telerik access.
Cheers,
Claudio
Hello @stevedennis,
thanks for your quick response. You can check your email; I have sent you some additional informations.
I can confirm that Telerik's nuget API are working as expected on Visual Studio (2019/2022) and Nuget Package Explorer.
Cheers,
Claudio
I had configured a connector to Telerik in a proget 5.x and it worked well.
I've upgraded to 6.0.5 (Build 9) and I'm hitting an issue.
Connector listing works well on webui, but trying to visit a package page an blocking error occurs.
Category:
Web
Url:
http://proget.mydomain.internal/feeds/test/Telerik.Package.Name/versions
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.]
Inedo.ProGet.WebApplication.Pages.Packages.Versions.<CreateChildControlsAsync>d__47.MoveNext() +827
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +32
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.ProGet.WebApplication.Pages.<InitializeAsync>d__12.MoveNext() +621
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +32
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.Web.PageFree.<ExecutePageLifeCycleAsync>d__57.MoveNext() +327
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +32
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.Web.PageFree.<ProcessRequestAsync>d__56.MoveNext() +319
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +32
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) +59
Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest(IAsyncResult result) +36
System.Web.CallHandlerExecutionStep.InvokeEndHandler(IAsyncResult ar) +241
System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +172
On diagnostic center there is also another error as follows:
Category:
Connector
Message:
Connector telerik.com error: Object reference not set to an instance of an object.
Details:
System.NullReferenceException: Object reference not set to an instance of an object.
at Inedo.ProGet.Feeds.NuGet.NuGetConnector.<SearchAsync>d__26.MoveNext()