Skip to content

Add F1 link from Command Line in C++ properties - #1886

Closed
Ben McMorran (benmcmorran) wants to merge 1 commit into
MicrosoftDocs:masterfrom
benmcmorran:patch-1
Closed

Ben McMorran (benmcmorran) wants to merge 1 commit into
MicrosoftDocs:masterfrom
benmcmorran:patch-1

Conversation

@benmcmorran

Copy link
Copy Markdown
Contributor

In a C++ project, go to project properties, and select Configuration Properties > C/C++ > Command Line. Press F1. You end up on the Clang Linker properties (Android C++) page, but this page seems like a much better fit.

In a C++ project, go to project properties, and select Configuration Properties > C/C++ > Command Line. Press F1. You end up on the Clang Linker properties (Android C++) page, but this page seems like a much better fit.
@PRMerger13

Copy link
Copy Markdown
Contributor

Ben McMorran (@benmcmorran) : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@colin-home

Copy link
Copy Markdown
Contributor

Ben McMorran (@benmcmorran)

I'm sorry to report that this change alone is unlikely to have the desired effect, or possibly any effect at all. By my count, this would make a seventh doc page into a target for this particular F1 tag. As near as I can tell, there's some randomness in which page gets chosen as the actual F1 redirection target when more than one has the tag. Clang Linker Properties (Android C++) happened to be the winner. The other doc pages with this tag are:

The real problem is in Visual Studio. Lots of controls are using "VC.Project.AdditionalOptionsPage" (with varying capitalization) as their F1Keyword attribute. I found no less than 27 xml files with this F1Keyword attribute in my installed VS, under MSBuild\Microsoft\VC\v160. Unfortunately, I don't know where to look for the sources to edit them. Ion might. What needs to happen is to change the F1Keyword attributes in whatever xml files exist for each of those property pages' controls to something unique (at least, unique per property page), and then update each of these Docs pages' f1_keywords header to match the new unique values. Ideally the change would go out in a servicing update for older binaries, as well, though it's unlikely to meet the bug bar, since we've lived with it forever, apparently.

@benmcmorran

Copy link
Copy Markdown
Contributor Author

Thanks. I'll see what I can change on the VS side and open a followup PR once that's resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants