Skip to content

1/7/2025 PM Publish #182

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Jan 7, 2025
Merged

1/7/2025 PM Publish #182

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 10 additions & 6 deletions powershell-gallery/docs-conceptual/how-to/working-with-packages/manual-download.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
---
description: Describes how to manually download a package from the PowerShell Gallery.
ms.date: 11/16/2022
ms.date: 01/07/2025
title: Manual Package Download
---

Expand All @@ -19,15 +19,15 @@ can then copy to an internal repository.

Each page has a link for Manual Download, as shown here:

![Package display page with install options](media/manual-download/packagedisplaypagewithpseditions.png)
![Package display page with install options][02]

To download manually, click on **Download the raw nupkg file**. A copy of the package is copied to
the download folder for your browser with the name `<name>.<version>.nupkg`.

A NuGet package is a ZIP archive with extra files containing information about the contents of the
package. Some browsers, like Internet Explorer, automatically replace the `.nupkg` file extension
with `.zip`. To expand the package, rename the `.nupkg` file to `.zip`, if needed, then extract the
contents to a local folder.
contents to a local folder using `Expand-Archive` or some other ZIP file tool.

A NuGet package file includes the following **NuGet-specific elements** that aren't part of the
original packaged code:
Expand All @@ -45,8 +45,8 @@ original packaged code:
> Some steps performed by `Install-Module` aren't included.

The easiest approach is to remove the NuGet-specific elements from the folder. Removing the elements
leaves the PowerShell code created by the package author.
For the list of NuGet-specific elements, see [Using manual download to acquire a package](#using-manual-download-to-acquire-a-package).
leaves the PowerShell code created by the package author. For the list of NuGet-specific elements,
see [Using manual download to acquire a package][01].

The steps are as follows:

Expand Down Expand Up @@ -81,9 +81,13 @@ The steps are as follows:
1. The `.PS1` file in the folder can be used directly from this location.
1. You may delete the NuGet-specific elements in the folder.

For the list of NuGet-specific elements, see [Using manual download to acquire a package](#using-manual-download-to-acquire-a-package).
For the list of NuGet-specific elements, see [Using manual download to acquire a package][01].

> [!IMPORTANT]
> The manual download doesn't include any dependencies required by the module. If the package has
> dependencies, they must be installed on the system for this module to work correctly. The
> PowerShell Gallery shows all dependencies required by the package.

<!-- link references -->
[01]: #using-manual-download-to-acquire-a-package
[02]: media/manual-download/packagedisplaypagewithpseditions.png
Loading