The official source of product insight from the Visual Studio Engineering Team
In our previous blog post, we introduced the new Find control we are building in Visual Studio. Our goal was to streamline and modernize the vast array of Find experiences and provide a lightweight mechanism to search within documents. With the huge number of responses we received from the Developer Preview, we knew that our top priority for the Beta release was improving the quality of Find. Since the Developer Preview release, we have fixed a large number of customer reported bugs, including replace in selection not working, buttons being disabled in the find dialog, missing wrap alerts, match whole word not working, and more. There still are some rough edges in the Beta Find control, but we are working hard at making Find consistent and reliable for future releases. Along with fixing bugs, we took a hard look at addressing the top customer suggestions. Here are some of the top suggestions reported in the Developer Preview that are now available in Beta:
Even with the improvements in the Beta Find control, there are still some noticeable bugs:
IMPORTANT: The extension provides a workaround for the shared scope & options issue. Please note that this extension can be expected to work correctly only on Beta and should be uninstalled when upgrading to future versions. This extension will not be serviced by Microsoft. If you encounter any issues after installing the extension, please uninstall and restart Visual Studio.
Finally, we want to thank you all for the great feedback you have been giving us. We are using the feedback to prioritize our work areas and we appreciate you telling us the Find pain-points. Please do continue to send us feedback on the Beta Find experience!
Murali Krishna Hosabettu Kamalesha – Program Manager, Visual Studio Editor team
Thanks for releasing the updated FindSettingsSeparator.vsix as this latest version works great. So glad to see the find scope issue resolved!
Ah, yes this updated version does in fact work with VS11 Beta with updates applied. Thank you!
One feature I would really love is Find/Replace with wildcards. So you can replace parts of phrases without affecting the parts that can vary.
Like mycontrol.DoSomething(1, 5, 34, 32, "abc") replaced with mycontrol.DoSomethingElse(1, 64, 28, 32, "abc"). You would specify a find string like mycontrol.DoSomething(*34, 32*) and replace string like mycontrol.DoSomethingElse(64, 28). Currently something like that would require going through every instance and replacing manually, since you don't know what the other parameters might be and you can't run a regular replace.
The FindSettingsSeparator worked for "Visual Studio 11 Express Beta for Windows 8"
but I can't install it on "Visual Studio 11 Express Beta for Web". Thanks!
"The new Find supports .NET regular expressions"
This is HUGE, really appreciated! Thanks!
The only thing I would really like to have changed now is the search text being multiline (3-5 lines will do) and the same for the replacement text. I know this makes the box huge with all options unfolded, maybe this could be based on screen resolution or simply an option.
Oh and some way to add favorites (especially useful for regex searches) would be really sweet, history is great, but it's not really a substitute.
For inspiration perhaps have a look at the Replace dialog in UltraEdit.
Val: That is exactly why we have Regular Expression support! Go and look it up if this is unfamiliar to you, it's a really powerful tool - not just for search/replace in editors, but also for a lot of development scenarios.
Please add "CTR+/" shortcut for commenting/uncommenting ("CTR+K,CTR+C" is useless - too complex). This little change would save me and other guys tones of minutes every working day :)
@Konstantin: If you prefer using a different shortcut such as Ctrl+/ you can assign it yourself in Tools/Options dialog, Environment/Keyboard page (and remove it from the current command using it, like Tools/GoToCommandLine)
@Alin: Is there a functionality for toggling comments in Visual Studio?
..so that one shortcut key could be used for both commenting and uncommenting like it works in almost all other code editors.
I'm running VS 11 Beta 11.0.50323.1 QRELB
The above patch (VS11_BETA_ONLY-FindSettingsSeparator.vsixx) announces that "The extension manifest is invalid."
I hate this thing. I have been using it for months and can't get used to it. I can never find which dropdown arrow does what. To make things worse - I can't get it to do search/replace with regex groups. I thought it would be fixed in RC. I guess not.
Is there an option or registry hack to restore the old dialog by default? I know it is still there because it is the same thing that still comes up with Ctrl+Shift+F/H, but it used to be that one of these (Ctrl+F/H) brought up local search and the other did it for global solution scope...
Visual Studio 2012 RTM does not search project files (vcproj, vbproj) when Find or Replace in Files is invoked. My intent was to use this to make all 130 projects in my solution target v4.5 of the framework by replacing "<TargetFrameworkVersion>v4.0</TargetFrameworkVersion>" with "<TargetFrameworkVersion>v4.5</TargetFrameworkVersion>". Are there faster ways to do this without having to open each project property one at a time?
You can use the Replace-in-Files dialog and change the scope to point to the folder in which these project files reside. This way, you can find and replace all occurrences in these files as desired.
In RTM, we've moved the search options from the dropdown to reside next to the scope. This was done to make options visible by default and easily accessible. This will hopefully make the UI more friendly to use. In VS 2012, the Find uses .NET regular expressions. The capture group syntax in .NET regex is slightly different when compared to the POSIX syntax. I'd recommend reading about .NET regular expression substitutions (msdn.microsoft.com/.../az24scfc.aspx).
If you need further help, have specific questions or feedback, please feel free to reach out to our find crew directly at firstname.lastname@example.org.