Skip to content
Merged
Changes from all commits
Commits
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
Original file line number Diff line number Diff line change
Expand Up @@ -47,7 +47,7 @@ You might choose to use this over installing a full PowerShell module if you did

### Extension Package

An extension package is organised much like any other Chocolatey package - though instead of the scripts within the `tools` directory you may be familiar with, there should be an `extensions` directory.
An extension package is organized much like any other Chocolatey package - though instead of the scripts within the `tools` directory you may be familiar with, there should be an `extensions` directory.

We'll now run through how to create an extension package, assuming you have an environment set up as in <Xref title="Preparing Your Environment for Package Creation" value="howto-prepare-env" />.

Expand Down Expand Up @@ -79,6 +79,9 @@ Follow the steps below to get started:
<summary>Extension package for testing.</summary>
<tags>extension chocolatey package</tags>
</metadata>
<files>
<file src="extensions\**" target="extensions" />
</files>
</package>
```

Expand Down Expand Up @@ -124,6 +127,8 @@ function Set-ConfigValue {
$Configuration | ConvertTo-Json | Set-Content -Path $Path
}
}

Export-ModuleMember -Function Set-ConfigValue
```

So, if you browse through the files in VS Code or Explorer, you should see a file structure like this:
Expand Down