You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
For me, prior to VS2022 running :make would build the solution. Now under multiple installs of VS2022, running :make only builds the current project. Running :make all does the same
To Reproduce
Steps to reproduce the behavior:
Open a solution in VS2022 containing several projects, where the default project has references to other projects
Make sure the project is clean, so that a full build will occur
Run :make or even :make all
You see the build fail since the referenced projects don't build
NOTE: Pressing F7 or Build/Build Solution will build all dependencies.
Expected behavior
All dependencies should build and default project should then build successfully
Screenshots
N/A
Environment (please complete the following information):
Visual Studio version: 2022 (This has occurred over several updates for me)
VsVim version: 2.10.0.6
Programming Language: C++
Check(Type 'x') any that are installed:
ReSharper
Visual Assist
Additional context
Almost all of the projects I work with are CMake based. The VS solutions are generated using CMake, from the command line. I have confirmed this occurs on a stand alone VS solution as well.
I have been digging through settings trying to determine if this overridable behavior with no luck.
Lame, I know, but I wanted to you to know all installed extensions:
Describe the bug
For me, prior to VS2022 running
:make
would build the solution. Now under multiple installs of VS2022, running:make
only builds the current project. Running:make all
does the sameTo Reproduce
Steps to reproduce the behavior:
:make
or even:make all
NOTE: Pressing
F7
orBuild/Build Solution
will build all dependencies.Expected behavior
All dependencies should build and default project should then build successfully
Screenshots
N/A
Environment (please complete the following information):
Additional context
Almost all of the projects I work with are CMake based. The VS solutions are generated using CMake, from the command line. I have confirmed this occurs on a stand alone VS solution as well.
I have been digging through settings trying to determine if this overridable behavior with no luck.
Lame, I know, but I wanted to you to know all installed extensions:
Add any other context about the problem here.
Note:
The following is written about contributing.
https://github.com/VsVim/VsVim/blob/master/CONTRIBUTING.md
General Keyboard configuration problems are described below.
#2527
The text was updated successfully, but these errors were encountered: