Have Geek Brain

Smallest Windows executable

I need to create a very simple graphical Windows application (open a file, make some changes based on user input, upload a file to an intranet server). The client company has the latest versions of Java SE, .NET, and Adobe AIR installed on all of its machines. And their # 1 requirement is to have the smallest possible xcopy deployment package. So which of the three listed platforms should I be using? Another option, of course, is the native exe.

Thank you, Andrey

EDIT: Thanks for all the answers guys! The client has offices in New Zealand and Australia, from what I have heard that communication there is very expensive and in short supply. And the sizing requirements came from their IT operations department, which in the past refused to install custom apps as being too big for features ... I'm looking for a modern platform for developing an app, at least in C ++;) So I would change the question which of the following platforms will have the minimum executable file size: MS VC ++ 2010, .NET 4.0 or earlier, Java 1.6 or earlier, Adobe AIR 1.6 or earlier.

+2


a source to share


9 replies


And their # 1 requirement is to have the smallest possible xcopy deployment package.

If you take this requirement literally, it is almost impossible to meet. If your program can only be truncated by one byte, then it does not meet the requirements.



If I were you, I would ask for clarification:

  • Can they give you a specific measure for the size you require? That is, how small is small enough?

  • If not, can they tell you how they will judge if your program meets their # 1 requirement?

  • If not, rewrite the contract as "time and materials" ... because you currently have no control over how much effort it will take!

+2


a source


I've seen several Windows graphical applications written in a clean assembly. You'd be surprised how much functionality you can fit in 10k.



I am by no means recommending assembly language, but it is the only way to fulfill such a strict "least possible" requirement.

+1


a source


As stated in Tiny PE only has a few bytes, but do you really need such a small application? Does a few kilobytes matter?

+1


a source


Handwritten assembly; -)

But for maintainability, I would go with either .NET or a native exe written in delphi / C ++ with manual window API calls.

0


a source


What is the point? Whichever technology you choose, the executable file will be no more than a few kilobytes (not including resources such as images). Hard drives now have gigabytes of memory, and internet connections can transfer several megabytes per second. You may be worried about a large application (say more than 50 or 100 MB), but in your case it just doesn't make sense ...

0


a source


I would use .Net because your target OS is Windows and .NET with it. As for deciding which platform will generate the smallest application on disk, I have no idea. However, I am confident that all three APIs will create an application millions of times less than the sum of all these platforms.

Why is this size requirement? Give us more details ... maybe there is another way to make your customer happy!

0


a source


Delphi or .NET (WinForms with C #) are probably the best ones for this. Delphi will create its own executables that don't require any external dependencies, but since the framework already has .NET, it fits the bill as well.

0


a source


Thought of silverlight from a browser app ? They are pretty small.

0


a source


Use VC ++ to build your own application, then compress it with an executable.

0


a source






More articles:


All Articles