Command not showing in experimental instance

[asherber]

I'm just starting to play around with extensions, but I can't get off the ground.

I've got VS2022 Community installed with extensibility workload. I went to the cookbook site and installed Extensibility Essentials 2022. I started a new solution and added a "VSIX Project w/Command (Community)" project. The cookbook has info about modifying the project, but as I understand it, even without modifying I should be able to F5 on the new project and see an entry in the Tools menu of the experimental instance that says "My Command", and when I click that item I should get a dialog that says "Button clicked". But the menu entry is not showing up for me.

What am I missing?

[moon6969]

I've just done several such tests today on 2 PCs - for me the "VSIX Project w/Command (Community)" project does just F5 out of the box.

Does the extension appear in the Extensions → Manage Extensions dialog (in the Experimental Instance when debugging)?

Have you tried "Reset the Visual Studio 2022 Experimental Instance" (in the Start Menu)?

Since you posted there have been updates to the 'Extensibility Essentials' and VSSDK build NuGet packages, so it may be worth updating them in your test solution...
https://www.vsixcookbook.com/getting-started/get-the-tools.html

[asherber]

@ErikEJ Yes, AnyCPU

@moon6969 I'm not ready to pave my machine on account of this.

I spun up a new AWS EC2 and installed VS, and the VSIX Community project does work out of the box with F5 (as I would expect).

However, I'm having this issue on both of my machines -- a Dell desktop and an HP laptop, both up to date with Windows and VS. I do keep them similarly configured, so at this point I'm thinking it's either some VS setting that I have or something else that I have running on both machines. Is there some way to have the experimental instance launch with the /log switch?

[StevenRasmussen]

@asherber - I never saw if you confirmed that you can see the extension in the Extensions -> Manage Extensions dialog? If so, is it enabled?
Also, you should be able to run the experimential instance by putting the /log switch at the end of the Startup external program: in the settings of the VSIX project:

[asherber]

@StevenRasmussen The extension does not show up in Extensions -> Manage Extensions

VS doesn't like it if you add command switches in that spot. I tried adding it in the Command line arguments edit box, but VS deleted it as soon as I hit F5.

[StevenRasmussen]

Have you checked the following in the properties for the project:

[asherber]

@StevenRasmussen Yup. All I'm basically doing right now is starting a new "VSIX Project w/Command (Community)" and hitting F5, expecting the "My Command" item to show up in the Tools menu. It works for me on a clean EC2, and presumably is working fine for lots of other people, but it's not working on either of my two (similarly configured) computers.