Possible Duplicates:
Etiquette for answering your own question
Should I answer my own question, or not?
I want to post a question on which I've done already quite a lot of research. I want to know the opinion of some experts on SO to see what solution (or possibly another one I didn't mention) they prefer and why.
which of the following is better:
1 I post the question and possible answers all in the main question body?
2 I post the question and a few separate answers?
3 I post the question and don't mention any answers at all?
some comments:
If I use method 1, I'm not using the system as it should be used, since no one can vote on the answers. If they want to vote they have to copy the answer (maybe reword it) in a separate answer
With method 2 I guess it could work. But I'm not giving anyone the moment in the bright light to own the answer and perhaps even defending it.
With method 3 people start giving answers but I have to comment that I already know them and perhaps give my negative (or positive) points about them. I can remember that Jeff once said that it is better to show that you did your homework IN the question, so that people see that you actually did some work before turning to the community and just asking questions. So point 3 seems like to exact opposite of this idea.
Any ideas?
(If I go with method 2, how do I make sure people have not already answered before I markup my answers?)
EDIT: To make the question mare tangible. I want to ask what people see as the best way to do asynchronous programming in .Net. One can use the task parallel library, use delegates and the begin/send pattern, use the CCR (robotics) and iterators style programming, etc etc.
loads of possibilities. I just want to see what others are going with and what they perceive as (dis)advantages