如何在 Visual Studio 2008 中从 For 或 For Each（类似于大括号，但在 vb 中）跳转到下一个语句
有谁知道从关键字开头跳转的键盘快捷键是什么，例如 for、forEach、if、while< /code> 等...当您使用“vb.net”时是否在 Visual Studio 中？我发现了以下问题，其中我以为会做我正在寻找的事情，但事实并非如此。
根据上面链接问题的评论，我检查了路径：
Tools/Options/Environment/Keyboard
...Edit.GotoBrace< /code>命令。根据我的阅读，该命令应该映射到瑞典语的键绑定：CTRL + å。
Vb.net 本身不使用大括号，但在下面的示例中：
For Each Foo in Bar
Do lots of stuff
Next
我本以为相同的命令应该将我从 For Each 跳转到“Next “但它没有任何作用。是否还有另一个命令（或者该命令应该有效，但本地有问题？）
Does anyone know what the keyboard shortcut for jumping from the start of a keyword, such as for, forEach, if, while etc... is in Visual Studio when your using "vb.net"? I found the following Question, which I thought would do what I was looking for, but it doesn't.
Following a comment from the linked question above, I checked the path:
Tools/Options/Environment/Keyboard
...for the Edit.GotoBrace command. From what I read, the command should be mapped to the keybinding: CTRL + å in Swedish.
Vb.net doesn't use braces per se, but in the following example:
For Each Foo in Bar
Do lots of stuff
Next
I would have thought that the same command should jump me from the For Each to the "Next" but it doesn't do anything. Is there another command (or should that command work but something is broken locally?)
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
为了其他 SO 用户的缘故，所以答案不会作为答案中的评论隐藏：
来自：
https://connect.microsoft.com/VisualStudio/feedback/details/534430/block-navigation-for-vb-net-similar-to-paranthesis-navigation
For the sake of other SO users, and so the answer isn't buried as a comment inside of an answer:
from:
https://connect.microsoft.com/VisualStudio/feedback/details/534430/block-navigation-for-vb-net-similar-to-paranthesis-navigation
没有可以做的。这是比匹配牙套困难得多的任务。找到匹配的NEXT关键字需要进行语法分析。只需对文本进行标记即可匹配大括号。我建议您在 connect.microsoft.com 上提出功能请求，这是一个很好的请求。
No can do. It is a much harder task than matching braces. Finding the matching NEXT keyword requires syntax parsing. Braces can be matched by merely tokenizing the text. I'd recommend you put in a feature request at connect.microsoft.com, it is a good request.