Thanks Alana, I had tried giving myself sysadmin rights previously, but was still getting permission errors. The trick from that article, to put the database in single user mode first, got things working. Cheers, Rob

Replying to myself: This is due to chromium protection feature. I successfully downloaded it via Firefox. Solved then

Hi @jimthomas1_7698, Thanks for bringing this to our attention, we will get that updated! Thanks, Rich

Hi @jimthomas1_7698 , What should target #0 be? (Deployment Target currently says 'Build to localhost', is that what target #0 refers to?) This message could definitely be clarified; but it basically means that Deployment Target isn't set for the first stage. If you see "Build to localhost" on the pipeline overview page, I'm guessing you didn't "Commit" the changes (save) -- it's at the top of the page. You have to explicitly save the pipeline that you're editing. Where in the Publish command do I specify the Resource Group, Resource Name and Subscription? Or will BuildMaster pull those azurewebsite publish parameters from the project's Properties/PublishProfiles .pubxml file? I'm not familiar enough with azurewebsite publish to be honest... but under the hood, the DotNet::Publish operation calls to dotnet publish. So if your project is configured to use the PublishProfiles... then maybe it will work? You can pass additional arguments into DotNet::Publish (which will get directly passed to dotnet publish, using the AdditionalArguments parameter) FYI: Deploying to Azure Websites is a Deployment Script Template we intend to create later. It's unfortunately a little complicated to do, since it primarily reles on a Which, if any, of the documentation can I rely on for help? We put that "Documentation Renovation in Progress" warning on the pages that are outdated; there's not too many of them with that warning... and we're making our way through them one page at a time In any case, don't hesitate to ask questions - it is often an opportunity for us to improve our software or documentation.

Hi @kenneth-garza_2882 , That should be the case, under the hood, ProGet is using this API: https://learn.microsoft.com/en-us/windows/win32/fileio/creating-and-using-a-temporary-file According to the docs for GetTempPath, the first path found will be used: The path specified by the TMP environment variable. The path specified by the TEMP environment variable. The path specified by the USERPROFILE environment variable. The Windows directory. So it seems there's many way to specify this.

Brilliant! Thanks again @atripp!

I've logged this as an issue in the upack repo, and we should have this included in an updated version within a day or two. Thanks!

Hi @p-pawlowski_8446, I'm not super familiar with JumpCloud, but it looks like they have a very nice tutorial on how to use Chocolate with JumpCloud: https://university.jumpcloud.com/courses/tutorial-using-chocolatey-for-windows-and-jumpcloud I think the main things that you will need to do with ProGet are: Make sure that your ProGet instance is accessible to the machines that you are installing the chocolate packages on In that tutorial, they showed the choco install command. You should replace that command with the one that shows in ProGet (ex: choco install 7zip --version 21.7 --source https://proget.yourserver.com/nuget/choco-demo-cached/): [image: 1670599111731-889f7fa4-b81e-4260-9c5e-67d799c9eb5d-image.png] Hope this helps! Thanks, Dan

Thanks a lot for your answer.

Hi @rehanh_0834, Do you have ProGet installed on Windows or in Docker? If you have it installed on Windows, are you using the integrated web server or IIS to host ProGet? Thanks, Dan

Hello, The Docker API is supposed to only support based bearer authentication, but in previous versions (v5) it also worked with Basic auth. There's a sample script on this page that shows how you can authenticate: https://docs.inedo.com/docs/proget-docker-semantic-versioning Cheers, Alana

@kaushal141992_6976 what Network error are you receiving? That's a large file to upload, so it's hard to say where the error is. IIS has a hard-coded limt of 4gb, but the integrated web server or Docker does not.

Yep, that must have been it, it's working now. Thanks for the help!

Hi @rob-leadbeater_2457 , This is a "hard-coded" limit that's built into IIS I'm afraid; if you use the built-in Web Server or Docker, this is not an issue. Another option is to use a drop-path for the packages. Otherwise, we have not implemented multi-part / chunked upload for Universal Packages yet; it's on our list, but there's not a huge demand for it. Cheers, Alana

Renaming the file works. ProGet is still able to server the symbols contained within the file to Visual Studio for debugging. Thank you for your help. Please consider this resolved.

@atripp Thanks!

Thank you very much!

Hi @krampusdecorous_7076, We have created a ticket, PG-2233, to fix this issue in ProGet. We are not exactly sure what is causing the issue as of yet, but we are able to recreate the issue and working on a fix. We are currently targeting Nov 18th for a release date on the fix. Thanks, Rich

Hi @joacim-svensson_8194 , It doesn't look like there's an edit page.... We'd love to learn how you're using manual vulnerabilities -- they don't have a huge use case, in my understanding. Just kind of like a quick/emergency way to block a package. Can you let us know what workflow is causing you to use manual and then edit manual vulnerabilities vs adding comments to them? Thanks, Alana

Hi @rmusick_7875 , 2CPU/4GB is pretty lightweight. What is your configuration? Like how many feeds, what kind of feeds, packages, users do you have? How about connectors to NuGet.org, etc?