I have some old non-working menu giving me COM error in visual studio 2017 right click menu. I want to get rid of this menu. but not sure how to. This is pointing to EditorContextMenus.CodeWindow.LocateinSolutionExplorer command. This command is dead now. How to clean up this menu?
Related
I have installed JetBrains' dotCover application (not the full ReSharper, but it still manages to get its big, meaty claws on my keybindings and such), and the Navigate > option in the context menu is now unavailable.
I have configured ReSharper's settings as follows, and have tried other combinations as well:
I have also tried resetting my keyboard shortcuts by going to Tools > Options > Environment > Keyboard and clicking Reset, and Navigate is still unavailable.
All I want is the test runner functionality of dotCover, with no other changes to my stock IDE settings. Does anyone know how I can accomplish this, or at the very list, how I can get Navigate back?
This Navigate menu item comes from ReSharper, not from Visual Studio. All Visual Studio navigation-related menu items appear above Navigate item on your screenshot. You might disable dotCover in Tools | Options | ReSharper Ultimate | Suspend now and check that Navigate menu item will disappear from the context menu. I've filed a new request to fix this.
I downloaded the visual studio 2017 with c# and xamarin when it gave me a lot of choices at installation time, now I want to install c++ also in existing vs2017. How can I do that? I don't want to install the whole visual studio again.
1.Go to Control panel
2.In the Add or Remove Programs dialog box, select the product you want to repair and then click Change/Remove
3.In the Setup wizard, click Next
4.Click Repair
5.Then Modify it by selecting C++ to add it.
Note : This work in Window OS only
Alternative answer (less searching needed) : Visual Studio 2017 also adds the " Visual Studio Installer" directly to the Windows Start Menu (this is the same executable used by #John Joe's answer).
I can't find the "Pin to Source" functionality in Visual Studio 2017, was it removed?
I Googled it and nothing til now.
This option is also missing for me in VS 2017. I am however able to pin variables by hovering over the variable and clicking the pin icon on the far right of the tooltip that pops up. This accomplishes the same thing for now.
I had the same issue with VS2019. I tried importing a backup setting from prior year (Tool > Import and Export), and turns out my old hotkey for this command still works -- even though I still can't see the Pin To Source in the hotkey mapping window. You can try this work around.
I tried repairing the installation and reinstalling everything from scratch but nothing seems to fix this problem. This problem also exists when I try to create a Win32 Application in Visual C++ as well as Visual Studio 2013.
Clicking finish and cancel seem to do nothing while the only button that works is the red X on the top right hand corner.
http://i.imgur.com/fHZZ4th.png
I have heard good things about this IDE but I can't seem to create a new project. Please help!
I have a problem for my visual studio 2010. When I click start debugging button and it's start debugging.
It seems that there is no error "i just create one "button" on it "
But it will show Unable to start program 'c:\users\.....\xx.dll'
Does someone now how to solve it?
The second question is: when I click left button to see the "Button" source code,
why it will show all this project code? Should I revise some setting?
Visual studio will not run a .dll by itself. does your solution have an .exe project? if so, right click it and select "Set as Startup Project". if not you will need to create one, and instruct it to load the forms within your dll.
as for left clicking the button, I'm not quite sure what you are describing. can you post a picture?
In earlier versions of MSVC while running .dll, will get a dialog asking path for .exe file
But in MSVC 2010 and above there is no such option. To fix this
Right click on your dll project
Properties
Configuration Properties > Debugging. Here, in Command -> add path to your exe.
Add command arguments, if any.
You are good to go!