Application.Launch doesn't seem to be passing the command line arguments in Process Start Info

[Paul Nardell]

I've had a SpecFlow test harness that I've been using for a bit over a year.  All has been working fine.

The test harness sets a path to a binary and then adds a command line parameter to the ProcessStartInfo then starts the application under test.  I've had no issue with this up until now and have made no changes to it.  This morning, I run my tests as usual and I'm seeing errors coming up when the application starts which suggest that no command line arguments are being passed in.  I see the expected value for Argument when I debug and inspect the PSI object but for some reason, when the Application.Launch command is executed by Visual Studio, the command line parameters are now being ignored.

Any ideas?  It seems very odd indeed.  Could there have been a Microsoft update to Visual Studio over the weekend?  I've tried both VS 2015 and VS 2017 and the issue is the same.

[Mike Hetzer]

Perhaps try to Launch the application using ProcessStartInfo object and System.Diagnostics.Process.Start() methods.
Then Attach to the already started application process in White.

That's about all I can offer right now - otherwise it may be an underlying problem with setting the path I would guess.