-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
prcEditor isn't opening #17
Comments
Thanks for filing this issue! To start, I'm assuming you've downloaded the latest version. Given that you uninstalled the pre-3.0 runtimes I won't have to check that the right version is running, but if you want to be extra careful you can double-check by doing
To check if there's some sort of dependency issue, in the command line, run
So basically the exe is just a wrapper program that calls dotnet and the dll together. But it will hide the output which makes calling the exe in the command line equally useful to just double-clicking it in the folder. If we get an error there, you can report it back here and we can decide what the solution might be. Other options:
then try running the output (which will be located in a folder named "builds") |
So I installed .NET core SDK 3.0.103 and ran though it still doesn't open when double clicking? |
That's kind of baffling. For one, the SDK really shouldn't be required because in its compiled form, it should only require the runtimes. Sounds like there's maybe some sort of re-compilation going on when you run the command. A quick solution to let you double click without any more work is to just create a batch file like dotnet prcEditor.dll I think what's happening is a problem with the 32bit (x86) vs 64bit (x64) versions of the runtime and the program exe. I notice that in your paths, dotnet runtimes are in the Program Files (x86) folder, maybe you should try the x64 versions of the dotnet runtimes instead. Either that, or we can use a build for x86 or AnyCPU. The configuration isn't specified in my automatic build setup, so I'm not sure if it built only for x64. I would figure the automatic setting is "Any CPU", which should work for either option, but can't be sure since it's been a while without messing with settings. Just in case, I pushed a commit to explicitly set this, and the release page should now have the AnyCPU version |
I'm getting the same issue. When viewing the event logs, I see this error:
After some googling it seems that this DLL is something you have to ship with the application when deploying it? I'm not sure how to install it. |
|
I've got only the 3.0.3 runtimes and prcEditor.exe doesn't do anything when clicked?
screen recording
^ video evidence if I didn't explain the problem right
The text was updated successfully, but these errors were encountered: