February 16th, 2007 by rick
I am not OVERLY shocked about this, but at the same time, I do find it interesting that SharpDevelop actually creates a smaller compiled binary than VS.NET does from the same code.
I decided to compile a Win32 app I had written a while back for my company in SharpDevelop just to see if:
- SharpDevelop could import from a VS.NET .sln file correctly.
- SharpDevelop would compile the (admittedly quite simple) code without problem.
- SharpDevelop would create a similar sized binary with similar execution time.
For #1, it was seamless, painless and very easy. Navigate to the project to import and boom, I’m done. Once again, #2 was simply and quickly tested with incredibly pleasing results. I clicked the run button and it popped up… no problems. And finally, on #3 I was nicely surprised.
- Compiled with VS.NET, .exe file size: 36k.
- Compiled with #Develop, .exe file size: 28k
That is a 23% reduction in executable file size. Granted, this was a small application with no images or other large binary objects, but my guess is, similar results could be seen in larger applications. Can you imagine that 3mb executable file dropping to 2.333mb, etc? It may not seem like a whopping huge difference with harddrives being as extensive as they are nowadays, but it harkens to cleaner bit code being created and I’m thrilled to see this result personally.
Posted in Technology |
