[OT] VS2022 Replace in Files problem
Folks, about 2 months ago, VS2022 *Replace in Files* stopped working as expected on my work PC, in VMs and on my laptop. After hours of experiments I have determined that Replace in Files will not alter any "external" files that are not part of an open project. The file types, folder locations, user account, recent minor updates, dialog options, /reset, etc make no difference. Can someone do something like this in a recent VS2022 release ... Create a C:\temp\junk.txt file and put the word FOO inside it. In VS2022 with *no projects open*, run a Replace in Files over the temp folder and file and see if you can change FOO to BAR. Does the txt file get updated? Not for me. Below is a sample of my attempt which says it made 1 change, but it's a lie. Is there some obscure option I've accidentally toggled? In VS2015 it changes files as I expect. I opened a ticket, but it's been in evaluation status for weeks -- Thanks, *Greg K* [image: image.png] [image: image.png]
Greg I just did a test as you requested. VS 2019 Pro 16.11.17 works as expected. VS 2022 Pro 17.2.6 does not make changes, as you have experienced, even though the output window says otherwise. . Regards, RC On Thu, 14 Jul 2022 at 14:10, Greg Keogh via ozdotnet <ozdotnet@ozdotnet.com> wrote:
Folks, about 2 months ago, VS2022 *Replace in Files* stopped working as expected on my work PC, in VMs and on my laptop. After hours of experiments I have determined that Replace in Files will not alter any "external" files that are not part of an open project. The file types, folder locations, user account, recent minor updates, dialog options, /reset, etc make no difference.
Can someone do something like this in a recent VS2022 release ... Create a C:\temp\junk.txt file and put the word FOO inside it. In VS2022 with *no projects open*, run a Replace in Files over the temp folder and file and see if you can change FOO to BAR. Does the txt file get updated? Not for me. Below is a sample of my attempt which says it made 1 change, but it's a lie. Is there some obscure option I've accidentally toggled?
In VS2015 it changes files as I expect. I opened a ticket, but it's been in evaluation status for weeks -- Thanks, *Greg K*
[image: image.png]
[image: image.png] -- ozdotnet mailing list To manage your subscription, access archives: https://codify.mailman3.com/
VS 2019 Pro 16.11.17 works as expected. VS 2022 Pro 17.2.6 does not make changes, as you have experienced, even though the output window says otherwise.
Wow! Thanks. So I'm not going nuts. Now the question is: what's going on? Is this by design or not? I hope it's not by design, because I often use VS for bulk file editing. I was bulk changing htm files in a website several weeks ago when I noticed that nothing had changed. The workaround is to tick *Keep modified files open* then Ctrl+Shift+S to save them all, then close all tabs. I had 400+ htm files, so I was lucky it worked. *Greg*
participants (2)
-
Greg Keogh -
Richard Carde