ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.
One of a set of tools we're offering as a way to say thank you for being a part of the community.
Case sensitivity difference between .NET 2.0 and 4.0
x = "Test"
If x = "test"
do abc
Else
do efg
End if
I have proven the above code works differently between my .NET 2.0 and .NET 4.0 console apps.
.NET 2.0 console app will execute abc.
.NET 4.0 console app will execute efg.
Why doesn't the 2.0 app do the same thing as the 4.0 app? Is there a configuration that says to not worry about case sensitivity or something?
If x = "test"
do abc
Else
do efg
End if
I have proven the above code works differently between my .NET 2.0 and .NET 4.0 console apps.
.NET 2.0 console app will execute abc.
.NET 4.0 console app will execute efg.
Why doesn't the 2.0 app do the same thing as the 4.0 app? Is there a configuration that says to not worry about case sensitivity or something?
Asked:
-
3
2
1 Solution
Bingo. The 2.0 app had Option Compare = Text instead of binary.
I changed it, and the code is executing like the 4.0 code.
thanks for your prompt response!
I changed it, and the code is executing like the 4.0 code.
thanks for your prompt response!
Actually, although it solved your problem, the information given by Fernando is not quite complete.
Option Compare Binary compare the binary values of the characters, their Unicode value, which makes it both Case and accent sensitive. The results are thus the same no matter the system on which it runs.
Option Compare Text follows the language specified in the Control Panel, and will thus change depending on the language. Most languages are case insensitive, but many are sensitive to accents. The results might thus be different from one computer to another.
The best way to compare strings is to use the String.Compare method. It has overloads that let you specify the case sensitivity and the language to use for everything else, so it is the only way to be assured of always getting the same results in a given application.
Option Compare Binary compare the binary values of the characters, their Unicode value, which makes it both Case and accent sensitive. The results are thus the same no matter the system on which it runs.
Option Compare Text follows the language specified in the Control Panel, and will thus change depending on the language. Most languages are case insensitive, but many are sensitive to accents. The results might thus be different from one computer to another.
The best way to compare strings is to use the String.Compare method. It has overloads that let you specify the case sensitivity and the language to use for everything else, so it is the only way to be assured of always getting the same results in a given application.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
By default string compare are case sensitive unless it has been change to case insensitive. This is done by setting the following statement at the top of the code file:
' Case insensitive compare
Option Compare Text
' Case sensitive compare
Option Compare Binary
If the above is not in the file at the top then in the project configuration on the Compile tab the Option compare Combobox is set to Text
Please check your setting as stated above.