Y
yuanliu1
Guest
The "build solution" menu is right above the "rebuild solution" menu.
Once a while, I accidentally clicked the "rebuild solution" and waste a good half an hour for the mistake.
I understand there are a good 1000 reasons to use a hotkey, but VS kept changes them, and let's put it aside. I could not train my whole team to reset the hotkey everytime we update the VS.
I understand there are a good 1000 reasons not to give a warning before cleaning up the whole solutions, let's put it aside.
I want to move "rebuild solution" away from the "build solution"
I followed the instruction online, "go to Tools->Customize-><g class="gr_ gr_467 gr-alert gr_gramm gr_inline_cards gr_disable_anim_appear Punctuation only-del replaceWithoutSep" data-gr-id="467" id="467">Commands,</g> hit the Context Menus radio button, and then hit the combo box and select "Project and Solutions | Project". That brought up the project context menu, where Build and Rebuild were together. I moved down Rebuild" I followed this instruction on VS 2017, but nothing happens.
Is there any other tricks to solve this problem?
Continue reading...
Once a while, I accidentally clicked the "rebuild solution" and waste a good half an hour for the mistake.
I understand there are a good 1000 reasons to use a hotkey, but VS kept changes them, and let's put it aside. I could not train my whole team to reset the hotkey everytime we update the VS.
I understand there are a good 1000 reasons not to give a warning before cleaning up the whole solutions, let's put it aside.
I want to move "rebuild solution" away from the "build solution"
I followed the instruction online, "go to Tools->Customize-><g class="gr_ gr_467 gr-alert gr_gramm gr_inline_cards gr_disable_anim_appear Punctuation only-del replaceWithoutSep" data-gr-id="467" id="467">Commands,</g> hit the Context Menus radio button, and then hit the combo box and select "Project and Solutions | Project". That brought up the project context menu, where Build and Rebuild were together. I moved down Rebuild" I followed this instruction on VS 2017, but nothing happens.
Is there any other tricks to solve this problem?
Continue reading...