vb.net running in debug mode vs. running the executable

[Brad Pears]

I have a vb.net 2005 project and have made a lot of modifications to it. The
project runs fine in debug mode. Now I want to implement it and first I am
running the executable on my machine to make sure it runs properly...
However, when I run it locally as an executable, I get no end to run time
errors - things like conversions from type string to integer etc...etc....
There's seems to be a billion problems all of a sudden.

I have option strict turned OFF in my development environment. Is it
enforcing all of these errors that would normally have been generated with
option strict ON when running as an executable? Is there a way to get around
it at all? I don;t understand why it runs perfectly fine in dev but bombs
out in a big way when running as an executable...

Thanks,

Brad

[rowe_newsgroups]

On May 22, 5:39 pm, "Brad Pears" <[e-mail]:

I have a vb.net 2005 project and have made a lot of modifications to it. The
project runs fine in debug mode. Now I want to implement it and first I am
running the executable on my machine to make sure it runs properly...
However, when I run it locally as an executable, I get no end to run time
errors - things like conversions from type string to integer etc...etc....
There's seems to be a billion problems all of a sudden.

I have option strict turned OFF in my development environment. Is it
enforcing all of these errors that would normally have been generated with
option strict ON when running as an executable? Is there a way to get around
it at all? I don;t understand why it runs perfectly fine in dev but bombs
out in a big way when running as an executable...

Thanks,

Brad

Why do you have Option Strict turned Off? In my book that is a huge no-
no. I'm not sure why they don't blow up during development, but you
should turn on Option Strict and fix them.

Thanks,

Seth Rowe [MVP]

[Brad Pears]

Yes, I think you are right - I will do that from now on.... They really
shouldn't even give you that option really...

Thanks, Brad

"rowe_newsgroups" <ro********@yahoo.comwrote in message
news:39**********************************@a70g2000 hsh.googlegroups.com...

On May 22, 5:39 pm, "Brad Pears" <[e-mail]:

>I have a vb.net 2005 project and have made a lot of modifications to it.
The
project runs fine in debug mode. Now I want to implement it and first I
am
running the executable on my machine to make sure it runs properly...
However, when I run it locally as an executable, I get no end to run time
errors - things like conversions from type string to integer
etc...etc....
There's seems to be a billion problems all of a sudden.

I have option strict turned OFF in my development environment. Is it
enforcing all of these errors that would normally have been generated
with
option strict ON when running as an executable? Is there a way to get
around
it at all? I don;t understand why it runs perfectly fine in dev but bombs
out in a big way when running as an executable...

Thanks,

Brad

Why do you have Option Strict turned Off? In my book that is a huge no-
no. I'm not sure why they don't blow up during development, but you
should turn on Option Strict and fix them.

Thanks,

Seth Rowe [MVP]

[Patrice]

It shouldn't be the difference all things being equals. If I remember the
IDE have an otpion to hide exceptions.

Also if you done your appl to continue whatever happens you'll have loads of
errors if something goes wrong but the first one is likely the more
signigifant (but example if data can't be loaded, you can then run in a fiar
amount of subsequent errors).

Your best bet would be investigate the first error you get. Optino strict o
is a good idea but it shouldn"t make a difference all things being equal
(basically it help to makes code that won"t contains those errors but if it
is off there i not reason you can run the code in debug mdoe with no error
and have loads of error when running the EXE file).

--
Patrice

"Brad Pears" <br***@truenorthloghomes.coma écrit dans le message de groupe
de discussion : eo**************@TK2MSFTNGP05.phx.gbl...

I have a vb.net 2005 project and have made a lot of modifications to it.
The project runs fine in debug mode. Now I want to implement it and first
I am running the executable on my machine to make sure it runs properly...
However, when I run it locally as an executable, I get no end to run time
errors - things like conversions from type string to integer etc...etc....
There's seems to be a billion problems all of a sudden.

I have option strict turned OFF in my development environment. Is it
enforcing all of these errors that would normally have been generated with
option strict ON when running as an executable? Is there a way to get
around it at all? I don;t understand why it runs perfectly fine in dev but
bombs out in a big way when running as an executable...

Thanks,

Brad

[Brad Pears]

Thanks for your help!!!
"Patrice" <http://www.chez.com/scribe/wrote in message
news:BC**********************************@microsof t.com...

It shouldn't be the difference all things being equals. If I remember the
IDE have an otpion to hide exceptions.

Also if you done your appl to continue whatever happens you'll have loads
of errors if something goes wrong but the first one is likely the more
signigifant (but example if data can't be loaded, you can then run in a
fiar amount of subsequent errors).

Your best bet would be investigate the first error you get. Optino strict
o is a good idea but it shouldn"t make a difference all things being equal
(basically it help to makes code that won"t contains those errors but if
it is off there i not reason you can run the code in debug mdoe with no
error and have loads of error when running the EXE file).

--
Patrice

"Brad Pears" <br***@truenorthloghomes.coma écrit dans le message de
groupe de discussion : eo**************@TK2MSFTNGP05.phx.gbl...

>I have a vb.net 2005 project and have made a lot of modifications to it.
The project runs fine in debug mode. Now I want to implement it and first
I am running the executable on my machine to make sure it runs
properly... However, when I run it locally as an executable, I get no end
to run time errors - things like conversions from type string to integer
etc...etc.... There's seems to be a billion problems all of a sudden.

I have option strict turned OFF in my development environment. Is it
enforcing all of these errors that would normally have been generated
with option strict ON when running as an executable? Is there a way to
get around it at all? I don;t understand why it runs perfectly fine in
dev but bombs out in a big way when running as an executable...

Thanks,

Brad