How do you deal with cases where a user asks a naive question expecting a nice simple solution to a complex problem, but then isn't happy with an answer that exposes the true difficulty of the problem.
For example: How do I easily create a VS extension to do X? (let X be some non-trivial task)
Of course, there often isn't a very easy solution- the user will have to build a Visual Studio extension, implement a handful of ugly IVs* interfaces, etc.
Lets say I spend some time explaining the scope of the problem and provide resources for getting started with a pretty big task. In most cases I'll get a response back with something like "I really wanted something simple".
How do you deal with cases where people asking these sorts of questions really don't want to see an answer that will make them learn something new? The question will likely never be answered again because there just isn't a simple solution to these sorts of problems. The answer will never be accepted because the user wasn't happy with it. Nobody wins!