- Home /
- Visual Studio /
This site uses cookies for analytics, personalized content and ads. By continuing to browse this site, you agree to this use. Learn more
Get help from our community supported forum
Report an issue
in Visual Studio Installer or Visual Studio
This allows diagnostic information about the program to be included in your report
1. Installer or Visual Studio
2. Report a Problem
3. Type and Submit
Available on Visual Studio 2017, Installer, and newer releases
Would you like to know more?
Solution Shows Missing File Icon
.Net Core Class Library Project (possibly others)
VS Community 2017 v15.2 (26430.15)
Solution Explorer shows the 'missing file' icon next to files that have been edited. Deleting a file from the solution explorer doesn't always delete the actual file on disk.
I was able to reproduce it many times. Create a new .Net Core Class Library Project, edit the default Class1.cs file. Press CTRL+S. The icon changes from a C# file icon to a missing file icon (document with a yellow triangle)
The same thing happened after update VS Community 2017 v15.3 Preview3 to v15.3 Preview4
I'm seeing the same thing in a new-style csproj project.
Thank you for your feedback! For us to investigate this further, could you confirm that the files exhibiting this problem were checked into a Git repository. Also is this a VS upgrade or a new install, and does this problem persist if you run repair?
Yes, I reproduced this during the Scenario Blocker day as well.
And no, there is no source control involved, it is a fresh install of VS 15.3 Preview 4.1 (no build to build upgrade)
No source control involved.
Fresh install, Repair, Update, all have the same problem.
+1, this issue reproes, not sure if this is merely a cosmetic issue, because the code compiles.
Still in 15.3P7.
Maybe this is not an display issue, VS also treat the files as missing, which lead to a lot of other issue, and broken compile.
---
When you rename a file shown as missing in core proj, VS doesn't really rename it(but modify it's content if you chose also rename the classname), but add an extra "Compile Include=" to proj file, which broken the compile with dup item. You can only get the new file after save it manually which the old one still exists.
When you remove a file shown as missing in core proj, instead of really remove it, VS just add an extra "Compile Remove=" to proj file, which block you to add it again.
---
Not sure if it's also cause by this one.
https://developercommunity.visualstudio.com/content/problem/82326/memory-leak-with-microsoftvisualstudioplatformuire.html
Thank you for your feedback! We have fixed the problem in an upcoming release. Thank you for helping us build a better Visual Studio!
@Jacob Viau
When you say upcoming release, like 15.3.4? (Because 15.3.3 just showed up for me about a half hour ago and I still have the problem) or an upcoming preview version? I'm hoping this is not being considered for preview only because I see this a Critical issue/blocker and should have been address way faster than it has been so far.
For those still on the older version - workaround: Add a file of the same name to the folder with the yellow icon. VS will complain that "this file already exists", however, now you will be able to right-click and delete the file permanently.
I'm not sure these are entirely benign - it seems that trying to rename a file which is in this state results in the name changing within Solution Explorer but not on the file system resulting in the two being out of sync. Once the file is in this state, it can't be opened unless the solution is reloaded or the file is renamed manually outside of VS.
In the case of the newer csproj projects, removing those files from the IDE also adds an unnecessary <Compile Remove="..." /> entry in the csproj.
Yeah, the VS project system seems to be confused by the cs files. Like the two above comments mentioned, renaming files causes entries that aren't needed in the csproj and build errors until the csproj is cleaned by hand. I've had to fall back to VS Code for now, as the VS hand-holding kills productivity.
So this is still not fixed in 15.4.0 Preview 1? Wish it to be fixed soon.
It CAN NOT be safely ignored, as it will add unnessery "Compile Remove/Include" to .csproj when rename/remove file, which will break the build with dup include. And may also cause memeryLeak with when use CodeMaid to clean code(up to 50MB/once in some big , 40times to get OOM).
111 People are following this
