We are all here pure volunteers. We do not have time or motivation to do Google queries for you.
In case you do not know how you can search the web for any infos you might need you maybe want to read this article[^].
Neither we are machines or heartless geeks. Anyone understands when your first question is not too good and some info went missing while asking. But for the future: Consider these guidelines[^] when asking a question.
And the most important thing: Be polite and use punctation marks.
Nutshell: ASP.NET does NOT have any inbuilt API support to send out an SMS. You need to go for a third party solution or use something that is found on the Internet. Articles and discussions above should help you out.
AFAIK, Marathi uses same script as Hindi. In that you can't easily tell which language is used.
Easier way to detect language if your text is written using Unicode is by checking the character range. If the character range is in between the range for Hindi, you can assume it is Hindi. But you need to scan till the end and if all the characters are in Hindi, the word is written in Hindi. Your algorithm should also consider zero-width joiner and non joiners (ZWJ & ZWNJ) while scanning the input. I have done an implementation of language detection. You can find code here[^]. It is written in C but the concepts are same for any language.
I have a simple .aspx page. I wish I could attach the picture here.
I want to show the data either in Chart control or Gridview control. When the user selects an option to see the data either in chart control or grid view control, that specific control has to show up and other control has to become invisible.
So far, I am able to populate data succcessfully in the chart control. If the user chooses "Grid view" option, how can I show the data in grid view control in the same location. I don't want the gridview control to be shown in a pop up window or any other window.
This is a well-known issue with WebParts. It was fixed in the "ASP.NET Futures CTP (July 2007 release)", but for some reason the fix was never added to the framework. The CTP is no longer available, and you wouldn't want to use it in a .NET 4 project anyway.
The problem was reported to Microsoft[^], but they closed it as "won't fix" because it was too complicated to implement.