Option Strict by default

[TechnoTone]

Ive searched these forums and found lots of references to Option Strict, most of which say that you should turn this on for all projects. However, I cant find any way to turn this on by default. Is it possible and if so, how?

wyrd mentioned writing an add-in that automatically sets Option Strict to On and removes the Microsoft.VisualBasic import. I cant find any reference in the online help regarding add-ins - how would you go about doing this?

 

[Divil]

The only thing I can think of is finding the new project templates (theyre there somewhere) and modifying them.

 

[TechnoTone]

Ive already checked them (thats where I removed the references to the Microsoft.VisualBasic namespace) but Option Strict/Explicit isnt there.

I have been wondering whether you could do something with the scripts in the VBWizards folder but its a little daunting to me.

What about the Add-in idea? Any sources of information on writing add-ins?

 

[Divil]

I had a quick go, and I was able to do this. I opened the file:

\VS.NET\Vb7\VBWizards\WindowsApplication\Templates\1033\WindowsApplication.vbproj

And added the line:

OptionStrict = "On"

Just after the OutputType = "WinExe" line.

 

[TechnoTone]

Nice one. Not seeing Option Explicit there I figured it wasnt the correct place. I guess Option Explicit = "On" is a default anyway.

Thanks.

 

[Volte]

On a side note, removing the reference to Microsoft.VisualBasic is
useless; it is required regardless, and will be referenced anyway.

Besides, theyre not all bad anyway.

 

[TechnoTone]

Originally posted by VolteFace
On a side note, removing the reference to Microsoft.VisualBasic is
useless; it is required regardless, and will be referenced anyway.

Besides, theyre not all bad anyway.

Are you sure about that? It works on mine!

 

[Derek Stone]

You can remove the imports statement but you cannot remove the reference. The Visual Basic .NET compiler (vbc.exe) will add the reference regardless, whether a project is compiled from Visual Studio or from the command line. This shouldnt be a concern to anyone however, since the Microsoft.VisualBasic assembly is distributed as an integral part of the .NET Framework.