none
Recovering from a system failure - how might Visual Studio be affected? RRS feed

  • Question

  • Yesterday while working on some code in VS 2019, my Windows 10 Enterprise machine blue screened. Normally it comes back up with no problems. Not this time. This time when I logged in, the screen went black and that was it. I contacted our tech support and they applied patches and upgrading my machine from Windows 10 1803 to Windows 10 1903. (Our corporate IT manages this so everyone else is still on 1803.) I lost most of yesterday, due to this whatever-it-was failure. But today, at least for now, things seem to be working fine.

    However, what I want to do is commit to source control what I was working on. First thing I did was get into VS 2019 and brought up the project I was working on. In the Output window I was presented with this message:

    [Failure] Could not find file 'C:\Users\Rod.Falanga\AppData\Local\Temp\.NETFramework,Version=v4.5.2.AssemblyAttributes.cs'.

    What I want to know is, how serious is this problem?


    Rod

    Tuesday, August 20, 2019 2:27 PM

Answers

  • Hi Rod,

    Thank you for posting here.

    As far as I know, this issue is harmless. It might appear after changing temporary folder or the path of the directory is modified which might cause the specified files not be found.

    According to your description, the temp folder might be changed when system has been updated from 1803 to 1903. You could try steps below to fix it.

    1. Exit Visual Studio and delete the hidden .vs folder, then restart VS and rebuild the solution to check whether this issue persists.

    2. Build -> Clean Solution, Build -> Rebuild Solution, File -> Close Solution, Open the solution. (Usually Rebuild solved this issue)

    Also, I have found similar issue, you could refer to this link, thought this issue is old and uses VS2017, the mentioned solutions or workarounds might help you.

    Any feedback will be expected.

    Best Regards,

    Dylan


    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 MSDNFSF@microsoft.com

    • Marked as answer by Rod at Work Wednesday, August 21, 2019 3:45 PM
    Wednesday, August 21, 2019 4:35 AM