Skip to content

Conversation

networkfusion
Copy link
Member

Description

Motivation and Context

Currently the icons sometimes "disappear" when the VS2022 nanoFw extension is updated.
This is a potential solution is outlined in "https://stackoverflow.com/questions/58311920/visual-studio-vsix-extension-not-showing-in-tools-menu" (although there are possibily other fixes).
A solution like this "should" be tried before escalation to the VS team, as although there is a workaround (via: devenv /updateConfiguration) it is annoying.

How Has This Been Tested?

I am currently unsure how to test (easily) but, for future could (possibily) use https://github.com/josetr/VsixTesting

Screenshots

Types of changes

  • Improvement (non-breaking change that improves a feature, code or algorithm)
  • Bug fix (non-breaking change which fixes an issue with code or algorithm)
  • New feature (non-breaking change which adds functionality to code)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Config and build (change in the configuration and build system, has no impact on code or features)
  • Dependencies (update dependencies and changes associated, has no impact on code or features)
  • Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
  • Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

  • My code follows the code style of this project (only if there are changes in source code).
  • My changes require an update to the documentation (there are changes that require the docs website to be updated).
  • I have updated the documentation accordingly (the changes require an update on the docs in this repo).
  • I have read the CONTRIBUTING document.
  • I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
  • I have added new tests to cover my changes.

@nfbot nfbot added the Type: bug label Apr 6, 2022
@networkfusion
Copy link
Member Author

This is the other "tip" I can find...
image

@josesimoes
Copy link
Member

Maybe you can try grab the vsix from the artifacts in the pipeline to try it.

I'm a bit surprised with the MainPackage.tt dependency... we don't have any package/file/class build artifact with that name, so I wonder were that's coming from. And I did a quick search on github and no hits came up with that name.

@networkfusion
Copy link
Member Author

Using the pipeline build https://dev.azure.com/nanoframework/Visual-Studio-extension/_build/results?buildId=31734&view=artifacts&pathAsName=false&type=publishedArtifacts "seems" to have the same issue... so this fix is probably invalid 😒
image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants