That's great news. Thanks!

Thanks. I was able to resolve this by running the full 4.8.2 installer which appeared to have a minor DB schema change. Once the DB was updated by the installer, ProGet was able to load from the web nodes when updated to the 4.8.2 binaries. I wish there was better documentation on updating ProGet in a NLB enviroment when there are updates to the DB.

Is it a "Portal PDB"? This is the new format and is not yet supported. If not, then the next step would be for you to submit a ticket with the NuGet package attached so that we can debug the pdb parsing.

You will need to open both ports; the npm api uses both HTTP and HTTPS.

Support for portable PDBs is currently an "open issue", and our initial research found that metadata information was undocumented, however since then it has been: https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PortablePdb-Metadata.md Unfortunately at this time we don't have a timetable for if or when this gets implemented, but it is on our list.

The ProGet server doesn't modify packages, except to strip embedded symbols and source code if that option is enabled on a feed. It certainly doesn't modify a package such that the folder structure is flattened. Are you certain the package isn't flattened on the server, and in addition to that, actually being downloaded from ProGet at all (versus the NuGet cache or something like that)?

Just to clarify, .NET PDBs with "full" debugging information (i.e. Windows PDB format) are supported, it is just .NET "portable" format that is currently not supported. Support for portable PDBs is currently an "open issue", and our initial research found that metadata information was undocumented, however since then it has been: https://github.com/dotnet/corefx/blob/master/src/System.Reflection.Metadata/specs/PortablePdb-Metadata.md Unfortunately at this time we don't have a timetable for if or when this gets implemented.

We've resolved this issue by running the Inedo agent service on the new build server under the same account as the Buildmaster service on our main server.

This seems to be fixed as of the Docker image containing ProGet Version 4.7.14. The Docker image hash is: b7a3d6595c21d34997b4cbe6da9187801f410f17bff8e84228711bf29396a6ab pulled on 9/6/2017

Hi, Krzysztof G., did you ever managed to integrate both Octopus and ProGet? Using just the ProGet URL we can "connect" but it replies with an empty list. Is there anything else needed? Maybe a registry path?

You can download Romp Milestone 1 here! Awesome to hear you're excited about Romp! Cheers!

This was a regression: https://inedo.myjetbrains.com/youtrack/issue/PG-1085 We will have a maintenance release out today to fix this.

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

I don't believe the NPM protocol allows for anonymous pushes. You could certainly have your CI put it in a drop folder however, which the ProGet would pick-up.

This is definitely on our roadmap; stay tuned!

This is the first request for such a feature; after v5 ships, we may consider putting this on the roadmap as a feature, depending on if anyone else requests it. These sorts of features may not be worth doing, because they are added complexity, more things to test, and only save a little bit of time during initial set-up.

I mean to add, I do have a Timeout set of 15 minutes which I would have thought would be long enough. I am bumping the timeout to 30 minutes. However, I was just looking to see if anyone else had run into issues with Symantec and/or Windows 2012r2 with artifact deployments.

It installs SQL just fine. perhaps this would help. POST http://inedo.com/proget/activation/request-key HTTP/1.1 Content-Type: application/x-www-form-urlencoded Host: inedo.com Content-Length: 80 Connection: Keep-Alive it then has a body containing the fields email fullname trial version

You can use your same license key in this case, it's no problem! The licensing agreement for BuildMaster and Otter explicitly permit dedicated dev/test instances. ProGet requires a separate server... but if it's just a temporary migration then it's also OK too.

Good to know as well on this side. Now I know how not to have configuration errors drive me nuts. Now I just have to figure out how I'm going to do this ... Looks like my network will need two ProGet servers ...