Hi Sebastian, You can access all of the DNC packages using the ODATA (v2) protocol API. If you're finding an issue with it, it's totally unrelated to the API protocol. Please submit a different question with specific packages, reproduction steps and we can investigate Cheers, Alana

There should be an official v1.0.0 version released with that exception fixed. Before attempting to install it, manually delete Artifactory.* from your Extensions path ({InstallDir}\Extensions) .

Sadly, for me, the given DLL cannot just be dropped into the folder to replace the old DLL without producing a binding redirect error: [FileLoadException: Could not load file or assembly 'ProGetCoreEx, Version=5.1.3.10, Culture=neutral, PublicKeyToken=20535527eaf4e568' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)] Inedo.ProGet.WebApplication.<BeginFirstRequestAsync>d__2.MoveNext() +0 System.Runtime.CompilerServices.AsyncTaskMethodBuilder.Start(TStateMachine& stateMachine) +114 Inedo.ProGet.WebApplication.ProGetHttpModule.BeginFirstRequestAsync(HttpApplication app) +90 Inedo.Web.<HandleBeginFirstRequestInternal>d__28.MoveNext() +306 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31 Inedo.Web.InedoHttpModule.ProcessEnd(IAsyncResult ar) +117 System.Web.AsyncEventExecutionStep.InvokeEndHandler(IAsyncResult ar) +219 System.Web.AsyncEventExecutionStep.OnAsyncEventCompletion(IAsyncResult ar) +159 System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() +31 System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +611 System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +213 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +131 ProGetCoreEx is version 5.1.3.9, however it expects 5.1.3.10

Thanks for the clarification. Unfortunately I can't mention any commercial products because the site this will be published on requires that commercial products be sponsors of the site. Unless Inedo wants to be a sponsor for 4sysops ;-)

This particular error (the 500) will be fixed with PG-1313

This will be fixed with PG-1313

I see what you mean. Though in this video the suffix is used for dev versions or release candidates. But I guess we could (ab)use this for branches. Will try and see how it goes.

Thanks for the additional troubleshooting. I suspect this is due to the way we are migrating dates from the old table to the new. I've created an issue to track this here. (It may not be publicly accessible yet, it's a new project and the permissions may not have propagated)

Otter, BuildMaster, Hedgehog, and ProGet for Windows all require any supported version of Microsoft SQL Server. So, 2017 would be supported, since Microsoft supports it still. 2005, however, not.

After more investigation I discovered the problem was due to lack of permissions on the Storage folder assigned (DOH!). Would be a good idea to improve the ProGet error message as you indicated so it gives a more helpful clue. Thanks for your help. Dwight

It autocomplete/dropdown uses Username & Password credentials for the Package Source URL. I also agree, that it should support both or at least be clear which type it's using :) The tracking issue for this is here: HH-17

Now I did see one version of BuildMaster (v6.0.5... maybe?) having some issue resolving $ServeRName, but it was fixed. Try upgrading to latest v6 as well...

If you need to supply credentials when connecting to the domain, make sure "Specific list..." is selected, and enter it as: domain.local,CredentialName Where CredentialName is the name of set of Username & Password resource credentials created via Admin > Change User Directory > Advanced > AD Credentials > Create

Thank you so much, build master now works.

You can actually put a full commit ID in the Tag field (which actually supports any refname)... I'll have someone put a note in to change that in the operation.

Stoyan -- this is really no way of doing this on Windows. It's simply a limitation of the operation system, and has been for over 10 years. You cannot have something that runs under a service context (BuildMaster and Inedo Agents run as a service) interact with the desktop UI in anyway. You cannot "escape" a service context in any way. So from within a service, you can't launch a program that launches a program that launches a program etc., that launches a WPF application. You would, instead, need to write a desktop application that monitors "something" (a drop folder, pipe, etc), and then reacts when that that changes.

Thanks for the quick update John. Definitely looking forward to the 5.1 release now, once it is out of Beta.

We have added these exclusions to the Web.config that we include with ProGet.

The tracking issue for this is here: PG-1309