kwsch
Usage Issue
This is less of an issue with the repository and more me asking for help with the usage. I'd appreciate any help I can get.
I ran dotnet build untieunite.sln, and the build succeeded with 0 warnings and 0 errors. I made my .bat file, copy and pasting the contents from the README and filling in my directories. Whenever I run my file, I get untieunite.consoleapp: command not found as an error.
Since I'm copy and pasting it, I can only assume the error must be where I'm placing the file, but I'm placing it next to the executable, which is the .sln file, if I'm not mistaken? I'd be grateful to anyone willing to help me with this.
Operating system? You might have to be explicit (untieunite.consoleapp.exe), but the intent is to invoke the program via command line with arguments for input_path and output_path. Most users find it easier for the .bat file approach instead of command line entry.
I was running it on macOS Monterey. I suspected there might be some mac-specific problem, so I ran it on Windows 11 using Parallel Desktop and got the same error.
Perhaps I misunderstood the README, is dotnet build untieunite.sln supposed to result in a .exe file? There's a few UntieUnite.ConsoleApp files around in the folders, but none of them were a .exe file.
The dotnet build triggers a build of the exe, which should then be in the ConsoleApp project folder's Debug/bin folder.
That's where the .bat file should be located & run from.
I see. In that folder, I have a UntieUnite.ConsoleApp, and .dll, .pdb, but there's no .exe in there. Is the plain UntieUnite.ConsoleApp supposed to be the executable? I ran the .bat file in there from Windows and also tried an explicit call, but none of those worked. The Windows error message was that the app was "not recognized as an internal or external command, operable program or batch file."
It's supposed to produce an exe. Try rebuilding with visual studio or something.
Deleted the folder, re-extracted from the .zip, and it's still the same. This is what the terminal tells me when I build. Should the .exe be mentioned in here?
Instead of .exe, try invoking with the .dll?
Not sure if updating the runtime (from netcore3.1 to NET6+) via the csproj settings will yield a different result.
No dice, unfortunately. Any last ideas? Although I'm starting to accept this might be a Mac issue maybe and I'm just unlucky.