Provider creates Chocolatey install dir at root of C:

[rkeithhill]

For those of us using both Chocolatey (choco.exe) and PowerShell's Chocolatey provider there is unfortunately now two different places to look for downloaded and installed packages. The Chocolatey provider is using the old location C:\Chocolatey. The newer versions of stand-alone Chocolatey are using C:\ProgramData\Chocolatey. This means I have two different places to look for installed packages and more importantly, there are now two different Chocolatey.config files. That means I have to manage the two chocolateys separately which is not intuitive. If I use Register-PackageSource to register a new Chocolatey source, it should be available if I use choco install but it isn't.

Also note that the choco install attempts to remove C:\Chocolatey. This can't be good for PowerShell's Chocolatey provider.

[CMCDragonkai]

I just experienced this now. How can we use both choco and the chocolatey provider at the same time?

[ferventcoder]

I see you just added this to https://github.com/chocolatey/chocolatey-oneget. Thanks!