3 ms·
I've reverted to WIN32 because users can run a single file, bare bones EXE without the Permission Police blocking you. Too often users aren't allowed to instal
by tosseraccount 12y ago
I've reverted to WIN32 because users can run a single file, bare bones EXE without the Permission Police blocking you.
Too often users aren't allowed to install programs.
A simple program that can run on anything since XP is a good solution around Microsoft's sandbox strategy and DLL hell and install programs are big problems.
With wine you can even run your simple EXE on Linux and Mac.
Native x86 means you run faster than these virtual machine based solutions.
- ynik 12y agoAre you talking about the .NET misfeature that gave managed programs running from network shares less permissions than native programs running from the same network share? Because that was removed a long time ago (.NET 3.5 SP1?).
- mc_hammer 12y agoi think hes saying for less dependencies, and portability, and no required elevated users, and speed: its best to write it in straight win32. i agree and ill chime in down here in the downvotes. i think a lot of authors like the op and myself if we want a speedy app we have to go to win32 api only. c# is slow and even MS doesnt use it in windows desktop mgr or IE. ex: without hw accelleration the hearts game is unplayable on a 2ghz machine. with raw win32 api thats not a problem
- ghuntley 12y agohttps://github.com/Squirrel/Squirrel.Windows https://github.com/Squirrel/Squirrel.Windows