Visualstudio-docs: followed instructions, but got errors

[screig]

Severity Code Description Project File Line Suppression State
Error Undefined 'guid' attribute 'guidTestCommandPackageCmdSet' in a

element VSIXProject1 C:\LocalFolder_CODE\VSIXProject1\VSIXProject1\TestommandPackage.vsct 35
Error Undefined 'id' attribute 'TopLevelMenu' in a element VSIXProject1 C:\LocalFolder_CODE\VSIXProject1\VSIXProject1\TestommandPackage.vsct 35
Error Undefined 'Parent/@guid' attribute 'guidTestCommandPackageCmdSet' in a element VSIXProject1 C:\LocalFolder_CODE\VSIXProject1\VSIXProject1\TestommandPackage.vsct 52
Error Undefined 'Parent/@id' attribute 'TopLevelMenu' in a element VSIXProject1 C:\LocalFolder_CODE\VSIXProject1\VSIXProject1\TestommandPackage.vsct 52

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 1b4a51b4-fb22-6621-8e50-915c95973701
• Version Independent ID: b8800c03-0708-eca0-e749-ea01879d5cc6
• Content
• Content Source
• Service: unspecified

[gregvanl]

Hi @screig Can you see if the change proposed in https://github.com/MicrosoftDocs/visualstudio-docs/pull/576 fixes your build error? If so, I'll merge that PR. Thanks

[screig]

sorry those instructions make no sense to me.

First off the template produces

    <!-- This is the guid used to group the menu commands together -->
    <GuidSymbol name="guidTestommandPackageCmdSet" value="{c72d48db-baf4-453d-9e51-573d3c25b6da}">
      <IDSymbol name="MyMenuGroup" value="0x1020" />
      <IDSymbol name="TestommandId" value="0x0100" />
    </GuidSymbol>

the original web page says I should add a line like this

<IDSymbol name="TopLevelMenu" value="0x1021"/>

From what I can gather, the new instructions call the same thing four different names:

• TopLevelMenu, in the first paragraph.
• guidTopLevelMenuCmdSet in the second paragraph
• cmdidTestSubCommand in first code block.
• MyMenuGroup in the second code block.

Makes zero sense, cant follow any of it.

[TuckermanRav]

I concur that the instructions are not correct. Getting the following errors while attempting to run in debug.

Severity Code Description Project File Line Suppression State
Error Undefined 'guid' attribute 'guidTestCommandPackageCmdSet' in a

element DensityExtension C:\Users\Administrator\source\repos\VSIXProject1\DensityExtension\FirstCommandPackage.vsct 35
Error Undefined 'id' attribute 'TopLevelMenu' in a element DensityExtension C:\Users\Administrator\source\repos\VSIXProject1\DensityExtension\FirstCommandPackage.vsct 35
Error Undefined 'Parent/@id' attribute 'TopLevelMenu' in a element DensityExtension C:\Users\Administrator\source\repos\VSIXProject1\DensityExtension\FirstCommandPackage.vsct 51

[screig]

Any ideas? Instructions that do work?

[ranjeesh]

I worked for me.
Ensure that you use the same GUId for couple of elements as shown below. I used "guidTFMIPackageCmdSet" in the below example.

[se7ensoft]

Doesn't work. Followed above instructions to a T and no menu item appeared in the experimental instance.

[javierdlg]

What version of VS did you build this on Se7ensoft?

[se7ensoft]

VS2017, but not certain what build it was when I posted.

[DigitalMystery]

Thought I had an issue at first which is why I landed here, but the walk-thru seems to be fine (at least as of now) for Visual Studio 2017. I had placed step one in the wrong set of GuidSumbols which thru everything off. Thanks!

[tanmay-18]

I worked for me.
Ensure that you use the same GUId for couple of elements as shown below. I used "guidTFMIPackageCmdSet" in the below example.

Thanks! It worked for me as well.

[DeanMauro]

This SO answer provides a clearer walkthrough

https://stackoverflow.com/questions/57146424/how-can-i-nest-tool-menu-buttons-for-a-vs-extension/57215504#57215504

[leslierichardson95]

Thanks for submitting your feedback and we apologize for the delayed response. Due to current resourcing and substantial extensibility changes we are currently working on that will result in significant, structural doc changes, we are closing this lower priority issue. We will return to this issue on a later date and address it based on it's relevance after those extensive extensibility updates are made. Feel free to comment here as necessary.