vsix

How to uninstall .vsix Visual Studio Extensions?

℡╲_俬逩灬. 提交于 2019-12-04 07:39:25
问题 I am currently trying to install the XNA Game Studio for Visual Studio Express 2013. And I accidentally ran the .vsix program BEFORE actually installing the XNA framework. After installing it and re-running the .vsix, I get a message error saying that the extension has already been installed. Which is not false. I have tried a lot of things to "delete" the empty extension : going in %LocalAppData%\Microsoft\VisualStudio and trying to find the extension, but finding myself with nothing, for

HWnd of Visual Studio 2010

早过忘川 提交于 2019-12-04 06:41:52
Is there a way to get the HWnd pointer to the top window of Visual Studio 2010 from a VSIX extension? (I would like to change the title of the window). Since there are good chances that your VSIX extension will be running in-process with Visual Studio, you should try this: System.Diagnostics.Process.GetCurrentProcess().MainWindowHandle (Note if you do this too early, you'll get VS Splash screen ...) I'm assuming you want to do this programatically in C#? You'll need to define this P/Invoke inside your class: [DllImport("user32.dll")] static extern int SetWindowText(IntPtr hWnd, string text);

VSIX window - key shortcut to execute ICommand

北慕城南 提交于 2019-12-04 04:19:34
问题 Having a Visual Studio extension (VSIX) project: In Window we got UserControl , which have Button binded to some ICommand . This works perfectly as expected, however I would like to attach a key shortcut (e.g.: CTRL + S ) which would fire the same Command . I have checked several questions, in which I found the most useful this code: <UserControl.InputBindings> <KeyBinding Modifiers="Ctrl" Key="Esc" Command="{Binding SaveCmd}"/> </UserControl.InputBindings> However the Command is never fired

Deploying VSIX using MSI installer

ε祈祈猫儿з 提交于 2019-12-04 02:35:00
Can anyony help me in "How to install VSIX using MSI installer". For msi installer I'm using visual studio Installer setup project. When I use VSIX with extension manager it works fine. I want to have it as a installer(using msi) instead of using enstension manager. or any best wa yto install and unstall VSIX files This isn't a suggested scenario. From MSDN, "You cannot use a Windows Installer package (MSI) to deploy a VSIX package. However, you can extract the contents of a VSIX package for MSI deployment. This document shows how to prepare a project whose default output is a VSIX package for

TFS - VS Extension: Add work item to pending changes via API

六月ゝ 毕业季﹏ 提交于 2019-12-04 02:29:56
问题 I am currently working on a VS extension / add-in and I need to associate work items with the pending changes (without triggering a check-in). After searching for some hours I couldn't find a way to accomplish this via the API. The only way I found to associate a work item to the pending changes is Workspace.CheckIn() which also would trigger the check-in.. Do I miss something? Or is this really not possible? 回答1: I have provided the sample code below, Note that, I have not tried this code,

The “GetDeploymentPathFromVsixManifest” task failed unexpectedly

送分小仙女□ 提交于 2019-12-03 23:45:49
After installation of visual studio 2017 getting his error for VSIX projects ... any suggestion to resolve the issue? Severity Code Description Project File Line Suppression State Error The "GetDeploymentPathFromVsixManifest" task failed unexpectedly. System.Runtime.InteropServices.COMException (0x80070005): ExternalSettingsManager::GetScopePaths failed to initialize PkgDefManager for C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe at Microsoft.VisualStudio.Settings.ExternalSettingsManager.GetScopePaths(String applicationPath, String suffixOrName, String

Add VSIX features to C# Class Library

放肆的年华 提交于 2019-12-03 17:47:54
问题 I have an existing Single-File Generator (housed in a C# Class Library). How do you add the VSIX project-level features to this project? The end goal is to compile my class library project and get a VSIX. (I'm actually answering my own question. This is in relation to SIngle-file generator changes in Visual Studio 2017 - but that question wasn't asking what I'm answering here.) 回答1: First off, your Single-File Generator class needs to have the appropriate class-level attributes: using System

VSIX package build failed without showing the reason (Visual Studio bug)

瘦欲@ 提交于 2019-12-03 17:28:46
问题 I have to enabled diagnostic mode of MSBuild project build output verbosity to see this: 1>Done executing task "EnableExtension" -- FAILED. (TaskId:81) 1>Done building target "DeployVsixExtensionFiles" in project "myextension.csproj" -- FAILED.: (TargetId:93) ... 1>Build FAILED. 1> 1>Time Elapsed 00:00:01.27 ========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ========== My problem is I cannot debug the Visual Studio extension package I'm working on, as the build output says something has

How can I match Visual Studio's theme when creating a VSIX tool window?

流过昼夜 提交于 2019-12-03 16:04:19
I am creating an extension for Visual Studio (2012+) that involves a tool window. I was hoping to style the window identically to match the current theme of Visual Studio. However, I am having a great deal of trouble figuring out how to do it. This post suggests that applying no style at all is all that is required, but that does not match my experience thus far (even creating a default VSIX project in VS2017 and adding a tool window shows a button that I would argue is standard WPF in theme and not VS themed, at least when using the dark VS theme in VS2017). This post asked a similar question

Registering an unpacked VSIX extension via MSI without using devenv /setup

∥☆過路亽.° 提交于 2019-12-03 14:52:31
问题 We have a Visual Studio extension, currently installed with MSI, since we need to perform certain tasks after the installation (ngen, registering certain COM servers, etc). In the end of the installation, we run devenv.exe /setup (more specifically, devenv.exe /setup /nosetupvstemplates to make it a bit faster) to register the extension in Visual Studio 2012 and above (in 2010 this step was not required, since VS2010 would rebuild the extensions cache on every startup). We're currently