- This topic has 6 replies, 3 voices, and was last updated 2 years, 3 months ago by
.
-
Posts
-
VS: 2020, V17.3.1 Community
Hi,
In VS, if I do:
Tools | VisualGDB | Manage VisualGDB Packages
I get a cache error popup as per the enclosed screenshot, appears it can’t find some sort of file(?) I noticed this 2 days ago, but then restarted VS, and the popup went away so I didn’t think it was a problem. I rebooted my PC today, and another VS update to 17.3.1, and get the same error, but does go away if close/restart VS. I noticed this before and after updating VisualGDB as per my post 2 days ago. This first started showing up after I updated VS to v17.3.0 two days ago. Is there a way to get rid of this popup?VisualGDB version: 5.6.107.4680
—————— System.IO.FileNotFoundException ——————
System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at xt.a(DTE a, VisualGDBPackageCommon c, StringBuilder b)
at xt.f(DTE b, VisualGDBPackageCommon a, n31[] c)
trace=[System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal:-1, xt.a:137, xt.f:391]Thanks
Ok, I restarted my PC again, and going into “Manage VisualGDB Packages” no longer gives me the popup err. Appears something with the last two Visual Studio updates (v17.3.0 and v17.3.1) gives this error the first time going into “Manage VisualGDB Packages” but doesn’t appear after that.
Hi,
We have confirmed the issue. Updating from VS17.2 or later to 17.3 reset the fonts/colors cache in a way preventing VisualGDB from resetting it using the regular API. This happened only the first time Visual Studio is started after the update. On subsequent launches, the cache was consistent, and even forcibly resetting it worked as before.
Could you please clarify if the problem happened once (i.e. updating from a particular old VS version) or after each VS update (e.g. 17.2->17.3 and 17.3->17.3.1)? If every update triggers the message, we can hide it by default. If it only happens once after a specific VS update, it is safe to ignore.
Hi,
The popup only occurs once going into “Manage VisualGDB Packages” the first time after the VS update. I’ll try to summarize:
– updating to 17.2.? (sorry I don’t remember what sub version I had) never showed the popup
– 17.2.? to 17.3.0 popped the msg once, this was 2 days ago. I restarted VS and the popup went away, so I thought some weird glitch and didn’t report it. Subsequent selection of “Manage VisualGDB Packages” no longer popped up the msg
– 17.3.0 to 17.3.1 popped up once again, but subsequent selection of “Manage VisualGDB Packages” does not pop up the msgThanks
Thanks for confirming this. It looks like the VS installer is now resetting the VS cache after each update (likely to work around the same type of problem that VisualGDB was working around), and that it temporarily makes the regular reset API return an error. We have updated VisualGDB to silently log any cache resetting issues instead of showing the error popup: VisualGDB-5.6.107.4689.msi. If you encounter any cache-related issues, you can view the log via View->Other Windows->VisualGDB Diagnostics Console.
- You must be logged in to reply to this topic.