See: https://stackoverflow.com/questions/45063717

Ben, That works. Thank you! TLDR; don't use "MultipartFormDataContent" when making this request.

I think its now implemented: https://inedo.com/proget/versions 5.0.9

Hello Charles, upack pack expects a directory, not an individual file, so the command should be: upack pack C:\location_of_upack_json_file C:\directory_containing_my_setup_exe --targetDirectory=C:\mytargetDir\build_artifacts

Never mind, found the 5.0 beta :-)

The default PDB format for the project files was changed from Full to Portable (see https://github.com/dotnet/core/blob/master/Documentation/diagnostics/portable_pdb.md). The portable format is not compatible with the symbol server. To switch back to the old format just add this to a property group in the *.csproj file: <DebugType>Full</DebugType>. You can also override this with /p:DebugType=Full in your build command. Also make sure that the nuget packages are created with --include-symbols --include-source

I'm having the same issue. When using this command "nuget.exe push -Source "http://{MyServer}/nuget/default/" -ApiKey "{USER:PASSWORD}" -Verbosity "detailed" .{PACKAGE}" I get these errors: NuGet Version: 3.5.0.1938 Pushing {PACKAGE}.nupkg to 'http://{MyServer}/nuget/default/'... PUT http://{MyServer}/nuget/default/ BadRequest http://{MyServer}/nuget/default/ 289ms System.AggregateException: One or more errors occurred. ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at NuGet.Protocol.Core.Types.PackageUpdateResource.<>c.<PushPackageToServer>b__19_1(HttpResponseMessage response) at NuGet.Protocol.HttpSource.<ProcessResponseAsync>d__141.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageToServer>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageCore>d__13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackage>d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<Push>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Commands.PushRunner.<Run>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.CommandLine.PushCommand.<ExecuteCommandAsync>d__28.MoveNext() --- End of inner exception stack trace --- at System.Threading.Tasks.Task.ThrowIfExceptional(Boolean includeTaskCanceledExceptions) at System.Threading.Tasks.Task.Wait(Int32 millisecondsTimeout, CancellationToken cancellationToken) at NuGet.CommandLine.Command.Execute() at NuGet.CommandLine.Program.MainCore(String workingDirectory, String[] args) ---> (Inner Exception #0) System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request). at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode() at NuGet.Protocol.Core.Types.PackageUpdateResource.<>c.<PushPackageToServer>b__19_1(HttpResponseMessage response) at NuGet.Protocol.HttpSource.<ProcessResponseAsync>d__141.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageToServer>d__19.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackageCore>d__13.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<PushPackage>d__12.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Protocol.Core.Types.PackageUpdateResource.<Push>d__8.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.Commands.PushRunner.<Run>d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at NuGet.CommandLine.PushCommand.<ExecuteCommandAsync>d__28.MoveNext()<---

Turns out that not all of the packages were being included in source control. Once I added in the missing package folders to source control I was able to move forward.

If this is happening, then the package is not being deleted from the package store on disk and is being re-added by the routine index reconcillation. The most likely cause for this is a misconfiguration (pointing to wrong file store), a file permissions error, or a back-up system restoring the package. When you delete a package, it should be deleted from the database and from the disk.

As of ProGet 4.7.4, we are no longer performing any server-side filtering based on target framework. Can you confirm that you are on the latest version?

thanks we managed to find it as nuget was packing the release and debug files over the top of each other for some stupid reason in just the packages generated for this project. no idea why it did not affect any other solution on our build server

That's what the nuget.exe client does, a Delete method. Yes. That will also remove package from disk and metadata.

For completeness: An alternate approach is to create a private source server and update to both the source server and to the Universal Feed from out in-house deployment tool. But we were hope that we could have pig-backed on what you already had. Oh well. Thanks.

An "Access to the path is denied" message is coming from Windows. Permissions aside, a likely culprit is anotherr process (anti virus, backup, etc) is locking the file and preventing access. Sometimes you'll need to use ProcMon to identify what this is. ProGet does not requests locks when reading files.

If you are getting a browser pop-up authentication (as opposed to a ProGet login screen), then it means Windows Integrated Authentication is not working. This is due to configuration of your server or domain. Unfortunately, this is performed by IIS/Windows (not ProGet), which means the request is never reaching our software; this means we can't provide any information about why it's not working. But this also means there are a lot of resources/articles you can find to give debugging on how to get it to work. I would suggest searches like, "Windows Integrated Authentication always authenticates" etc. Please post what you find!

You can Log-Information to see what $WorkingDirectory is. Unless you set a value, it will be something like C:\BuildMaster\_SVCTMP\_Ennn\D0 where nnn is internal identifier of the execution. Log-Information Working-Directory is $WorkingDirectory;

Thanks a lot. It works ;)

It looks like you probably mean to use an assembly-qualified name instead of the .Name property on line 68: So it probably should be something like: writer.Write(resultType.FullName + "," + resultType.Assembly.GetName().Name); That would generally be the minimum information you'd need to get the type with Type.GetType. That said, as you've discovered, RemoteJob is a pretty low-level interface, meant to give complete control over any over-the-wire serialization. You may want to look at the RemoteEnsureOperation as a base class to use instead, which handles the RemoteJob details internally - you just add the [SlimSerializable] attribute to properties that you want to be serialized and it takes care of the rest. You also may find the SlimBinaryFormatter class useful - it is the class that RemoteEnsureOperation uses to perform its serialization. Hope this helps!

In this case, the error message means that the user runnin the installer does not have permission/access to read the configured ProGet database (this is an upgrade).