|
Well done, thank you
|
|
|
|
|
If I make a neat tool that I think adds a lot of value for Visual Studio programmers, and that I do not want to charge people money for it --- rather, in order to make the world a better place, I just want to fling it out there, along with its source code and corresponding GitHub repo, would it be acceptable to write a The Code Project article about it, describing why I wrote it, its feature set, how to use it, and such?
|
|
|
|
|
|
CodeProject is more about knowledge-sharing rather than it is tool sharing. I actively remove articles deemed as tool-sharing from the site. The proper way to post this would be to write an article about your tool. Share the code, how it works, why you made it, what you learned along the way, interesting bits of the full source code, explaining concepts around the code and why you made those decisions. Basically turning your tool into a class lecture and explaining it in a way that the whole class can understand.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Yes, Sean,
Quote: Share the code, how it works, why you made it, what you learned along the way, interesting bits of the full source code, explaining concepts around the code and why you made those decisions. Basically turning your tool into a class lecture and explaining it in a way that the whole class can understand.
Maybe I was not communicating well enough, but that was exactly what I was intending to do. The only issue is, each tool has over 100 Visual Studio projects as part of its solution and is written in a production-level fashion. I assume a multi-part article series would also be acceptable, so I did not have one really huge article covering the gamut of the effort. Would that also be acceptable?
Regards,
Brian Hart
|
|
|
|
|
I guess it depends on how many multi-part we're talking. Five parts is OK. I'd say that's a good and reasonable maximum. Otherwise huge article is totally appropriate. Members even seem to like it.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Like the subject line says, that is my question.
I've been a member and author on the Code Project for 24 years. I do not want to do anything wrong, but I think it is important to try and get eyeballs if I feel I've published something that is going to be of interest to the community.
Regards,
Brian Hart
|
|
|
|
|
Everyone who publishes something online wants/needs eyeballs. I certainly appreciate and understand that. But I think the method by which you try to get those eyeballs matters.
The Lounge is not meant to be a place to share your recently published article. Doing so could be construed as an ad, which is against the Lounge's policy.
If you've published something that is going to be of interest to the community, the content will speak for itself.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
Well, consider the situation where everyone who wrote an article, including the hundreds of spammers, decided to promote it in the Lounge.
|
|
|
|
|
That's fair.
But if I worked really hard on a long article, and I want people to know about it ("ta da, here's this really cool, informative article I wrote and humanity will be better for the knowing of it") why can't I make a mention of it.
|
|
|
|
|
Some authors put a link to their latest article in their signature. Do that if you want to drive people to your article.
|
|
|
|
|
@sean-ewington, we have an article posted[^] with a link in to a Youtube channel. The author says he might be remunerated for this. This feels like spam to me.
|
|
|
|
|
Whatever the reasoning for that link, it has been removed.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
The latest public revision of my project article is 6. However, there are revision 7 and 8 in composing state. I want to delete revisions 7 and 8, and only have revision 6 as the last/latest one. How do I delete just the 2 revisions that are in the composing state?
What I have tried:
If I select the "trash can" link, I get a prompt with:
"Are you sure you want to delete this Project?"
No... I don't want to delete this project. I only want to delete the last 2 revisions that are in composing state.
|
|
|
|
|
I don't believe you can delete revisions, unfortunately.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
|
This was submitted as a Project:
How to implement a Custom Authorization Filter in C# .NET Core[^]
I noticed that several experienced reviewers have flagged it as "Wrong type". What am I missing? There are many Articles that should be Tip/Tricks, but I thought pretty much anything could be a Project if it discussed a repository, unless the documentation was poor enough to simply reject it.
|
|
|
|
|
Project type submissions are actually supposed to be the same full-fledged articles; a thorough explanation of their code, how it works, why they made it, etc.
Unfortunately, most of these Proejct submissions are just people sharing their GitHub projects, which is totally understandable. If it were me, that's what I would expect. What usually happens is this gets into the realm of tool sharing, which is not what CodeProject articles (or CodeProject) is about. So sadly, I delete most of these submissions, while offering to the author, "hey, we'd love to have this if you were able to make these additions."
If I had to guess, these reviewers are flagging this article as "Wrong type" because they want it to be a tip. My experience is that reviewers feel like anything that's short, or simply "not good enough to be an article" should just be a tip. Like a dumping ground of sorts. "This is good, but not article good, so, it can stay, just over there." But what tips are supposed to be is essentially extremely condensed articles. You still have to explain your code, what you're doing, why you did it, but it's a short solution to a simple problem that doesn't require / ask for in-depth explanation. Here's a recent, perfect example:
Access your Microsoft JSON DOM the easy way with the dynamic keyword[^]
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|
... me, I'm still searching for one. I don't like using the article writing tool from scratch because I write slowly and revise a lot. I am quite happy with writing my drafts using Markdown in VSCode but when it comes to importing them in CP tool, there is no easy way to do it. The "Markdown All in One" extension in VSCode has some kind of "export to HTML" function but it doesn't play nice with CP styles specially for code formatting.
Is there a way to import directly markdown in CP? Do you have other insights how to make writing/editing easier?
Mircea
|
|
|
|
|
I asked about using Markdown in articles a few months ago. It looks like it's going to be a work in progress. Right now, this capability doesn't exist.
|
|
|
|
|
|
Yes, I have that one but writing in HTML is painful or I haven't found a good HTML editor.
Mircea
|
|
|
|
|
I liked Editpad a lot when working with HTML some years ago.
I stopped using it in 2017 though, so I do not know how the current versions will be.
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.
|
|
|
|
|
yes im interst in workflow.
|
|
|
|
|
I'm always happy to post the article for you, as an option.
Thanks,
Sean Ewington
CodeProject
|
|
|
|
|