It would be really nice if this issue was fixed - I've been hitting it for quite a while. I think there may be some tags associated with the article stored in the database that are not shown on the page, which could explain why it complains.
is there an easy way to check that out without havin to register over there to post a comment in the original blog?
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
It would be a little weird to share someone else's blog feed, then claim the first post that came through as your own. It would be the first time I've seen it. But to be safe, I've left a comment on the original blog post.
I know for our blog entries we have a minimum word requirement. I'm not sure if the same is true for GitHub projects. That said, this project readme wouldn't quite meet our submission guidelines. Would you be interested in submitting this instead as a full article?
CodeProject articles have a certain layout to follow, so that users can learn the most from them. Each article attempts to answer the following questions: What problem does this solution solve? How does this help someone else? How does the code actually work? What is going on inside the code snippets?
Here is a submission from a first time author who did a terrific job, just to give you a basic overview of what a beginner article might looks like: Avoiding InvokeRequired[^]