Open vLGrok opened 2 years ago
Thanks for reporting this issue, It is a known issue.
Could you please try to clear VS Cache and see if the images comes back? You can do this through opening command line under Visual Studio's Tool menu and run the following command:
devenv.exe /clearCache
We need to reach back out to the VS extensibility team to figure this out. @zewditu Can you take care of this?
@zewditu Is this finally resolved?
@JakeRadMSFT to try Fully qualified namespace registration before reaching out to partners.
Still running into this issue with the latest version from the private feed.
Hypothesis: The source you install from is the issue. If you install from the private feed it's an issue but if you install from the marketplace it's not.
@beccamc
I think we're okay to close this issue. It only appears to happen with builds from the private gallery. After installing the latest release from the Marketplace, the images are there.
@luisquintanilla Jake told me today that he has a consistent repo without the private gallery.
@JakeRadMSFT to try to repro / fix next week
I was unable to repro when updating to the latest version: 16.13.10.2245901
Managed to get this to repro today in a dev build... experimenting with fix.
@JakeRadMSFT to provide next steps. Moving to December 2022 milestone.
We don't have a consistent repro. Closing for now and will wait for feedback.
The bug has been fixed on the latest main build 17.14.4.2315802.
The bug is repro again on the latest main build 17.14.4.2316301.
The bug is not repro on the latest main build 17.14.4.2316401
The bug is repro again on the latest main build 17.14.4.2316701.
I still see this issue in VS Professional 17.8.3. Is it supposed to be resolved or is it still an open issue?
System Information (please complete the following information):
Describe the bug
To Reproduce Steps to reproduce the behavior:
Expected behavior Expected the tiles to have images along with the text below the images.
Screenshots
Expected:
Actual:
Additional context As far as I know, no functionality is affected. I haven't continued past this step but will. Just wanted to report this before moving on.