1.If the receiving party knows how to implement it, don't post all the code.(For example, an error)
2.If the receiving party is a beginner, should show the whole project demo to him.(For example, don't know how to write the implementation code.)
3.When you reply to a specific sentence, you need to add >> in front and italic-bold display.
4.Use comment with ... to omit unnecessary existing content or other possible operations when replying with code.
5.Comment out the wrong code, then add the correct code after commented-out code.
6.Note the specification of the format, such as punctuation (in English), spaces, etc.
7.Make it clear when you don't understand the specific needs
8.Firstly point out the problem and then provide a solution
9.Non-Microsoft links, add third-party statements
Note: This response contains a reference to a third party World Wide Web site. Microsoft is providing this information as a convenience to you. Microsoft does not control these sites and has not tested any software or information found on these sites; Therefore, Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. There are inherent dangers in the use of any software found on the Internet, and Microsoft cautions you to make sure that you completely understand the risk before retrieving any software from the Internet.
10.Don't be careless, such as providing the wrong content when replying
11.If the OP still follow the case that has been solved, reply with the following statement
I think this problem is different from the original question, and I noticed you also post a new thread for this new problem, so please close this thread if your original question is solved by marking the helpful reply as answer as this will help others looking for the same or similar issue down the road.
12.Reply to a case unrelated to the current forum
This forum is discussing and asking questions about the Windows Form and ClickOnce, it will be more appropriate to ask your question at Microsoft Community.
Thank you for your understanding.