A vote of 1 for no EXE
-
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 suspect that poster is of the [Gimme the Codez] variety - so I wouldn't let it bother you Ed
-
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?
Ed Gadziemski wrote:
What is your take on providing EXE files with articles? Do you still do so?
I never run the exe for the reasons you mentioned, concern about viruses, etc. Also, I usually want to include the code is something I'm doing, so I want to make sure the code compiles, I really don't give a darn about the exe. Me, I just put a link to the code on GitHub nowadays. I'll make a branch specific for the code in the article so the reader can correlate what I'm writing about and the code examples in the article to the actual code. Sorry to hear about your 1-voter. Marc
Imperative to Functional Programming Succinctly Higher Order Programming
-
I suspect that poster is of the [Gimme the Codez] variety - so I wouldn't let it bother you Ed
It's hard to believe there are nearly 11 million Code Project members now. It makes me feel old to be member 29062. Almost as old as you! :) Not quite the close-knit community of the golden days.
-
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?
You can always downvote the posting, then explain why. Maybe a downvote or two will be enough to convince people not to downvote without good reason. Or maybe it'll start flame wars. Who knows?
I wanna be a eunuchs developer! Pass me a bread knife!
-
You can always downvote the posting, then explain why. Maybe a downvote or two will be enough to convince people not to downvote without good reason. Or maybe it'll start flame wars. Who knows?
I wanna be a eunuchs developer! Pass me a bread knife!
Mark_Wallace wrote:
downvote without good reason
Members can vote any darn way they like. And so they do.
-
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 for 99.99% of the cases it makes no sense to include an .exe in an article explaining/discussing some code.
Try Hovercraft for Android, voted "a game" by players.
-
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 usually don't add exe files to the downloads, for the reasons you have mentioned and most of my stuff is something where the source code is much more important than an executable.
The console is a black place
-
I agree; most articles should not include an EXE. Only one of mine does. 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. Only include the code and the article text; let the reader decide how to use it. Anyone who can't figure it out probably isn't worth your effort.
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
-
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.