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.

Hello Jim, Is there anything in Event Viewer → System from Service Control Manager, or anything from ProGet in the Application section of the event viewer?

Hi Ben-- This is a fantastic solution, and suits the situation perfectly. Thank you!

Please see http://inedo.com/support/questions/6445#inline-post-6445 for more information

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.

Ugh. Apparently what I meant to say was there were no changes, except for that one that causes this exact problem with npm feeds :/ Thanks for doublechecking me, looks like I needed it. (Apparently this is a very simple fix that had already been corrected by a dev for the upcoming 4.7.10, due for release today). For your reference, this is now logged as PG-1014

In case anybody wants to know, this is what worked for me: SubjectName = the CN (CommonName attribute of the subject in the certificate) Description = the Description in the certificate

We will have full support for Windows containers in ProGet 4.7.10, which is scheduled for release tomorrow.

We will have full support for Windows containers in ProGet 4.7.10, which is scheduled for release tomorrow.

If you set --targetDirectory on the pack command to an empty or nonexistent directory, the .upack file will be the only file in there, and you can use myDirectory\*.upack to select the upack file for the push command.

Just discovered Kevin's answer here which should work: http://inedo.com/support/questions/4058#inline-post-5062

That error will occur if the Amazon extension is not loaded. If you haven't already, you can download the extension form Admin > Extensions, or just follow the manual installation instructions (i.e. put it in the Extensions folder on the disk).

Hello Aris, If you click on the release number (the leftmost column) the user that created the release is displayed in the Details section.

Hello Mario, I've added resetadminpassword to ProGet.Service.exe for the next minor release (4.7.10) - PG-1009 For now, you can reset the password in the database to Admin by setting the Salt_Bytes and Password_Bytes to 0x26CF0B87A338C08CA30F and 0x5868049613BC1ED1E4E3C2E404D8B85684B53263 respectively.

Ok, I noticed that in your log, npm isn't authenticating. Is the anonymous user allowed to access the feed in ProGet?

If you upgrade to the latest v5.6 (currently 5.6.11), then it should work OK!

Hello Michael, NPM feeds don't currently support an API key, but you can share a single ProGet user between all of the users who need to upload to the feed to simulate the same thing. The Publish Packages task group on the NPM feed is all you need to upload a package. If you want to replace an already-uploaded package, you need the Overwrite Package task, which is available on the Administer and Manage Feed task groups by default, but you can create a new task group with just Overwrite Package on the Customize Tasks page (/administration/security/customize-tasks).

Hello Matt, It looks like the PostgreSQL version of Feeds_SetLastSyncDate was not updated when the MSSQL version was. I've logged this as PG-1006 and it will be fixed in the next version of ProGet.

This must be it, redownload solved it. I downloaded 5.6.11 sometime on Apr 4.