I have a VB.NET application that takes command-line arguments.
It works fine when debugging provided I turn off Visual Studio’s ClickOnce security setting.
The problem occurs when I try to install the application on a computer via ClickOnce and try to run it with arguments. I get a crash when that happens (oh noes!).
There is a workaround for this issue: move the files from the latest version’s publish folder to a computer’s C: drive and remove the “.deploy” from the .exe. Run the application from the C: drive and it will handle arguments just fine.
Is there a better way to get this to work than the workaround I have above?
Thanks!
“Command-line arguments” only work with a ClickOnce app when it is run from a URL.
For example, this is how you should launch your application in order to attach some run-time arguments:
I have the following C# code that I use to parse ClickOnce activation URL’s and command-line arguments alike:
Such that my main function looks like: