Report a bug
From Sense/Net 6.0 Wiki
In this section you'll find the basic guidelines on reporting errors you may encounter in Sense/Net 6.0.
You can report the bugs you found at the forum.
[edit] The basics of bug reporting
The first goal of a bug report is to let our programmers see the error with their own eyes. If you can't show us the failure personally, please provide us with detailed instructions so we can reproduce it.
The second goal is to describe what went wrong. Describe everything in detail: when did it happen, how did it happen. State what you saw, and what you were expecting to see. Include any error messages you might have got. Don't forget to inform us of the configuration of the client and the server computers, including the version and make of the operating systems and browsers you used.
Our programmers might ask you for additional information. Please do not think of this as unnecessary pestering or excuses to leave the problem unfixed - they might need information that you have overlooked as unimportant or trivial. Have the detailed version numbers of all software involved (operating systems, .NET framework, IIS, browser, etc.) at your fingertips, as this information can be of key importance.
In case you managed to diagnose (or even fix) the problem yourself, please do us a favor, and still send us a detailed bug report with the entire scenario necessary for reproduction of the bug, and your diagnosis and/or fix as well.
[edit] Things to keep in mind
- Before reporting a bug, please check the Known Issues. Chances are, it could have been found already, and there might be a workaround for it.
- Be clear. This is essential in a bug report. If we don't understand you, we can't fix the bug.
- Be specific. State what you did and how you did it. Don't write "I logged in". Write "I entered my name and password into the login box on the left of the main page, and clicked the Log In button" instead.
- Be verbose. It's always better to give too much information instead of too little. If the information you provided isn't enough to reproduce the problem, we'll have to contact you for further specifics. This takes time, and is an unwanted hassle both for you and for us.
- Be wary of pronouns. Keep down on the use of "it", and unclear references like "the window". What is trivial for you might be ambiguous for someone else. A clear bug report tends to have lots of word repetitions - your concern should be understandability instead of style. If in encountering the bug, you did five things with the "tree view in the content explorer", you might want to write down the phrase "tree view in the content explorer" five times to be clear. Please do so.
- Make screenshots. A picture is worth a thousand words. If you can make a screenshot of the problem you encountered (with visible signs of the malfunction), attach it to you bug report. It will help us a lot.
- Write processes in steps. It is easier to understand how you got the error, if you use numbered, short sentences to describe what you did.
- Read what you wrote. Read the report back to yourself, and be critical. If you saw this message for the first time, would you be able to reproduce the bug using only what is written?
