Solution Properties

  • Thread starter Thread starter VJ
  • Start date Start date
V

VJ

I have a VS.NET2003 Project1 under Solution1, for this the Option Strict is
off. It is a huge project and would be impossible to make sure it meets the
Option Strict on conditions. We are developing a new project/sloution in
which Option Strict is On..

Do I have to everytime open each solution, go and change this in
Tools->Options and compile the code?.. Really it is painful to do this..
Anyway out??

VJ
 
* "VJ said:
I have a VS.NET2003 Project1 under Solution1, for this the Option Strict is
off. It is a huge project and would be impossible to make sure it meets the
Option Strict on conditions. We are developing a new project/sloution in
which Option Strict is On..

Do I have to everytime open each solution, go and change this in
Tools->Options and compile the code?.. Really it is painful to do this..
Anyway out??
Click to expand...

Yes (if you don't write a script to automate that). I prefer specifying
'Option Strict' on per file basis.
 
VJ said:
I have a VS.NET2003 Project1 under Solution1, for this the Option
Strict is off. It is a huge project and would be impossible to make
sure it meets the Option Strict on conditions. We are developing a
new project/sloution in which Option Strict is On..

Do I have to everytime open each solution, go and change this in
Tools->Options and compile the code?.. Really it is painful to do
this.. Anyway out??
Click to expand...

What do you have to do everytime? The Option Strict setting can be changed
in the project properties.


--
Armin

How to quote and why:
http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html
 
VJ,
As Herfried suggested, I normally put Option Strict On & Option Strict On at
the top of each source file.

So for your huge project you can add Option Strict On at a source file by
file basis, rather then setting it at the project level.

I tend to prefer the source file level, as its obvious when you open that
source file if the intent is to have Strict & Explicit On or Off. Especially
when the source is shared with others...

Hope this helps
Jay
 
Hi VJ,

I like it as well to set "option strict on" as default.

I find the arguments to set that as well in top of the program strange.

I tend to the opposite and set Option Strict Off in top off in my programs
when it is explicitly meant not to use that. That shows that better in my
opinion.

However, I started this to open a debate if someone disagrees with me.

I am always willing to tell that I agree with the other when he has strong
arguments against this.

Cor
 
I too believe in having this at the project level, so you can't point write
some stuff that VB otherwise lets you do.. , no more claim of that VB is not
as good as C#. Hey even better you know, we get the equalness of C# plus all
the additional functions... , so I say we get 15% more salary than C#
guys...:-)

VJ
 
Back
Top