Are you trying to reject anything with bad words, or change them to something like **** ?

If you want to replace, something like this will work:

protected string replaceBadWords(string testThis, string[] badWords)
{
foreach (string s in badWords)
{
string replaceWith = string.Empty;
for (int i = 0; i < s.Length; i++) replaceWith += "*";
testThis = testThis.Replace(s, replaceWith);
}
return testThis;
}

That takes in a string to test, and a string array of bad words and returns the 'cleansed' string.

This one will return a true if it contains a bad word:


protected bool containsBadWords(string testThis, string[] badWords)
{
bool output = false;
foreach (string s in badWords) if (testThis.Contains(s)) output = true;
return output;
}

but I don't recommend this method as it can be very ambiguous if you do not want to show the word. What if the user inputs assanine or something like that?
Permalink | Report

Have you set the ControlToValidate property so that it references the TextBox you're trying to validate?

As far as a smarter route, this seems like a good approach, this way you can validate without the extra overhead of a postback.
Permalink | Report

Don't forget to include the English town name "Sc--thorpe" in your tests.

I'd also recommend reading Jeff Atwood's article on the subject of obscenity filters, linked below.

EDIT: looks like Mahalo has the same problem with Scu nthorpe :D
Source(s):
http://www.codinghorror.com/blog/archives/001176.html

Permalink | Report