This line which appears twice in .vcxproj files:
<Import Project="$(SolutionDir)\$(SolutionName).props" />
Seems to be causing this QT error when loading the solution in VS2019:
ProjectName.vcxproj: background build ERROR: The imported project "C:\Users\...\ProjectFolder\.props" was not found. Confirm that the expression in the Import declaration "C:\Users\...\ProjectFolder\.props" is correct, and that the file exists on disk. C:\Users\...\ProjectFolder\ProjectName.vcxproj
The first issue: I noticed the error has two backslashes on the second directory. I read on a Microsoft Docs that $(ProjectDir) returns a trailing backslash, so I removed the one in the Import Declaration which left it with only one backslash.
The main issue: After removing the backslash, it appears that the $(SolutionName) macro is returning an empty/null string, causing QT to try and load ".props". Whats interesting is that if you type ANY text to the left OR right of the macro (in the import declaration), it instead returns the appropriate solution name as intended, but with the additional text messing up the path. Remove that text and reload VS and it goes back to returning an empty string. For example:
$(SolutionDir)$(SolutionName)asdf.props results in "C:\Users\...\ProjectFolder\ProjectNameasdf.props was not found"
and
$(SolutionDir)asdf$(SolutionName).props results in "C:\Users\...\ProjectFolder\asdfProjectName.props was not found"
but
$(SolutionDir)$(SolutionName).props results in "C:\Users\...\ProjectFolder\.props was not found"
In the Property Pages > Executable Directories > Macros window everything is defined as it should be. I've ran out of ideas
What I've tried:
- Using
$(ProjectDir)\$(ProjectName)(same error) - Using
$(MSBuildProjectDirectory)\$(SolutionName)(same error) - Using
..\..\to point it to the props file (same error) - Adding
Condition="Exists('$(SolutionDir)\$(SolutionName).props')"into the import tag (changed the error to "ProjectName.vcxproj background build FAILED!") - Removing the import declaration completely
- Read and tried every existing StackOverflow post even remotely related
Other info:
- Project was transferred from VS 2017 to 2019
- This project involves multiple solutions nested into one parent solution
- Each solution under the parent solution throws this error two times, I believe it's once for each Import Declaration which involves
$(SolutionDir)$(SolutionName) - As mentioned this project involves QT
- Each child solution points to the one parent solution's .props file
- The project continues after these errors and functions normally without further error. However I am concerned it might cause issues later and want to clear it up for completeness sake.