Option Strict On

[kleinma]

Do you guys use it? I read in a VB.NET book that its highly recommended because it just makes for better code. It is somewhat of a pain in the ass because you have to convert values constantly from string to integer etc.

I have been using it just because of the general rule that its good practice. I would have to image most people DONT use it though

[crptcblade]

I don't use it because I feel that VB wasn't meant to be strict. If I want to deal with all the casting and conversion stuff, I use C#. If I just need to put something together and prove that it will work, I use VB without Option Strict.

[kleinma]

well being that im not a C# programmer, would you suggest using it for at least the production apps i build?

I agree if im just doing something for fun or for testing I wouldnt bother

[techgnome]

I use, and I'd recomment using.... same with Option Explicit On.... but to each their own.

TG

[alextyx]

I use Option explicit but not option strict, also if often I try to write code as if option strict was ON. I prefer to be free to choose. Sometime is too comfortable don't have to respect that rigid rule!

[VBGuy]

I don't always use it because I have apps that use late binding to an Excel COM object and you can't late bind with Option Strict ON.

[kleinma]

well its at the moduler level right? not the project level. so you could turn it off in a module that needed late binding or something like that

[salvelinus]

I use it because it helps me understand/learn .Net better by forcing me to realize some of the mechanics of what's going on.

[TLord]

I use option strict on.

It just makes my code better and cleaner.

[SuperSparks]

I always use Option Strict On, even though it can sometimes be a royal pain. It all helps with the learning process, and you get better code at the end IMHO.