Skip to content

Commit 2f4c88b

Browse files
authored
Merge pull request #1077 from gep13/fix-extension-docs
(doc) Remove incorrect line about extensions
2 parents 2eff204 + 7e1c579 commit 2f4c88b

File tree

1 file changed

+0
-2
lines changed

1 file changed

+0
-2
lines changed

src/content/docs/en-us/guides/create/create-extension-package.mdx

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -132,8 +132,6 @@ Open the `example.extension.nuspec` file in VS Code and modify the metadata as a
132132

133133
That's all you need!
134134

135-
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.
136-
137135
#### Creating Your Install Script
138136

139137
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!

0 commit comments

Comments
 (0)