Enable/Disable State?

[nurbles]

I have several extensions that are normally disabled -- except for special situations. I cannot see anything in the import/export features of this nifty extension that show (or restore on import) the enable/disable state for each extension.

For me, I find export/import most useful when Microsoft asks me to "Repair" Visual Studio as part of testing a bug I reported. Since "Repair" means "lose all local settings, extensions and customizations" I need a quick way to get all of the extensions I depend on back in play quickly as I already waste enough time debugging and working around Microsoft's problems.

Edit: I landed here by clicking "More Info" for Extension Manager 2019 and I'm stuck with VS2019 until some critical bugs are fixed in VS2022, It looks like EM2019 is not being updated, so I guess this is mostly useless for me. But the idea may help others, if it is possible. In fact, an option to download all of the appropriate .vsix files into a folder and also create a .CMD (or powershell, if you must) script to automatically install all of them would be AMAZING -- especially since, as it stands, we need to remember which extension to manually install so that we may import what we previously exported.

[astrohart]

I think that this is not really that big of an issue...if I have extensions installed, and they are disabled, should not this tool just not export them at all?

[mmmbvia]

When you have a Work account where you are signed in to your works email, for the license, plus you also have a private community account at home, then you need a way to sync between Work and Home

It is critical to be able to sync both enabled and disabled. I have 32 disabled extentions, that i need to quicly enable when i need them.. and a lot more that is enabled. My brain is not able to remember the names, so it will be a big help if it can export both the enabled and disabled, and there current state. Please 😀

@astrohart

[loop8ack]

I'm thinking about exporting the enabled state as well and enabling or disabling already installed extensions on import, that should solve the problem?

However, I can currently only provide such a function for Visual Studio 2022, is that a problem?

Also, I can't say when I'll get around to it at the moment.

@mmmbvia

[martinandersen3d]

Visual Studio 2022 is perfect!
Thanks 😀