If you have a problem with something in a tip or article, ask the question on the forum at the end of that tip/article. It's highly unlikely that the author will just happen on by this forum looking for questions about their article.
As a Code Project tip, asking questions in the right forum is the fastest way to get an answer. If you ask questions in the wrong place, you end up wasting your own time, waiting for us to answer with anything other than a "this isn't the right forum" answer.
I was brought up to respect my elders. I don't respect many people nowadays.
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?
Last Visit: 31-Dec-99 19:00 Last Update: 29-Nov-23 5:13