Gary Chefetz has made an interesting post over at ProjectServerHelp on how to write a great post when you look for help in the Microsoft communities newsgroups. He makes several interesting points:

• Always include version information
• If possible, always include specific error information (preferably a stack trace or direct copy from the event/ULS log
• Include information about any troubleshooting performed to-date
• Do not assume that similar error messages equate to similar problems, since software tends to use “catch-all” errors for many problems.

As someone who frequently answers questions in the newsgroups, I think that these are all very important. They cover some of the biggest timewasters in the newsgroups (for both users and experts alike). When posting, try to follow his advice — doing so should help cut down on the time-to-resolution for users seeking assistance in the newsgroups.

You can check out his post here.

Popularity: 66%