I wish this help you If to believe JsonLint “ != " . They dont have the same encoding, i remember i stumbled upon it as an issue with greek keyboard if I am not mistaken. This one is valid, also according to the text coloring of Stack Overflow:
With these it helps I found a solution to this problem, and I can see the dll now included in the VSIX and a user confirmed that it works for him. In Visual Studio, with the extension solution open, double click the .vsixmanifest file Open the "Assets" tab Click "New" Set Type to "Microsoft.VisualStudio.Assembly" Set Source to "A File on FileSystem" Click Browse to set Path to your dll, (don't worry the reference is not added as an absolute path, but added as a relative path or just a strong assembly name) You can leave "Embed in this folder" empty. Click OK Rebuild the solution, and the file should be in the VSIX file now.