.NET languages follow the rule of type safety. Type safe means that you can’t just mix different types randomly during assignments. For example, the following line will not compile and causes the error message shown in Figure 1-8:
Dim aDifferentString As String aDifferentString = 1.23
Figure 1-8. Type safety in .NET enforces the rule that only equal or safe types can be assigned implicitly to each other.
By default, Visual Basic .NET simulates the non-existent type safety used by Visual Basic 6.0 and Visual Basic for Applications (for example, for macro programming in Microsoft Word or Microsoft Excel). You can (and should) change this ...