![]() ![]() There is no way to trigger it manually if Visual Studio decides it isn't worth it's time to give you the option. ![]() ![]() Supplying a template parameter in the editor, a useful way to get intellisense info for templates, frequently just doesn't pop up at all. ![]() Using intellisense to rename something is no longer even mildly reliable, now frequently suggesting locations that are very clearly in another class. For example, in something like foo.bar->baz (when no function baz exists) it now highlights foo, instead of bar. You cannot use F12 to jump to the definition of a designated initializer.Įrror squiggles seem to have moved to highlight another part of the source, compared to earlier releases. Jump to definition is now far less reliable (frequently not finding anything, even for simplistic use cases), and jumping to declaration seems to have been removed entirely. You could use F12 to jump to a definition, and then press it again to jump to the declaration of a function. Why does that option even exist in local find/replace? I also don't want to remember the times when I used local find/replace, and instead completely f*cked over my entire project (as in: revert the days' work to the last version in version control) because I had accidentally reconfigured it to 'replace in all files'. I don't want to even think about how often I've started typing, only to find that I'm instead reconfiguring local find/replace. In the current release, ctrl-tabbing into an editor that has a local find/replace box open will set focus to that find/replace box, instead of to the text. Microsoft seems to find an exciting new way to break search in what feels like each release. I hope this release will be an improvement, obviously, but I feel Visual Studio is functioning less and less well in each release. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |