Take a look at Changing an Inedo Product's URL with the Integrated Web Server; after setting up a certificate, you can follow this guide to register https urls, and edit the configuration file to listen on port 443 for ssl.

You may want to check hte IIS error logs to see if anything pops-up; there is no additional configuration needed on the ProGet side (just run the installer), and it's most likely the case the request isn't even being routed to PorGet software. IIS has so many configuration options, that it's possible something was inadvertantly misconfigured at a root level. As an alternative, you can just use the Integrated Web Server, and then try to later upgrade to IIS once you get things working.

At this time, the NuGet team has no plans to make the v3 API publicly consumable, and will support the v2 API indefinitely as the public API; as such, we have no intention to reverse engineer and attempt to implement a private API. Note this it is entirely a "behind the scenes" transport mechanism (JSON vs XML) and makes no difference at all from a usage perspective.

I understood. Thank you for your post, Alana.

You could install the SQL Tools, but there may be a osql.exe installed that you could have command-line access to.

Here is an example path to a .pdb file, the same folder contains .dll: C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\lib\dnx451\JA.AppCentral.Logging.pdb Package folder also contains the source in C:\Users\nsitnikov.dnx\packages\JA.AppCentral.Logging\0.1.7-Build1\src folder

Hi Dean, thanks for your reply. Redownloading the installer has resolved the issue. Best Regards Alex

Great! Thank you for the quick response, and also for an excellent lead time. Impressive!

A FileSystemWatcher is used, so any changes to the directory will trigger an import.

Hi Junaid, This is a known issue with npm; basically it's sending a JSON document with two "dist" properties. For example... { "dist": "value1", ..., "dist": "value2" } The JSON Library we're using isn't too keen on that, and we already have a fixe (PG-603) planned/scheduled for the next release.

That was it. The user had access, but not permission to change schema. I really think this should be catch and a nicer message displayed instead of the installer just crashing though.

Hello; I believe the error is due to a bug in the LdapDirectory code, which is not properly escaping that group name that has a parenthesis in it. So, we will need to fix the bug; I've logged this as PG-602, and we can get it in the next maintence release (which is targeted for next week). Best, Steve

Ok, so I have now got something working. It seems it was failing because I had the smaller installer (without sql server). That does absolutely nothing when running the silent command. If that's meant to be the case, then maybe that should be documented somewhere. Thanks

Is there anything listed on the Administration > Error Log page that relates to this? Errors listed there will have additional context (feed, connector, etc) If it doesn't appear there, I guess you could enable 1 at a time to see which one is the culprit.

Ah yes, that solved my problem. Thanks!

We do, along with a few other types (Gems, PyPi, Composer), but there's no ETA on it right now; once we get private a Docker registry, we will look to refactor the feeds and UI a bit as to allow for easier adding of simple package types.

Chocolately packages are, essentially, nothing more than a powershell script that downloads and runs an installer from some url on the internet. It would be virtually impossible to inspect arbitrary powershell scripts and determine what they would download when run, and then download/proxy those installers. So, if you want full control over all aspects of the chocolatey packages (including the installers that are downloaded), you will just have to create your own based on the contents of the open-source packages.

Currently, only NuGet feeds use the license filter, it shouldn't be displayed on npm feeds... We do plan on adding support for better licensing filtering in a future version, as the current implemention is a bit limiting.

OK, I was supposing it but I didn't find it explicitly in documentation. Thanks for your quicker answer.