{
}
PingBack from http://asp-net-hosting.simplynetdev.com/c-case-insensitve-string-replace/
Don't you think that iteration would be better than recursion for this?
The reason I go for recursion because it is easier to understand and maintain.
If you use live.com to search, you could see that there actually have other faster solution available already. However, they are pretty complicate, it may be useful if you required to use that function frequently. If you only use this function rarely and the project will get touch by multiple developer, usually simple solution is better than complicate solution.
use String.IsNullOrEmpty instead of inputStr == null || inputStr.Length == 0
Yes. I should use String.IsNullOrEmpty instead of checking whether the string by myself.
Old school programmer. ^_^
