-
When I created the Package Reference Sample Deep Dive I was constrained in the range. Originally I created a longer version with more details. However, I forgot about it... Now, while organizing my publications I have discovered it again and so here I publish the original version. I suggest reading it...
-
In the last months I have been working on deep dives that help developers to understand how VS SDK Sample applications work. About the half of them have already been reviewed and released on MSND Code Gallery. Not only me, but also other VSX guys are working on deep dives on various VS SDK samples. Here...
-
When you create a simple menu command with the VSPackage wizard, it creates code snippets in you package class: // --- Package attributes omitted for clarity public sealed class SimpleCommandPackage : Package { // --- Constructor generated by VSPackage wizard is omitted protected override void Initialize...
-
When you create a simple tool window with the VSPackage wizard, it creates a class derived from ToolWindowPane for you that delegates the user interface responsibility to a user control. The following code is one example: [Guid("4469031d-23e0-483c-8566-ce978f6c9a6f")] public class MyToolWindow...
-
If you used the VSPackage wizard—and I am sure you used it by now—you can discover that it creates a VSPackage.resx file and also a Resources.resx file to store localizable resource information. Attributes used for package registration have indirect references to strings in the VSPackage...
-
When writing LearnVSXNow articles and working on projects I collected a lot of experience related to VSX. Some of them simply do not directly match with the main stream of the articles. I have got many “how-to-dos”, created small but useful code artifacts, found irritating bugs, etc. I decided...