|Namaste Fresher-ji, (or, if you prefer, "Namaskaram," or "Vannakam")
Job searching can be frustrating, can take a long time, I know. It's important you try hard to not let a sense of disappointment cause you to withdraw from keeping your full energy involved with continuing to educate yourself technically, and to keep up the good personal habits (diet, exercise, social relaxation) that make you, in person, aware, alert, and socially agreeable.
Please keep in mind the profound words of Kabir: "rahi gulzar to phool khilenge," "where there is a garden, the flowers will come." If we do not take care of our own garden, who will ?
Since you have experience, evidently, teaching, I suggest you continue to do that in some way, even if it means volunteering somewhere, since, imho, there's no better way than teaching to continually sharpen and improve your own understanding of what you have learned yourself.
From your other comments, it seems like there may be only a few .NET companies in the area where you live. Have you considered relocating first to an area where there are more .NET companies ? Yes, I know that may not be possible, but you might consider at least a job-finding trip to that area ?
I would also suggest ... if you haven't done so already ... that you create a technical blog, and try and make it relevant to people working in .NET in your area.
While you may not like the idea of applying for an entry-level position, like QA tester, or tech support, that might be a way to "get your foot in the door" in a company you want to work for; once employed there, and known and respected, you might have the opportunity to make yourself known to other programmers there and eventually shift to a programming job.
best wishes, Bill
«I'm asked why doesn't C# implement feature X all the time. The answer's always the same: because no one ever designed, specified, implemented, tested, documented, shipped that feature. All six of those things are necessary to make a feature happen. They all cost huge amounts of time, effort and money.» Eric Lippert, Microsoft, 2009