I have an article on IEnumerable in C# (published).
I have the same thing in VB, (unpublished).
Typically I don't like reading articles with one set of code in the article and two downloads or two sets of code in the article (usually C# and VB), I find it distracting and confusing.
Particularly for IEnumerable where there are meaningful, not just semantic, differences (to my eye as a beginner).
So, should I post an alternative to my own article or a second article?
And does it matter?
It's all a matter of choice, but it's often easier to put both sets of code in the same article. There is a little link at the top of each code block in the finished article so the reader can hide the parts he/she does not want to see.
A while ago I attempted posting my first CodeProject Article. Sadly my article got rejected, accompanied by rather negative/dismissive comments, not all though.
I then proceeded to post my article and sample source code on MSDN, to date the stats indicates the sample source code being downloaded around 400 times. In other words, a potential 400 page views that could have gone towards CodeProject.
My question being: Are there any concrete rules defined around whether or not to reject an article?
Thanks very much for your inquiry. Sometimes articles are rejected because they cover ground already well-trodden. While we appreciate the efforts of all authors, we do try to keep content fresh on CodeProject (which, admittedly, is difficult to ensure with community approval).
We're always happy to look over your idea before you begin writing, or even have you work with a CodeProject Mentor if your article needs a little boost. You could even post your article idea in this forum and get some feedback from the community. We're very happy to work with you to get your article topics chosen, and your articles approved and posted.