Bug Reports

The newest version of Proget doesn't appear to work via IIS install. Not sure it's setting it up right, but you get a 403 directory browsing not enabled.

Rolling back to the previous minor version, the install works as expected.

There was an issue with the newer version where packages would not fill in on the ui when you dumped them in the folder and it would get out of sync and say the package can't be found even though it was in the folder. We have quite a few feeds and packages. Reverting back to the previous minor version fixed this problem. I can't give you a ton of details as at first I tried rebuilding the server with the newest version (which failed due to the above issue). I didn't want to spend a lot of time on it, so I reverted it to the previous minor version.

It appears that if your Package name has "Soap" in it or at least the suffix of the package is .Soap, you get a 404 specific proget error page with this error message.

/api/v2/package/builds/Ipc.Boarding.Endpoints.Soap/1.3.0.4 does not map to any handlers. The URL may have been entered incorrectly or linked to from an old reference.

changing the package to Ipc.Boarding.Endpoints.Sp made it work, but no matter how many I generate under the previous name, I always get the same error

Hi, this is a bug in the installer; can you set the AppPool to "Classic". There is in issue in some instances with Integrated pipeline, that will cause this.