News

Visual Studio's 'Find in Files' Gets Modernization Revamp

Now that Visual Studio 2019 v16.4 has shipped, the dev team is turning to new priorities in the v16.5 preview round, including the IDE's "Find in Files" feature, which is getting a modernization revamp.

Find in Files, of course, helps developers search for terms in code files and, if need be, also provides "Replace in Files" functionality.

For such basic capabilities, the Visual Studio dev team is expending a serious amount of work and study, including soliciting developer feedback to ensure the best possible upgrade.

"Find in Files is one of the most commonly used features in Visual Studio," said Dante Gagne, senior program manager, Visual Studio, in a Dec. 12 blog post. "It's also a feature that gets a substantial amount of feedback, and due to the age of the code, has been very costly to improve. Earlier this year, we decided to reimplement the feature from the ground up in order to realize significant performance and usability improvements.

Microsoft:
[Click on image for larger view.] Microsoft: "The new experience is pictured above and should be easily recognized by the more modern look and consistent color theming." (source: Microsoft).

"We've released the new find in files experience in Visual Studio 2019 version 16.5 Preview 1 and we're looking for feedback from the community. We expect this experience to be the one our developers will use and love in the future, so we want to make sure we've prioritized the right features. We still have more improvements coming that we're not quite ready to talk about yet, but before we deprecate the old experience, we want to make sure the new version is meeting the needs of our users."

So far the team has already noticed significant performance improvements, like one search that used to take more than 4 minutes getting done in 26 seconds.

Besides performance, search functionality has been enhanced with the ability to specify paths, conduct multiple searches and use a regular expression builder.

"Now that the Find in Files experience has been reimplemented to use the newer patterns of Visual Studio, we're going to be able to provide more of the features we get asked for" Gagne said. "We'd love to hear your experiences with the new dialog. We're always watching Developer Community, and we've got a survey specifically for collecting feedback on the new experience that you can answer here. We know there are features that aren't available today and your feedback is how we'll prioritize the rest of the features. If you're running into problems or you think the new dialog isn't working correctly, please send us feedback with the Give Feedback button in Visual Studio."

About the Author

David Ramel is an editor and writer at Converge 360.

comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube