Limiting reference discovery in VS2015
In our project, we have several classes that each have a private member variable like:
private:
varType varName;
When we right-click on that variable name and select Find all references, the list returned includes all references seemingly based on the name alone, including those in the other classes.
Now I'm not sure but I seem to recall that earlier version of Visual Studio were a little more intelligent in that they could figure out I was only interested in the references to this specific variable (i.e., only in the given class).
Does anyone know of a way to get a list of the relevant results rather than everything with the same name?
It appears to me that the first time I go looking for an id member variable, the entire concept of searching for references will be rendered useless as I try to filter the million or so lines containing it.
visual-studio visual-c++ ide
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
add a comment |
In our project, we have several classes that each have a private member variable like:
private:
varType varName;
When we right-click on that variable name and select Find all references, the list returned includes all references seemingly based on the name alone, including those in the other classes.
Now I'm not sure but I seem to recall that earlier version of Visual Studio were a little more intelligent in that they could figure out I was only interested in the references to this specific variable (i.e., only in the given class).
Does anyone know of a way to get a list of the relevant results rather than everything with the same name?
It appears to me that the first time I go looking for an id member variable, the entire concept of searching for references will be rendered useless as I try to filter the million or so lines containing it.
visual-studio visual-c++ ide
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
I don't recall exactly how it was in VS2015, but in VS2017 you can group the 'references' found by project or path etc which is fairly convenient. Other than that there's likely no way apart from installing some plugin which has a more involved parsing.
– stijn
Jan 3 at 8:33
add a comment |
In our project, we have several classes that each have a private member variable like:
private:
varType varName;
When we right-click on that variable name and select Find all references, the list returned includes all references seemingly based on the name alone, including those in the other classes.
Now I'm not sure but I seem to recall that earlier version of Visual Studio were a little more intelligent in that they could figure out I was only interested in the references to this specific variable (i.e., only in the given class).
Does anyone know of a way to get a list of the relevant results rather than everything with the same name?
It appears to me that the first time I go looking for an id member variable, the entire concept of searching for references will be rendered useless as I try to filter the million or so lines containing it.
visual-studio visual-c++ ide
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
In our project, we have several classes that each have a private member variable like:
private:
varType varName;
When we right-click on that variable name and select Find all references, the list returned includes all references seemingly based on the name alone, including those in the other classes.
Now I'm not sure but I seem to recall that earlier version of Visual Studio were a little more intelligent in that they could figure out I was only interested in the references to this specific variable (i.e., only in the given class).
Does anyone know of a way to get a list of the relevant results rather than everything with the same name?
It appears to me that the first time I go looking for an id member variable, the entire concept of searching for references will be rendered useless as I try to filter the million or so lines containing it.
visual-studio visual-c++ ide
visual-studio visual-c++ ide
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
asked Jan 3 at 7:55
paxdiablopaxdiablo
641k17512631682
641k17512631682
I don't recall exactly how it was in VS2015, but in VS2017 you can group the 'references' found by project or path etc which is fairly convenient. Other than that there's likely no way apart from installing some plugin which has a more involved parsing.
– stijn
Jan 3 at 8:33
add a comment |
I don't recall exactly how it was in VS2015, but in VS2017 you can group the 'references' found by project or path etc which is fairly convenient. Other than that there's likely no way apart from installing some plugin which has a more involved parsing.
– stijn
Jan 3 at 8:33
I don't recall exactly how it was in VS2015, but in VS2017 you can group the 'references' found by project or path etc which is fairly convenient. Other than that there's likely no way apart from installing some plugin which has a more involved parsing.
– stijn
Jan 3 at 8:33
I don't recall exactly how it was in VS2015, but in VS2017 you can group the 'references' found by project or path etc which is fairly convenient. Other than that there's likely no way apart from installing some plugin which has a more involved parsing.
– stijn
Jan 3 at 8:33
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54018346%2flimiting-reference-discovery-in-vs2015%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f54018346%2flimiting-reference-discovery-in-vs2015%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
I don't recall exactly how it was in VS2015, but in VS2017 you can group the 'references' found by project or path etc which is fairly convenient. Other than that there's likely no way apart from installing some plugin which has a more involved parsing.
– stijn
Jan 3 at 8:33