A user had recently asked a question about having relative paths in visual studio build events. He came to the conclusion that it just simply wasn't possible after an answer offered by another. That's fair. I was about to offer a workaround but found that the author deleted the question in response. The user now asks a different question which appears to be dependent on the last one. No fault there IMO.
What is the proper way for me to communicate to him that I have a workaround solution to his previous question?
Prior to his second question, I was looking for ways to somehow communicate with him. Since in-site private messaging will not be implemented, I thought about commenting on a random question of his but to me is not a proper way to communicate this. I could probably leave a comment on his new question mentioning it, but it feels awkward communicating this way. I was tempted to answer in his new question not offering a solution to the new question (as I'm not sure how I can answer properly) but just referencing his older question. As a last resort, I was going to "ask" his question again and immediately answer with my workaround in the hopes that he would see it.
What steps should I take? Is there a more practical and proper way to get my message through? What would the community suggest I do?