In recent version of Visual Studio 17.2.3 and SmartCommandLineArgs 2.3.0, arguments that contain backslash n are sent to the application as a new line character.
--my_arg=c:\users\nathan\source\myfile.txt
This appears to work fine on Visual Studio 17.1.5 and SmartCommandLineArgs 2.3.0.
If I use forward slashes instead of backslash it parses the argument value properly.
If I run via the command line in a Developer Terminal then it works properly, so it seems to be something with SmartCommandlineArgs:
In recent version of Visual Studio 17.2.3 and SmartCommandLineArgs 2.3.0, arguments that contain backslash n are sent to the application as a new line character.