vsx,vspackage,visual-studio-sdk
You need to mark your VSPackage as MEF-enabled. Check for details here: Does anyone know how to implement the DynamicEnumProperty type for C++ Project Property rules...
visual-studio,com,envdte,vsix,vspackage
HRESULTs are COM's weakness, error codes don't scale well. At least part of the reason that Java ate Microsoft's lunch. The error code doesn't mean anything more than "could not attach debugger", there isn't any room to also unequivocally explain why it couldn't be attached. Nothing similar to, say, an...
Supported Visual Studio versions are defined in the .vsixmanifest file. If you open it in the design view and select Install Targets, the Version Range for your extensions is currently probably [12.0]. To add support for VS 2015, change it to [12.0, 14.0]. ...
The EnvDTE.Configuration class has a Properties collection that has your desired values: config.Properties.Item("StartProgram").Value config.Properties.Item("StartArguments").Value FWIW, the VSLangProj.dll assembly has a VSLangProj.ProjectConfigurationProperties class with the property names that you can expect in the config.Properties collection....
c#,visual-studio,visual-studio-extensions,vspackage
@ErikEJ's tip worked for me. I had to port the extension project to VS2012 and build it with target set to [11.0,12.0] and this ensured that the VSIX that I generated worked for both VS2012 and VS2013. No errors too!
visual-studio,envdte,vspackage
Commands created from add-ins accept parameters by default. Commands created from packages need to specify the <CommandFlag>AllowParams</CommandFlag> when defining the command in the .vsct file. See: http://msdn.microsoft.com/en-us/library/bb491716.aspx And see also this thread: IOleComandTarget::exec for commands with parameters https://social.msdn.microsoft.com/Forums/en-US/134983e8-049c-40e1-a212-312fa637698b/iolecomandtargetexec-for-commands-with-parameters?forum=vsx Then, it should work, either using dte.ExecuteCommand or...
visual-studio,visual-studio-extensions,vsix,vsx,vspackage
If your project system is based on MPF custom tab pages can be integrated via the ProjectNode class. This class defines the GetConfigurationIndependentPropertyPages and GetConfigurationDependentPropertyPages methods; those are virtual methods and can be implemented by any derived type to return the type-id´s of IPropertyPage implementations. internal class CustomProjectNode : ProjectNode...
The AddIns folder under the Documents folder is not created by default by VS when installed, so you need to create it by hand, as you have done Remove the folder C:\Users\developer\Documents\Visual Studio 2013\AddIns from the Options window, it is not required, the %VSMYDOCUMENTS%\AddIns folder takes care. .AddIn files...
visual-studio-extensions,vsix,vspackage,mpf
I assume, that you´re using MPF to implement the project system for your custom language service. When doing so, you probably have a project root node which is derived from either ProjectNode or HierarchyNode... If so, you could share the root node´s instance with the designer and try to find...
Instead of watching the file changes yourself you can use the built in events provided by Visual Studio: SolutionEvents and ProjectItemEvents. This Stack Overflow post explains how to use them in a vs package.
c#,visual-studio,visual-studio-2013,vspackage
So I solved my problem by this: DTE dtr = (DTE)GetService(typeof(DTE)); string filePath = dte.ActiveDocument.FullName; I also tried DTE2: EnvDTE80.DTE2.dte2; dte2 = (ENVDTE80.DTE2)System.Runtime.InteropServices.Marshal.GetActiveObject("VisualStudio.DTE.12.0"); string filePath = dte2.ActivaDocument.FullName; NOTE: When using DTE I get the current document in the Main Visual Studio (when running the code, another Visual Studio will be...
Enroll the VSIP Program (https://vsipprogram.com). The Basic Level is free. It takes a couple of days to get approval from Microsoft. Click the "Support" link at the bottom of the main page to go to the FAQ section. There is a "How do I get a PLK/SLK for Visual...
visual-studio,visual-studio-2015,visual-studio-extensions,vspackage,visual-studio-templates
In VS 2015, you start with a VSIX project, and then add Items, like for example a VSPackage - see http://blogs.msdn.com/b/visualstudio/archive/2015/05/29/extending-visual-studio-2015.aspx
visual-studio-2010,c#-4.0,vspackage
source.extension.vsixmanifest This is the so-called VSIX manifest file which plays vital role in the discovery and registration mechanism of Visual Studio extensions. FirstLook.vsct The so-called command table file storing the definition of the menus and commands to be merged into the Visual Studio IDE during the registration process. FirstLookPackage.cs Class...
c#,nuget,vspackage,visual-studio-sdk
You'll need to perform the same steps that "NuGet Package Restore" does, adding NuGet.exe, NuGet.config and NuGet.targets correctly to the solution. To see how this changes things, diff two empty solutions where one restores NuGet packages and the other doesn't. To add your custom feed, you can add <packageSources> <add...
visual-studio-2012,vsix,vsx,vspackage
Well, sorry for the confusing documentation, but this walkthrough is not something I would recommend for your case (I'm a dev on VS editor team). As you pointed out you can handle commands much simpler by hooking up command filter via IVsTextViewCreationListener, this is actually way more common and better...
c#,visual-studio-extensions,vspackage,vsct
...what I might be doing wrong. You're essentially trying to bundle two packages (TemplatePackPackage & MenuOptionsPackage) into a single package, which messes up your .pkgdef file, which I believe is the cause of your issue. If you comment out the MenuOptionsPackage class, then you should see only one menu...
Please check within the .vsct file. An example is here: https://msdn.microsoft.com/en-us/library/bb166492.aspx
c#,wpf,visual-studio,visual-studio-2013,vspackage
Well I just found a few things - so I'm gonna answer my own question so that other people having the same problem may take advantage of it: Set up your extension as in this tutorial but check "Tool Window" Create a new UserControl for the ToolWindow "ToolWindow2Control" and copy...