I've asked for a review on the way that I'm populating some comboboxes in a datagrid. One commenter asked what the purpose of the application was. Are those comments really relevant to a code review? In my particular case, I'm asking if my method is effective, or if there is a better way. The purpose of the overall application, I feel, has no bearing on the outcome of the question. I'm not trying to be a jerk, I just feel that comments like this aren't really relevant, and are non-conducive to what CR is supposed to be about.
We allow posters to bring a wide array of issues with respect to your code. They are not restricted to simply answering the problem as you see it. A good portion of the time, people come here with ugly code because they've taken the entirely wrong tack to solve their problem. As such, understanding what they are actually trying to do can actually be quite important. Often once that's understand we can suggest something way better.
In your case, the commentator is raising questions about the UI. That is straying a bit off-topic because we don't typically do UI reviews. But comments have more lee-way in being off-topic then answers. He's pointing out that your UI choices seem a bit odd. That's some feedback on your UI, feel free to take or leave it.
Knowing the purpose of code is not just relevant, it is essential in order to properly review it.
Code is only a means to the end of solving someone's problem. If we don't know what that problem is, we can't say whether the code is going to be any good at solving it. All we can offer is a "generic" review which is much less useful to you and much less interesting for us.
What is your problem exactly? Please add more context. Is there a reason you use strings? Is there a reason you use observable collections? Are those collections supposed to be unique per item? Stuff like that. It's hard to tell from your code what behaviour you are trying to achieve, so it's hard to give you proper advice.