Sadly, there wasn't a non-hacky way to implement the extension, and there's no way to determine which languages "support this feature natively". Since Go To Definition wasn't designed as a queryable command, the extension had to use some broad guessing at what has definitions, and it actually under guesses for certain scenarios (I remember one or two in VB, at least).
I'd be happy to at least modify this standalone version to avoid loading for documents that use your DSL language type and you could file a Connect bug to get it integrated back into the PPT extension . Fee free to either add a Q&A comment here or a github bug (https://github.com/noahric/gotodef/issues) with the details, or make the modifications yourself and send me a pull request on github.
I think this would be a very userful feature (at least for me): go to definition from XML comments like those:
/// A loader, that is responsible for retrieving XYZ from the database.
/// E.g: <see cref="MyLoaderClass"/>.
Sometimes I do want to promote to document rather than just peeking definition.
Please refer and reply to this discussion:
I used to use the "Go to definition" feature of pre-2012 versions of Visual Studio to navigate identifiers that came from build errors (which happens excessively often when something goes wrong while comipiling templates).
It is counter productive to have to copy/paste identifiers from the build output to a code window that does not deserve polluting, only to then use the addin.
Would it be possible to make this addin work in the context of any text window, like the build output?
It may be possible, but definitely not straightforward. The extension itself doesn't actually do the "Go to definition" logic, it just basically triggers a press of F12 (the GoToDefinition command). If F12 does work in the output window, then it's just a matter of getting the extension there and figuring out what to underline on ctrl+mouseover.
I've had a problem for ages while working on a legacy site that was built in VB.NET and we've added C# projects to it.
The problem seems to be that Go To Definition doesn't work across the projects.
I even tried setting up a test solution to see if the problem existed on a brand new one and it still did.
I've tried all the solutions I've found on the net around using Project References and not File ones but nothing seems to work.
Well, one thing works. ReSharper. Unfortunately, ReSharper is quite overkill just to get Go To Definition working properly...
Is there any chance your extension could fix this bug and enable the Go To Definition (And Find Usages if possible :P) across projects?
I'm not comfortable in making this change myself. Given your response to my review comments indicating that it wouldn't be too hard to implement peek definition and find all references with a non-configurable key combination, would you consider?
CTRL + Left Click == goto def
CTRL + Middle Click == peek definition
CTRL + Right Click == find all references
what do you think?
...well now that MS's PPT 2013 extension is out, which can do a peek definition with the ctrl-click, I guess this request (and extension) is no longer needed...
unless this one provides the ability to do both (peek and goto def) via different mouse buttons / key combo.
without this plug-in, when I click on a word, hold [Ctrl] and [Shift], and click on another word, it selects the everything between both clicks including the whole words.
however when I have this plug-in installed it tries to jump to the word I click on even if it isn't a hyperlinked one.
it would be nice if you ignored jumping if, other keys were pressed, specifically in this case the [Shift] key.
Hi, the functionality you're describing doesn't require the use of the Ctrl key. Click once in the file, then Shift+Click to where you want the selection and it should select everything in-between. Ctrl is not needed.