Installed the .NET 6.0 Web Hosting Bundle
I did a complete uninstall, an new install (choosing IIS)
Changed the application pool to No Managed Code and Integrated pipeline mode
And now it works, thank you for the tips.
Installed the .NET 6.0 Web Hosting Bundle
I did a complete uninstall, an new install (choosing IIS)
Changed the application pool to No Managed Code and Integrated pipeline mode
And now it works, thank you for the tips.
I tried to upgrade again but simply changing the path IIS is not enough.
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
We upgraded from 6.0.18 to 22.0.1 with InedoHub but the Web folder was missing and we could not longer access ProGet through IIS en https
When I use an api key, there seem to be no caching problems.
So I have this in my .npmrc
_auth=<base encoded string api:key>
I disabled the cache, but when I publish a new package its still not visible.
Version 1 is published
$ pnpm view @vicrea-neuron/progettest versions
[ '1.0.0' ]
Publish version 2
$ npm publish
npm notice
npm notice package: @vicrea-neuron/progettest@2.0.0
npm notice === Tarball Contents ===
npm notice 64B package.json
npm notice === Tarball Details ===
npm notice name: @vicrea-neuron/progettest
npm notice version: 2.0.0
npm notice package size: 162 B
npm notice unpacked size: 64 B
npm notice shasum: 7187dcb1f33b4025539a79b0728b0b33dd44af9a
npm notice integrity: sha512-G+8QbHgghLq4g[...]/Cn6P+qby28eQ==
npm notice total files: 1
npm notice
It does not show up
$ pnpm view @vicrea-neuron/progettest versions
[ '1.0.0' ]
Only after an IIS reset version 2 is visible
$ pnpm view @vicrea-neuron/progettest versions
[ '1.0.0', '2.0.0' ]
As far as I know I did not do anything other then what the documentation said.
Which IIS settings would you like to see?
We changed from http to https using this documentation
https://docs.inedo.com/docs/various-iis-switching-to-iis
But now when we publish an npm package with npm publish we don't see the new version with pnpm view only after an IIS reset is the new package visible.
The package also don't show up in Latest Local Packages list, but do after an IIS reset