1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions. Or if you must, use the Back Room[^] - but enter at your own risk.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen. For those discussions where you wish to be a little more frank, use the Soapbox[^]
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
A driver was stuck in a traffic jam on Pennsylvania Avenue Washington DC . Nothing was moving.
Suddenly, a man knocks on the driver's window.
The driver rolls down the window and asks, "What's going on?"
"Terrorists have kidnapped all of our politicians during a sitting of parliament, and they're asking for a $100 million ransom.
Otherwise, they are going to douse them all in gasoline and set them on fire.
We are going from car to car collecting donations."
"How much is everyone giving, on average?" the driver asks.
The man replies, "Roughly two gallons."
New version: WinHeist Version 2.1.0 Beta
There's a fine line between crazy and free spirited and it's usually a prescription.
I'm currently unsupervised, I know it freaks me out too but the possibilities are endless.
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?
The Code Project.
I wonder which part he didn't understand
Wrong is evil and must be defeated. - Jeff Ello
Any organization is like a tree full of monkeys. The monkeys on top look down and see a tree full of smiling faces. The monkeys on the bottom look up and see nothing but a**holes.
That person does not have C++ in their profile so may have trouble compiling the project like I would.
Several places will not allow downloading files with .exe in them so you could always upload a version with and with out the .exe or a seperate file with just the exe for download for those that would like to test it as is.
Some like to view how a program works before digging into the code. If it crashes then they may not bother viewing the code.
I personally forget to remove the .exe from my projects before uploading them after spending so much time on the articles.
Yeah, I know including an EXE used to make things easier. But with Vista/Win7/Win8 security features blocking executables or demanding admin privilege, with various 64 bit and 32 bit architectures, with multiple versions of .NET possibly requiring download and installation, it doesn't seem like a good idea anymore to include an EXE that may only run properly on some systems while crashing on others.
You are right about that, the only way that would work is if version checking was built in so it would not just crash, but throw a error stating it needs version x or admin right to run properly on OS version X or .Net framework X.
There's usually no point in providing an EXE, because usually it's just an example anyway. The point of the example is showing how something works, not to provide a useful application. Some articles may come with a useful application, but usually that makes no sense to do.
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.
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.
I suspect I just lost an approximate 30 hours worth of work. I decided to play around with the CodeProject API, and of course did that on my dev VM (which runs on my iMac - no comments on that. Please.) - I was updating it (the VM that is, not the iMac) to use Ubuntu 14.xx, and all of the sudden the whole HOST OS hung up, crashed to leave the VM in unusuable state. Yes, uploading everything to an SCM was on the todo list
Update: I'm now setting up a second VM, praying to be able to mount the old virtual hdd and rescue the data.