From 7e1c579ff424c5b61f5b215622ab88eef6f70965 Mon Sep 17 00:00:00 2001 From: Gary Ewan Park Date: Mon, 7 Oct 2024 02:55:15 -0500 Subject: [PATCH] (doc) Remove incorrect line about extensions The .extension file extension is a requirement when creating extension packages. It is this file extension that causes Chocolatey CLI to extract the files into the extensions folder, in the same way that the .hook file extension that causes files to be extracted into the hooks folder, and then the .template file extension that causes files to be extracted into the templates folder. --- .../docs/en-us/guides/create/create-extension-package.mdx | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/content/docs/en-us/guides/create/create-extension-package.mdx b/src/content/docs/en-us/guides/create/create-extension-package.mdx index 49b571a44f..d700e2775a 100644 --- a/src/content/docs/en-us/guides/create/create-extension-package.mdx +++ b/src/content/docs/en-us/guides/create/create-extension-package.mdx @@ -132,8 +132,6 @@ Open the `example.extension.nuspec` file in VS Code and modify the metadata as a That's all you need! -You may notice that all of the example packages above end with `.extension`. This is not required for an extension package by Chocolatey itself, but it is how we easily classify extension packages on the Chocolatey Community Repository. - #### Creating Your Install Script As we mentioned earlier, there's no need for an install script in an extension package - Chocolatey CLI handles putting the extension in the right place!