|
Hi ,
it seems something strange occurs on my tip https://www.codeproject.com/Tips/5284754/A-way-to-compile-C-code-for-Python-in-Visual-Studi , in the list of my tips do not show name and language. And nobody read it, ok may it's not so interesting but I can find it only by url.
Thanks
|
|
|
|
|
It looks like you haven't published it yet:
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
It seems that the original tip you submitted was closed. What you are looking at is currently a draft. If you'd still like to share this tip, I would recommend making some improvements.
CodeProject is more about code sharing rather than tool sharing. So we would ask you to make some changes to the article to discuss more how the tool works (showing and describing examples of that code) rather than telling us what it does.
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[^]
You can take a look at our article FAQ here:
CodeProject Article FAQ - Part 2: How to Post an Article on CodeProject [^]
For tips on writing articles, please see this article:
A Guide To Writing Articles For Code Project[^]
You can also see our submission guidelines here:
Submission Guidelines[^]
Please let me know if you have further questions.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
|
I can't see that it's broken. The content of the link element has the same format as in previous posts.
It's the same format as in the previous posts that have been pulled successfully by CP
|
|
|
|
|
|
It looks like it may be the <?xml version="1.0" encoding="utf-8" ?> that is at the beginning that is confusing things. If I remove that from the response from your site, then MS Edge can parse the feed.
Presumably, we could as well.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
or change the <rss> tag to a <feed> tag.
It looks like you have a mixture of RSS and Atom going on.
"Time flies like an arrow. Fruit flies like a banana."
|
|
|
|
|
Matthew,
I don't think the XML declaration is a problem, after all, RSS Feed is an XML format.
I also don't think that anything has changed on my blog website, so the feed is the same as in the past, when pulling the posts from it worked well.
I didn't post anything for a year, but that should also not create a problem?
I just deleted my blog from CP, and then added it again. This has triggered the successful pulling of my newest post. So the problem is not the format of the feed.
-Gerd
|
|
|
|
|
Speaking of not encoding things properly...
You forgot to HTML-encode the <a rel="nofollow noopener"> in your message.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
"Bugs and Suggestions" might give the idea to some people, especially people who are not native English speakers, that they can ask for help with their bugs here.
Changing it to "Site Bugs and Suggestions" might make it a little clearer. Of course, it's no guarantee that the behaviour will stop, but it's a small step.
Cheers,
Vikram.
|
|
|
|
|
It's already called that in the side-bar:
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Sure, the link is called that, but the forum itself is titled just Bugs and Suggestions.
Cheers,
Vikram.
|
|
|
|
|
The earlier thread was inappropriate for the Lounge and was either deleted by the user or admins.
Honey then started a new thread which has replies, but looks like some of the replies to the earlier one somehow came under Honey's main post.
CP_threads_mating - Album on Imgur
Cheers,
Vikram.
|
|
|
|
|
|
using (SqlConnection conn = new SqlConnection())
{
conn.ConnectionString = "server='servername';database=D_MART;IntegratedSecurity=True";
try
{
SqlCommand cmd = new SqlCommand();
cmd.CommandType = CommandType.Text;
cmd.CommandText = "SELECT PRODUCT_ID FROM PRODUCT_DETAILS";
cmd.Connection = conn;
conn.Open();
Console.WriteLine("Connection open!");
SqlDataReader sdr = cmd.ExecuteReader();
while(sdr.Read())
{
int PRODUCT_ID = (int)sdr["id"];
Console.WriteLine(PRODUCT_ID);
}
conn.Close();
}
catch(Exception ex)
{
Console.WriteLine("can not open connection!");
}
}
}
|
|
|
|
|
This is not the appropriate forum for this question. Under the Code Project logo at the top of the page, mouse over "quick answers" and click on "Ask a Question" in the menu that appears. Or use this link[^] and include "SQL" as one of the Tags.
|
|
|
|
|
Although I understand the point of removing the rep points from deleted items... the guy below could have a point.
If an article has been downloaded and upvoted and so on, but it gets so old that is really not worth to keep it online anymore... shouldn't the legitime reputation points awarded back in the day remain in the authors account?
If an article gets nuked due to spam, plagiarism or whatever other choice... then yes delete the reputation too.
In my opinion there should be a possibility to keep the points for something that just "aged" bad, without incurring in anything wrong with site policies.
I could imagine a button for the owner and / or staff that appears after X minimum time online and allows deletion without removing the reputation.
What do you think?
M.D.V.
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.
|
|
|
|
|
I agree there is a point. However, if points are kept, it should concern both negative and positive points.
However, that's only the authors side. I believe that a mechanism that would allow to close an article and clearly state it obsolete would be a good idea. All the article text should remain but the article would contain a clear statement that this idea/technology/approach is obsolete. This way the search engines would still find the content but when a reader comes in, she/he sees that this is something that should be avoided these days.
I think this approach would greatly help people that come in touch with something 'old' and don't yet know what to think about it or how to use it.
|
|
|
|
|
Wendelius wrote: but when a reader comes in, she/he sees that this is something that should be avoided these days. And how would that work? Spend a little time in QA and see how many "developers" are proliferating, not just bad, but seriously dangerous, code. If an article is not valid then it should be deleted for ever.
I do take Nelek's comment about the reputation points.
|
|
|
|
|
Quote: If an article is not valid then it should be deleted for ever. I would hope it wouldn't get through moderation in that case. Now, there's "not valid" for being dangerous and wrong, as you mentioned, and "not valid" for being obsolete, as Wendelius mentioned. The latter shouldn't be deleted, because legacy systems have remarkable tenacity. A few readers might even find such articles interesting from an historical perspective. But a comment noting their obsolescence would be a helpful warning to those doing new development.
|
|
|
|
|
But when the only text in the article is, "obsolete", it serves no purpose.
|
|
|
|
|
I agree that article without the original text servers no purpose. I also agree that if the article is initially bad it should not pass moderation or if it does, voting hopefully shows how bad an idea is.
What I mean is that over time things become obsolete and while I understand Nelek's initial post was about rep points (as was the first paragraph in my answer), I think it would be worth while to have a discussion what to do with obsolete articles.
Just an example, what about an article discussing about new features of a product version which nowadays is end-of-life and the features do not necessarily exist in newer versions. What if there would be an option to report such article as obsolete and if enough reports have been given, an 'obsolete' watermark would be added. Probably not the best way to handle such situation but some food for thoughts.
|
|
|
|
|
Wendelius wrote: What I mean is that over time things become obsolete and while I understand Nelek's initial post was about rep points (as was the first paragraph in my answer), I think it would be worth while to have a discussion what to do with obsolete articles. To be honest... My original thought was about the complain below of losing the points for an obsolete article.
But to be honest I like the idea of keeping a good article with the warning "this is old stuff" or even "obsolete" if the content deserves it.
M.D.V.
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.
|
|
|
|