You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the binary is just self-extracting zip file, why not just provide this as a archive (let users extract with their 7z application) so they are not nudged to run unsigned binaries unecesary.
Of course this extraction is possible without providing dedicated archive file, however it's not obvious for first time users that this is even a option without running it. Before running this could be some installer really necesary to run, updating paths in registry and whatnut.
Maybe at least giving the Windows binary a explicit name to know that it's just self-extracting binary that the extraction with a standalone 7z is possible? oss-cad-suite-windows-x64-20240131-self-extracting-7z.exe
The text was updated successfully, but these errors were encountered:
Also another issue with that exe is that when you run it, it automatically extracts to current directory without asking you where to extract so would prefer .7z and dropping the exe too.
I got few versions of this and I always forget how this behaves when downloading next one after some time, so it is not just "first time users" :-)
When the binary is just self-extracting zip file, why not just provide this as a archive (let users extract with their 7z application) so they are not nudged to run unsigned binaries unecesary.
Of course this extraction is possible without providing dedicated archive file, however it's not obvious for first time users that this is even a option without running it. Before running this could be some installer really necesary to run, updating paths in registry and whatnut.
Maybe at least giving the Windows binary a explicit name to know that it's just self-extracting binary that the extraction with a standalone 7z is possible?
oss-cad-suite-windows-x64-20240131-self-extracting-7z.exe
The text was updated successfully, but these errors were encountered: