- This topic has 3 replies, 2 voices, and was last updated 3 weeks, 2 days ago by
.
-
Posts
-
40+ years software experience but new to VisualGDB. Just installed v6.1R3(build 5547) on VS2026. I have .Net, the Universal C Runtime installed and MSVC v143
I created a new project and went for the LED Blink example on STM32F091RC.
The project gives the following error:
The imported project “C:\Program Files\Microsoft Visual Studio\18\Professional\MSBuild\Microsoft\VC\v160\Microsoft.cpp.targets” was not found. Confirm that the expression in the Import declaration “$(_VCTargetsPathForToolset)\Microsoft.cpp.targets”, which evaluated to “C:\Program Files\Microsoft Visual Studio\18\Professional\MSBuild\Microsoft\VC\v160\\Microsoft.cpp.targets”, is correct, and that the file exists on disk.
..the file it wants is actually in the …VC\180 folder on this PC so it appears to be looking in the wrong place.
If I close and re-open the project, I get a dialog with ‘Missing MSBuild properties’, suggesting VisualGDB is an older version. I have the latest installed (
When I press resolve I get the following exception:
Encountered 1 errors while trying to update project(s):
—————— System.ArgumentException ——————
System.ArgumentException: Invalid ruleset name: ConfigurationGeneral
at rj.SetCustomPropertyValue(String b, String a, String c)
at mf1.e(IVCConfiguration b, ToolchainKey a)
at rp.h(j43 c, IProjectEditContext d, Boolean b, KeilComponentTree a, String[] e)
at ss.t()
trace=[rj.SetCustomPropertyValue:41, mf1.e:0, rp.h:1353, ss.t:938]Any ideas?
Thx, Jonny
Hi,
This means that the MSBuild files are missing from the VS installation. You can confirm it by trying to create a regular Win32 C++ project (non-VisualGDB) – it should be either missing, or would run into the same problem.
Installing Visual C++ project support via the VS installer should fix it. You can also use CMake-based projects instead, as they do not rely on MSBuild.
Inside C:\Program Files\Microsoft Visual Studio\18\Professional\MSBuild\Microsoft\VC\v160 I found a VisualGDB folder with the targets file.
I copied this to ...VC\v180 and everything works.
Hi,
It can be a glitch related to first installing an early preview of VS2026, and then upgrading it to the latest stable one. VisualGDB installer finds the latest MSBuild version with a non-empty Platforms subdirectory, and copies its platform files alongside the default platforms. This normally matches the Visual Studio’s default mechanism for finding the platform files.
It is difficult to say why it would look for the files in a different location this time, but copying/symlinking the VisualGDB platform to a different MSBuild version should work just fine.
If anyone else encounters the same problem, feel free to post here, and we will investigate it further.
- You must be logged in to reply to this topic.