vsix

问题 I'm currently implementing a vsix extension tool window which will soon need a database connection string for querying some data to display to the developer in the tool window. I'd like to make this connection string configurable by the developer. As the developer is unlikely to change the config settings often a file would be sufficient. Is it possible to just use an app.config file in the same folder as the sln file and if so must I use some custom configuration settings to wrap the file?

问题 Previous question: Visual Studio Extension: How to disable native command? I build an extension that manages correctly Git Modules and, to do so, I have a folder in the solution called SubModules. I managed to add my context menu to the solution file and to the project files, but I would like to disable some native commands when right-clicking on my SubModules folder (i.e. Remove, Add). I now know how to disable the native commands I want, but to do so, I need to get the "path" of the

问题 I'm creating a VISX project. It runs normally, but after I update all it's nuget packages, it start to show errors when I try to run it in the Visual Studio Experimental Instance. I tried to revert the packages, but it seems that some packages versions are no longer available for download. The main reason is that the VISX can't load the Microsoft.VisualStudio.Threading assembly after the dependecies are updated. I tried adding the assembly to the package's Assets too. The VISX can load it now

问题 I would like to disable parts of my extension's tool window if it is opened without a solution loaded, and need a way to detect this. I know about the DTE events that are fired when a solution is opened/closed, is there perhaps a similar event for when the IDE itself has finished loading? 回答1: I found my answer while writing the question, but I thought I may as well still submit in case anyone else is looking for this in future with similar search terms to me. EnvDTE.Solution.IsOpen 来源： https

问题 I have installed the VS 2010 SDK but I still don't have the VSIX project type. This system has never had any beta bits on it. Any ideas? 回答1: OK so I'm a dummy... you have to target .NET 4 to see that project type. 回答2: Yes, but first download and install the SDK : http://www.microsoft.com/downloads/en/details.aspx?FamilyID=47305cf4-2bea-43c0-91cd-1b853602dcc5&displaylang=en 来源： https://stackoverflow.com/questions/2766566/cant-find-vsix-project-type-in-vs-2010

问题 I created a new VSIX project and added a new item -> Extensibility -> Custom Tool Window Then I tried to build, but it gave an error: 1>------ Build started: Project: JSBQ, Configuration: Debug Any CPU ------ 1>E:\JSBQ\packages\Microsoft.VSSDK.BuildTools.14.2.25123\tools\VSSDK\Microsoft.VsSDK.Common.targets(126,5): error MSB4018: The "VSCTCompiler" task failed unexpectedly. 1>E:\JSBQ\packages\Microsoft.VSSDK.BuildTools.14.2.25123\tools\VSSDK\Microsoft.VsSDK.Common.targets(126,5): error

问题 I'm interested in getting a Project or ProjectItem (as examples, not limited to those two) for the current selection where only a single item is selected. Most people seem to be using IVsMonitorSelection to get an IVSHierarchy and then use the following to get the object for the selected item (in case of a single item being selected): var monitorSelection = (IVsMonitorSelection) Package.GetGlobalService(typeof(IVsMonitorSelection)); IntPtr hierarchyPointer, selectionContainerPointer; uint

问题 I have a VSIX extension that I created which shows up in Visual Studio 2010 and works as designed. However I am attempting to build some Visual Studio automation which relies on this Extension and although its present in the project where I am building my automation package, when I run the package project, the visual studio experimental solution loads no problem, however when I look within the Extension Manager I do not see my registered Extension (even though it shows up within my Visual

问题 I'm getting the error: Unable to find an entry point named '?' in DLL 'PkgdefMgmt.dll' when installing a Visual Studio Extension (vsix) for VS 2017. This extension was developed in VS2015, so i thought i'd upgrade, recompile, and reinstall it, but I get the same error. This is a new laptop with Windows 10 and VS 2017. Any ideas to fix? Here's the complete install log: 5/9/2017 10:23:21 AM - Microsoft VSIX Installer 5/9/2017 10:23:21 AM - ------------------------------------------- 5/9/2017 10

问题 Visual Studio 2017 seems to have changed a lot of things in the extensibility area https://docs.microsoft.com/en-us/visualstudio/extensibility/breaking-changes-2017 The previous recommendations regarding installing a VSIX from an MSI now seem obsolete (Deploying VSIX using MSI installer), but there seems to no information about how to do it now. The VS2017 FAQ implies the VSIX installer can (should?) be kicked off manually, is this the recommender approach now? vsixinstaller.exe /q