BUG: Extension Manager `Export Extensions` feature won't function (sporadically) in VS 2022 17.10.5

[astrohart]

Figure 1. Animated GIF of the issue.

I am utilizing Microsoft Visual Studio 2022 Enterprise Edition v17.10.5 with the extension Extension Manager 2022 installed, as obtained by clicking the download button in the web page that is linked.

Steps to Reproduce

1. Install Microsoft Visual Studio 2022 Enterprise Edition v17.10.5.
2. Install the Extension Manager 2022 extension from the website linked.
3. Open Visual Studio.
4. Click the Extensions menu on the menu bar.
5. Point to import and Export Extensions, and then click Export Extensions.
6. The message box shown in Figure 1 appears.

NOTE: While composing this issue, I tried to invoke the Export Extensions command again, and it popped up the Export Extensions dialog box. How weird. I am befuddled by this.

I respectfully suggest that this issue still be created, and the situation monitored for a repeat occurrence. If it recurs again, I will then add a new post to this issue with the Activity Logs (produced by running devenv.exe with the /Log switch).

For now, I ask that this issue be filed so this can be monitored and tracked. The animated GIF in Figure 1 was recorded just moments before it started working.

[astrohart]

Figure 1. Error message dialog box.

At 14:11 hours MDT on 08/02/2024, the message above was encountered again when following the reproduction steps listed above. This was done after exiting and then restarting Visual Studio.

The ActivityLog.xml file produced by Visual Studio is attached.
ActivityLog.txt
File 1. The Visual Studio activity log.

[loop8ack]

Thank you for the detailed information.
Unfortunately, I can't find anything helpful in the log and I can't reproduce it locally either.

But I can implement more detailed logging and we may find out more then.

However, I have a lot to do at work at the moment, so I can't estimate when this will be ready.

[astrohart]

@loop8ack as a contributor I can potentially look into this as well. I also have been severely constrained on my own time as well. Remember, I am still working on that massive PR to refactor for robustness, fault-tolerance, and best practices! Still a work in progress though. In the intervening years, I underwent a career relaunch and cross-country move and the dust is still settling.

When I file issues, partly it is for my own reference as a contributor as well.

BTW - just a FYI - the issue is only sporadic. When I click the same menu item again, the issue does not appear. It comes back randomly and unpredictably.