I beleive the Launch.json replaces or overrides that part of the .csproj file in the newer C# project templates so you need to move the StartArguments into commandLineArgs
Maybe this is close? It is not quite right but i do not have enough knowledge of Rhino Script to fix but hopefully it helps you along the path - good luck!
When I run Rhino via cmd from its directory with “/nosplash” it opens without splash screen as expected, but when I add “/nosplash” to the command above from Visual Studio it returns a plugin error before starting:
and another error when it finished loading:
Furthermore it does not open the grasshopper file.
I can’t seem to get either method to work. I’m on MacOS, so I believe I need -arg instead of \arg, and confirmed this by launching Rhino from a Terminal. I watched the video “5.9 Speeding Up…”, and I’ve tried putting -runscript="_Grasshopper", with and without escaped quotes, in various places, all no dice; it never has an effect. It would significantly speed my development to get this working. I’d love some help!
It’s important that I took out the “executablePath” from my previous post, as that was causing Grasshopper to not see my .gha file and then the whole thing was pointless.
Now I can really by making a re-usable .gh file for testing. Thanks!
Glad to see you’re rockin @silviana_amethyst, just so you know Visual Studio for Mac is being discontinued in late August 2024. Here are some nice shiny docs on using vscode.
I’ll follow up and say that my launchSettings.json was left over from my student doing development on a Windows machine. I worked hard to find that Project value. My new student, also doing development on a Windows machine, had to (of course) remove the hardcoded file path to the rhino executable. But then VS changed Project back to Executable.
So, now I’m fighting for space in the launchSettings.json file. I think I might need a profile for Windows and a profile for Mac.