Notice (2018-05-24): bugzilla.xamarin.com is now in
Please join us on
Visual Studio Developer Community and in the
Mono organizations on
GitHub to continue tracking issues. Bugzilla will remain
available for reference in read-only mode. We will continue to work
on open Bugzilla bugs, copy them to the new locations
as needed for follow-up, and add the new items under Related
Our sincere thanks to everyone who has contributed on this bug
tracker over the years. Thanks also for your understanding as we
make these adjustments and improvements for the future.
Please create a new report on
Developer Community or GitHub with
your current version information, steps to reproduce, and relevant error
messages or log files if you are hitting an issue that looks similar to
this resolved bug and you do not yet see a matching new report.
Description of Problem:
Find in Files and Replace in Files takes into account .svn folders when executing a directory search (which is what happens when you want to replace text in files only within a project). This makes this feature difficult to use when used in conjunction with svn. The source control folder text gets matched and potentially changed.
Steps to reproduce the problem:
1. Select a project file with source files in it
2. Right click and select Find in Files
3. Select to Replace
4. Input a search string that will occur in at least one file
5. Select either Find or Replace
6. The search string is matched in metadata files in the .svn folder of the project.
Metadata files in the .svn directory (and possibly .git) can accidentally be modified.
The find in files should have the option to ignore the .svn and .git directories (or it should do so by default).
How often does this happen?
Whenever I'm searching/replacing text in all files in a project.
I'm not sure how "find in files" can know for certain what folders to ignore. I suppose we could make it ignore hidden files and folders, and add an option to include them.
See also bug 2055, arguably a better solution to this problem.
I think #2055 is the way to go
*** This bug has been marked as a duplicate of bug 2055 ***