Menu
In the Solution Explorer, the vcxproj projects that have references, show a warning symbol on each of the references associated with the project. When the reference is highlighted, the properties panel indicates that the Full Path is:
The Microsoft.VisualStudio.ProjectSystem.References.UnresolvedBuildDependencyProject Reference" reference could not be resolved.
If the "..." box is pressed, the same error messagebox is shown and I am unable to select a new reference. I have tried deleting the reference and adding it again, but the result is the same. When new projects references are added, the result is the same.
All this happens when I compile using the Visual Studio 2008 (v90) toolset. If I compile using the Visual Studio 2015 (v140) toolset, the Full Path to the referenced library is shown correctly.
Some Background:
I upgraded my project from Visual Studio 2008 to Visual Studio 2015. This project contains a mix of managed and unmanaged with type .vcxproj. On this machine, the Visual Studio 2008 redistributable has been installed. This enabled me to compile using the Visual Studio 2008 (v90) toolset. My intention is to first compile my project with my VS2008 settings within VS2015 (For restrictive reasons, I have to use the v90 toolset). Thus, I configured the VC++ directories accordingly. There is no Linker option in the Configuration properties of the linking project. In the properties of the reference, the following configurations are enabled:
456
To fix a broken project reference by correcting the reference path. In Solution Explorer, right-click your project node, and then select Properties. The Project Designer appears. If you're using Visual Basic, select the References page, and then click the Reference Paths button.
You can also right-click the project node and select Add > Project Reference. If you see a References node in Solution Explorer, you can use the right-click context menu to choose Add Reference. Or, right-click the project node and select Add > Reference.
I ran into the similar issue. In my case just closing the solution and opening it again fixed the issue.
166
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
