I suggest SO to show warning messages for VB.NET questions being answered with C# solution or vice versa.
closed as off-topic by Nathan Tuggy, S.L. Barth, Werner, Glorfindel, rene Dec 22 '16 at 8:33
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This question pertains only to a specific site in the Stack Exchange Network. Questions on Meta Stack Exchange should pertain to our network or software that drives it as a whole, within the guidelines defined in the help center. You should ask this question on the meta site where your concern originated." – Nathan Tuggy, S.L. Barth, Werner, Glorfindel, rene
I believe the community is well enough capable of policing this kind of issue on its own.
Since we're in the land of .NET, many times a C# answer will in fact be sufficient to get the VB asker past a particular problem. And the C# answerer is already often enough saying "sorry, this is C# code, I'm not entirely sure of the VB syntax" or some other such disclaimer.
Expanding outwards to cover the non-.NET universe, if the answer is indeed in the wrong language and it does not assist in answering the question, that's where we have downvotes. But if the answer helps move the needle, then the language itself is not a problem. It could even be pseudocode, for all we care.
Then next we'll have warnings for C and C++, fizz and buzz .. boom and bang .. where is it going to stop .. lisp and fainbruck?
I think this kind of automatic rejection / warning is just a bad idea, globally. It's way more expensive than it's worth.
Considering they are using the same framework, and answers usually aren't that complex, it should be well within the abilities of any programmer to translate an answer from one .NET framework answer to another.
Even for VB.NET developers.