Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, November 24, 2017 8:25 AM
I cloned a project from Git and tried to open the solution in Visual Studio. A lot of projects show yellow exclamation marks on their references, even on ones like "Microsoft.CSharp". Removing and re-adding them doesn't help, the exclamation mark stays and the project doesn't build.
When I start a new project, however, I can add the same references just fine.
What's wrong here?
EDIT: I now reinstalled all Nuget packages, closed and reopened the solutions and the exclamation marks went away on some projects, but not all.
All replies (4)
Tuesday, November 28, 2017 8:52 AM âś…Answered
Hello,
in the meantime, before the answer got posted here, I just deleted and re-created the project, re-adding all source and resource files. If it appears for the next time, I try what you suggested.
Saturday, November 25, 2017 5:20 AM
Hi Windfisch,
Welcome to the MSDN forum.
>> EDIT: I now reinstalled all Nuget packages, closed and reopened the solutions and the exclamation marks went away on some projects, but not all.
Those references in the above projects are the VS system reference or custom DLL? The reference like Microsoft.CSharp that you mentioned before still meet this issue after your installed all NuGet packages.
Did you open this solution in the same VS version that it be created in? Please right click the solution name and clean solution, go to the Store folder and delete the hidden .vs folder to test.
The yellow exclamation mark often caused by the target framework of destination project and the version of references was different, or this reference not existing. Right click the project name, select Unload Project and edit the .csproj file directly in VS. Under one of the <ItemGroup> nodes you will find sub nodes tagged Reference. Ensure that the HintPath node value points to a valid path. Also, double check the nodes SpecificVersion and Private for valid values.
Best regards,
Sara
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]
Tuesday, November 28, 2017 3:17 AM
Hi Windfisch,
Do you have any updates? Please have a try with those suggestion in my previous reply.
If this issue persists, please update it in here and we can help you research it deeply.
Best regards,
Sara
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]
Tuesday, November 28, 2017 8:58 AM
Hi Windfisch,
Thank you for your update and it seems your issue is solved by yourself, so glad to hear that and thank you for your sharing, that will help other community members who meet the same or similar issues.
Could you please mark your reply as the answer? So, we can close this thread, if you have any update issues about the VS IDE in the future, please feel free to let us know, thank you for your understanding.
Best regards,
Sara
MSDN Community Support Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected]