A vote of 1 for no EXE
-
PIEBALDconsult wrote:
I also don't include IDE-specific files because I generally don't use an IDE and they're unlikely to be of any use to the reader.
I'm going to have to disagree with this one unless you're publishing articles for Ruby/C++ on *nix/etc where no IDE is the norm. The vast majority of .net developers do use VS, and automatic up-conversion wizards mean that a minute to create a .sln/csproj pair for your article in the minimum version of VS that supports what you're doing will successfully load in all of the newer and shinier versions of VS that MS churns out.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason? Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful? --Zachris Topelius Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies. -- Sarah Hoyt
But I'm not going to create files that I don't need simply because someone else might find them helpful.
-
A user voted my CWtlPicture article a 1 because I did not supply an EXE file with the article. I stopped putting EXEs with most articles a few years ago because of virus concerns and because targeting multiple platforms (32 bit, 64 bit, etc.) adds complexity to the link structure. I know it is more convenient to download and run a pre-compiled EXE than to download and build a project. However, at least half of the Code Project EXEs I've recently download either crash or do not run at all, so I have to debug and/or build the project anyway. On the article submission page, it says "If emailing files, please do not email executable files within zips. Our email provider automatically bounces any email containing exe's, or zip's with exe's inside." But it is possible to send EXE files in other ways. What is your take on providing EXE files with articles? Do you still do so? Have you run into platform issues with downloaded executables like I have? What is the best practice nowadays?
I think your reasoning is excellent, Ed. You just ran into a web surfer who's too lazy to compile the project himself, or too inept, or just looking for freeware with no intention of learning anything or doing any work. Move along, nothing to see here, lad. And nothing to be concerned about on your end. Carry on! :)
Will Rogers never met me.