It's about as clear as mud, but I think as clear as concrete would be more interesting.
Honest question: Microsoft seems to be going out of its way to make this more difficult for developers. We're a year in now and the situation hasn't improved. We already have code-signing and app model IDs etc. Will figure it out eventually here but is it really necessary to jump through all these poorly documented hoops? How is manually referencing a source at "C:\Program Files (x86)\Windows Kits\10\UnionMetadata<SDK_Version>\Windows.winmd" considered best practice in getting this done? Why isn't an actual command path given with MakeAppx.exe step, and instead, vague instructions? Why is every step of this made to be so manual? Is this really the level of quality of support you want to give, to enable devs to add menu items in Win11?
Sincerely. It looks like it's being made difficult on purpose.
It's about as clear as mud, but I think as clear as concrete would be more interesting.
Honest question: Microsoft seems to be going out of its way to make this more difficult for developers. We're a year in now and the situation hasn't improved. We already have code-signing and app model IDs etc. Will figure it out eventually here but is it really necessary to jump through all these poorly documented hoops? How is manually referencing a source at "C:\Program Files (x86)\Windows Kits\10\UnionMetadata<SDK_Version>\Windows.winmd" considered best practice in getting this done? Why isn't an actual command path given with MakeAppx.exe step, and instead, vague instructions? Why is every step of this made to be so manual? Is this really the level of quality of support you want to give, to enable devs to add menu items in Win11?
Sincerely. It looks like it's being made difficult on purpose.