Hi Ben.
Thank you for the clarification of the problem scope.
Look forward to the fix.

Thank you for the quick response, much appreciated +1

Inedo has excellent support and reacts promptly.

Our buildserver tries to upload new packages to Proget at every build.
If the package already exists with same version then the server responds with http code 403.
In the past it contained a message, so this is a bit more to the standard.
The issue is that it is very hard to know why you get 403 from the proget server.
We know that the buildserver cannot overwrite packages so 403 is not an issue if it was ONLY about overwriting packages rights, and we will allow the job to succeed.
But you also get 403 if you have faulty credentials and for that the buildjob MUST fail.
We think that it should be much more explicit why we get 403 as response from proget so we are able to implement different methods for handleling the response.

It could be as simple as to describe in the body what went wrong or maybe choosing other code - albeit i can appreciate that 403 describes the scenario but in too broad terms.

Product: ProGet
Version: 5.0.10

Hi Tod
Thanks for the fast response.

Since i am not relying on the statistics of Proget i have solved the issue with a bit of work.

• Created new feed that uses new standards
• setup custom feedpath and droppackage path for bulk import
• on the server i located that packages on the filesystem and dumped into the appropiate bulk import folder.
• wait a minute or two and the new feed has all the packages.
• Rename feeds so the new one has the name of the old deprecated.

It is a workaround but it works but again - you loose statistics.
Symbols and Source seem to survive :-D

We have been using Proget for years and Symbols and source server has worked pretty well for our .NET 4.* packages.

We are now building net standard 2.* packages and Proget will no longer serve symbols nor source anymore.

Proget states that Package Source : ProGet Hosted
but nothing is indexed etc.

It relates to https://inedo.com/support/questions/6804 as well.

I have confirmed that packages contains PDB and source files.

Command to build csproj used is:
dotnet pack -c Release --include-source --include-symbols

Is there a plan for supporting source and symbols for these package types?

Product: ProGet
Version: 5.0.7

Trying to upgrade a feed:
This feed uses the ProGet 4.0 schema for NuGet package metadata. It will continue to work indefinitely, but does not support Semantic Versioning 2.0, which recent versions of the NuGet client support.

The upgrade fails because of pretty clear error, Null constraint, but that should not happen - right?
Seems like the upgrade script is not taking care of all the possible scenarios.
Any suggestions as to how to proceed?

Error:

Beginning database transaction...
Database transaction created.
Gathering list of packages in feed...
Found 1642 packages.
Migrating packages...
Migrating ABCpdf 10.1.0.8...
Unhandled exception: System.Data.SqlClient.SqlException (0x80131904): 515`16`2`NuGetPackagesV2_CreateOrUpdatePackage`82`Cannot insert the value NULL into column 'PackageHash_SHA1_Bytes', table 'ProGet.dbo.NuGetPackageVersionsV2'; column does not allow nulls. INSERT fails.
Transaction count after EXECUTE indicates that a COMMIT or ROLLBACK TRANSACTION statement is missing. Previous count = 1, current count = 0.
   at System.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__174_0(Task`1 result)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Inedo.Data.DatabaseContext.DbResult.<CreateAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Inedo.Data.DatabaseContext.<ExecuteInternalAsync>d__33.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Inedo.Data.DatabaseContext.<ExecuteNonQueryAsync>d__31.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Inedo.ProGet.Executions.MigrateNuGetFeedExecution.<ExecuteAsync>d__16.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Inedo.ProGet.Service.Executions.ActiveManualExecution.<ExecuteAsync>d__7.MoveNext()
ClientConnectionId:dec39986-dc1e-4dcf-9d29-646f03280442
Error Number:50000,State:42,Class:16

Product: ProGet
Version: 5.0.7

Solved by using link by Martin Helgseen
http://inedo.com/support/questions/7217

Thanks

Just upgraded Proget to 4.8.4

First issue.
Get a warningbar in the top stating
Warning: The Inedo Core extension is not loaded, most ProGet functionality will be missing.

Entering Admin mode and navigating to extensions.

• We do not currently use any extensions but since the warning states that the InedoCore is not loaded, and it is an extension itself i think - Ill install the InedoCore Extension.

Steps.

• Under available extensions click the extension: InedoCore
• Click Install in new Modal window
• Installation fails:

Unhandled exception: System.ArgumentNullException: Value cannot be null.
Parameter name: targetDirectory
at Inedo.Common.WebApplication.Pages.Administration.Extensions.OtterDenClient.<DownloadFileAsync>d__11.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 Inedo.Common.WebApplication.Pages.Administration.Extensions.ExtensionUpdater.<UpdateAsync>d__26.MoveNext()

Product: ProGet
Version: 4.8.4

Hi Tod
That is great news +1
Thanks for the very fast reply and hotfix release, which i look forward to.
For now we have stabilised by loading a backup of our Proget server, rolling back to 4.6.7 so we are good for now :-D

Regards
Thomas

Hi.
We use the free version of proget.
We only host internal packages.

I just updated from 4.6.7 to 4.8.1 and now hell has broken loose.

None of our internal packages has a license since they are by nature internal and we have no need for it right now.
Unfortunately alle our packages are blocked on proget and we have many packages.

How can we solve this quickly - it must/should be possible to allow packages without licenses.

I look forward to hearing from you.

Product: ProGet
Version: 4.8.1

Hello Shane,

You can add this as a script from Admin → Manage Scripts:

param($projectDir, $buildType)

powershell -file $projectDir/Resources/tools/PreBuild.ps1 -projectDir $projectDir -buildType $buildType

Then, from the deployment plan, adding "Execute PowerShell Script" with that script will give you fields for the two parameters.