PowerShell / PowerShell/PSResourceGet

Powershell shouldn't install modules to MyDocuments as thats not for applications

Open
#195 7 comments 12 reactions 1 assignee View on GitHub

@alerickson is already working on this.

Since May 11, 2022.

Area-Install Issue-Bug Issue-Discussion Status-Investigating
Dominant language
C#
Stars
576
Forks
114
Avg merge
1d 2h
Merged PRs (30d)
7

Description

Microsoft is pushing more and more during Onedrive setup to have MyDocuments managed by onedrive.

Being a good dev and not running elevated means installing packages with -Scope CurrentUser but this means packages are stored in MyDocuments\WindowsPowershell or MyDocuments\Powershell. This means all modules are then synchronised up to OneDrive.

This is made worse by sporadic issues due to connecting of Onedrive.

  1. Collisions with OneDrive and the install-module resulting in modules not saving correctly
  2. Modules not used in a while get "archived off" and thus are downloaded on demand by onedrive resulting in problems when trying to load modules

Use of AppData would be much more appropriate for modules.

related items #41

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.