Thread-jacking is the practice of appending your question to an existing thread in a forum or news group. This is a relatively common practice among newcomers, and while you obviously weren't to know, it is discouraged. People thread-jack for two main reasons:
Chances are that you found the thread as a result of using the Forum's search facility or Google, which is an excellent start to getting your problem resolved. However, if your question is the same and the thread is current, then you should wait until the thread is resolved at which point you should get the answer to your problem. If your question isn't answered by the end of the thread, then it must be a different question, and therefore should require a new thread of its own. If you want to reference an old thread or post, then start a new thread and post a link to the thread that contains the solution you are trying to implement.
Adding your question to a current thread might be considered very rude. It's a bit like walking in on someone else's conversation and shouting "What about me?". If anyone answers your question the thread is likely to get very confused, and no one will be quite sure who is addressing which problem. Try following this thread which illustrates the problem pretty well.
Resurrecting an old resolved thread (necroposting) reduces your chances of obtaining help. A lot of people who provide help are watching for unresolved posts, and will ignore a resolved one that has suddenly come to life again. Also, a lot of answerers at forums.asp.net are "points-conscious", in that if their reply to a thread is "Marked As Answer", they are awarded extra points. However, only the person who started the thread has the facility to mark posts as answer. Since you didn't start the thread, there is no motivation among this group of answerers to help you, because you can't Mark As Answer on someone else's thread.
Thread-jacking might also be seen as a way of avoiding the delays that sometimes occur while a post is being moderated for approval. This can be frowned upon too.
So, start a new thread. But before doing so, consider the following general guidance:
 "Relevant" code means sufficient to see the line that produced the error in context, or enough for people to create a sample page to test themselves. 792 lines of aspx mostly composed of styling information is enough to put anyone off reading your post.
Speaking of styling, if you don't know how to use external CSS files yet, you really are better off getting your page working properly before spending hours fiddling around with the Properties panel to format your various controls, especially if the result of the error you get means you have to replace controls, or the page entirely.
*Delete as appropriate
**Ok, so that's a personal bugbear of mine :-)
Tuesday, November 13, 2007 12:33 PM
Last Updated: Sunday, December 23, 2007 11:01 PM
Posted by: Mikesdotnetting
Total Views to date: 869637
Unfortunately, something went wrong and your message or comments have not been submitted successfully. I'll try to fix whatever the problem is as soon as I can.
Thanks for you comments. They have been successfully sent to me. I will try to respond if necessary as soon as I can.