When to use AndAlso vs And ?

  • Thread starter Thread starter Guest
  • Start date Start date
real quick-- my 7 machines; how do i determine which versions of the
framework I _PROBABLY_ have installed on these 7 machines? keep in
mind that it is 3 different operating systems :)
Click to expand...
<snip>

I'm not fortunate enough to have even 3 machines, let alone 7, but I
can just navigate to C:\WINDOWS\Microsoft.NET\Framework and sure there
it is:

09/11/2006 00:20 <DIR> .
09/11/2006 00:20 <DIR> ..
05/11/2006 02:07 <DIR> v1.0.3705
05/11/2006 04:33 <DIR> v1.1.4322
13/12/2006 23:04 <DIR> v2.0.50727

Is there something that I am missing? I mean, in good old VB.Classic
days I had much more trouble finding what was the installed version of
ADO and what I had to download to keep it current (I must say that I
didn't use ADO much, so when I did use it the dificulty synchronizing
the deployment machine(s) was significant -- or so I recall).

Regards,

Branco.
 
in the good old days.. did it even ****ing matter what version of ADO
you were using?

Seriously

2000 shipped with 2.5 and XP shipped with 2.6 right?

other machines all had 2.1 with the release of IE4.. right?

you are missing something; you got your head on backwards

-Aaron
 
I've got several dual-boot machines
Click to expand...
<snip>

Forgive my ignorance, but how does this inffluence anything in finding
the installed version(s) of the .Net framework?

Regards,

Branco.
 
Unless you have a desired side effect of all parts of the expression getting
performed reguardless so that a function gets called.

However,

This sort of "side effect" programming, is questionable at best and can be
harder to debug for others. Usually it's best to short circuit.

This is a great addition to VB and I use it alot.
I used to have to jump some whoops to use AND because each item would get
evaluated reguardless.

For example:

If not objectX is nothing AND objectX.method=something then

This would blow up if objectX was nothing, because it would always try to
hit part two of the condition.

The same thing written like:
If not objectX is nothing ANDALSO objectX.method=something then

would have no problem because if objectX is nothing then it would stop
before trying to access a method/property on it.

-Shane
 
because C:\Program Files or C:\Windows doesn't point to the correct
instance

the point of the matter is that there is not a simple way to determine
the current version of .NET framework on any of these 8 machines.

THUS, .NET deployment is absolutely, prohibitively-- unreasonable.

If every single machine in the world had .NET 3.0 then everything might
peachy-- if it didn't run soooooo goddamn slow.

but as it is; they're never going to make 3.0 run on Windows 2000 so
they can eat a dick sandwich

there is a better place; it is called PHP, MS killed VB, sorry guys

-Aaron
 
I don't have a desired side effect.

shit worked fine in the past.

unnecessary change is not GOOD. it is not WANTED. it is not
ACCEPTABLE.

-Aaron
 
because C:\Program Files or C:\Windows doesn't point to the correct
instance
Click to expand...
<snip>

I stand corrected: the simplest way to check the installed .Net
frameworks is to navigate to %windir%\microsoft.net\framework.

Regards,

Branco.
 
Back
Top