Closed witoldsz closed 1 year ago
Cool, my first github issue :-). Thanks for reporting it with all required information. . The problem has been fixed with with https://github.com/peterdell/wudsn-ide-install/commit/a510e002f27796384ab68f4e9e9bfa00c013640e Please try with the new EXE.
OK, so I've tried the new .exe
but that Windows-thing was removing the file saying it is dangerous (excuse my ignorance, but last time I used Windows, it was XP and now I've installed Windows 10 in virtual machine just to check how does the WUDSN work, waiting for Linux version soon, as promised :wink: )
So, I've tried the .bat
version and it worked well. Why the .exe
version exists if it's just a problematic way to lunch simple batch files? Or is there some other difference?
If you are a Linux user, scripts are the totally natural way to start a program. CHMOD a+x and there you go. On Windows, it is the opposite. Having the EXE comes with benefits like including icons in different resolutions, publisher information, version information and it is also the only way to associate the application with a file type like ".asm" via the registry. I didn't expect it to be so much hassle though, because I had released all my other programs as EXE created from Java (jar) files. But since I want to download the JDK/JRE itself, it's not possible. I'm sure I'll find a way to make a EXE that does not result in false positive. And since now I know that you'd like to try a Linux version, I'm motivated to actually do it.
Windows 10, running
wudsn.exe
(most recentmain
, i.e. commitba44f3a07ecc873630a1f97dabe941a6af5851af
).The
https://www.wudsn.com/productions/java/ide/downloads/eclipse-platform-4.19-win32-x86_64.zip
responds with500 Internal Server Error
.