- Home /
- Visual Studio /
cykol2002
reported
Jul 17, 2017 at 04:34 AM
Solution by
Stephen J Naughton
·
Aug 29, 2017 at 11:57 PM
I have also noticed that is you rename a file after the missing file notification and restart VS you end up with two files the old file and one with the rename.
Solution by
John Catenzaro - MSFT [MSFT]
·
Oct 09, 2017 at 09:00 PM
This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://www.visualstudio.com/vs/ Thanks to everyone who provided feedback, votes and solutions for this problem.
Solution by
John Catenzaro - MSFT [MSFT]
·
Oct 09, 2017 at 09:02 PM
This issue has been fixed and is now available in our latest update. You can download the update via the in-product notification or from here: https://www.visualstudio.com/vs/ Thanks to everyone who provided feedback, votes and solutions for this problem.
Solution by
Andrew Casey [MSFT]
·
Aug 24, 2017 at 05:22 PM
In the some Windows Insiders builds, saving files in .NET Core, UWP, and Shared projects may result in yield/warning signs next to the changed files.
The yield/warning signs are benign and may be safely ignored. Reloading the solution will remove the yield/warning signs.
Source: https://www.visualstudio.com/en-us/news/releasenotes/vs2017-knownissues
111 People are following this
Blend 2017 Framework 4.7 Behaviors Not Initialized
1
Solution
Can not add new file to filter in C++ shared project
1
Solution
Visual Studio 2017 - Windows form is not installed with installation
2
Solution
Installazione Visual Studio Update 15.3.0
1
Solution
[C++]Incorrect Automatic brace completion
1
Solution
Typo in Visual Studio Community 2017 UnitTest Project
2
Solution
Feedback window won't close
1
Solution