EXEs

[A. Gaubatz]

I have noticed that my application runs much smoother in the Visual
Basic Development Environment, than it does using the .exe located in
the project's "bin" folder. Is this the right .exe to be using? Also, if
it is, is there any way to make the .exe work as smoothly as it does
inside the Dev Environment?

Thanks,

 

[Herfried K. Wagner [MVP]]

I have noticed that my application runs much smoother in the Visual
Basic Development Environment, than it does using the .exe located in
the project's "bin" folder. Is this the right .exe to be using? Also, if
it is, is there any way to make the .exe work as smoothly as it does
inside the Dev Environment?

How do you determine if the application runs "smoothly"?

 

[A. Gaubatz]

The application involves animations, and they play smoothly in the dev
environment, wheras with the .EXE, they are very jerky when the app is
first opened.

 

[Herfried K. Wagner [MVP]]

The application involves animations, and they play smoothly in the dev
environment, wheras with the .EXE, they are very jerky when the app is
first opened.

Which control do you use for plaing the animations?

 

[Guest]

I noticed that you said that the animations were jerky when the app was
"First Opened". When an application is opened, I don't think that code is
loaded and converted to machine language until is actually called and used in
the app which can take a bit of time. However, after it's loaded and used
once, it should run faster than from the IDE.

 

[Nick Randolph]

I would suggest that this is the reason for the differences you are
experiencing. One of the issues we often see is that debugging causes the
app to behave differently (especially when multi-threaded) than it runs in
release. The solution is to test test test test and test again and for you
to always run the tests in release mode.

Nick