Skip to content
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.

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

Follow Visual Studio Extension Checklist #116

Open
1 of 6 tasks
jcansdale opened this issue Jun 11, 2018 · 0 comments
Open
1 of 6 tasks

Follow Visual Studio Extension Checklist #116

jcansdale opened this issue Jun 11, 2018 · 0 comments

Comments

@jcansdale
Copy link
Owner

jcansdale commented Jun 11, 2018

Visual Studio Extension Checklist

Here is a list of things to make sure to remember before publishing your Visual Studio extension.

Adhere to best practices

Add high-quality icon

  • All extensions should have an icon associated with it. Make sure the icon is a high-quality .png file with the size 128x128 pixels in 96 DPI or more. After adding the icon to your VSIX project, register it in the .vsixmanifest file as both the Icon and Preview image.

Add license

  • This license will be shown on the Marketplace, in the VSIX installer and in the Extensions and Updates... dialog. One should always be specified to set the expectations for the users. Use choosealicense.com to help find the right license for you.

Write good Marketplace description

  • This is one of the most important things you should do to make your extension successful. A good description consist of:
  • Screenshots/animated GIFs of the UI added by the extension
  • Detailed description of the individual features
  • Links to more details if applicable

Show in Help/About

  • All extensions can be present in the Help -> About Microsoft Visual Studio dialog box. To do that, add an InstalledProductRegistration attribute to you Package class and make sure the name, description and version are accurate.
[InstalledProductRegistration("The name", "The description", "1.0")]
public class MyPackage : AsyncPackage
{
   ...
}

Use KnownMonikers when possible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant