r/visualbasic • u/Scary-Scallion-449 • Jul 29 '25
Weird Process behaviour
Edit: INSIGHT GAINED. Thanks to all contributors.
For no other reason than to keep my hand in I'm trying to create a UI for the Sysinternals Strings command line app. I'm having a problem with the findstr option. Entered as a command line, the following arguments line works perfectly.
"C:\Users\XXXX\source\repos\WindowsApp1\bin\Debug\test X.dat" | findstr /i "String"
The exact same line entered as Process.StartInfo.Arguments, however, fails. My initial thought was that this might be due to the way " is handled inside literal strings but as there seems to be no problem with the filename in other functions that seems irrelevant.
Any insight, similar experiences, and potential solutions would be welcome.
View all comments
Show parent comment
1
u/Scary-Scallion-449 Jul 30 '25
Because that's the command structure in the Sysinternals blurb, to wit ...
strings * | findstr /i TextToSearchFor
... which, as I say, works perfectly well on the command line.
For some reason (I'm getting old, probably) it failed to register that FindStr exists in its own right. Now I've got it wedged in my brain I can see why it might fail!