Click Run and get no response

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I'm seeing some erratic behavior when running app's within the VB.NET IDE. When I select Run (F5 or >), sometimes my user form appears, and other times it doesn't. The application appears to be running somewhere, because when I click Debug, the Stop button is available and clicking it stops the application. But the user form doesn't appear, and the application's icon doesn't appear at the bottom of the screen. When I build the application just prior to running it, I seem to have better luck, but I didn't think this was necessary if I had not made any changes to the app. What's going on and how do I remedy it?

TIA,
Andy Roe
 
Hi Andy,
Once again today ( not with you ), a difficult question is
asked. These sorts of problems are almost impossible to diagnose remotely
with this amount of information.

Some basic questions.

Q.) Did this ever work consistently, or has it just recently started doing
this.?

Q.) If it used to run OK, what changed have been made lately before it went
wrong.?

I .) If neither of the above are true then :-

Q.) How frequently does this fail ?

Q.) Does it happen on another machine or on release mode ?

Q.) If Yes to the question above, what is the Load Event trying to do which
it may not be able to complete ?

Q.) Have you tried to define the area which may be causing the problem by
disabling functionality one by one ?

Q.) Do you have further information which may be of help given the questions
asked ?


Regards -OHM
I'm seeing some erratic behavior when running app's within the
VB.NET IDE. When I select Run (F5 or >), sometimes my user form
appears, and other times it doesn't. The application appears to be
running somewhere, because when I click Debug, the Stop button is
available and clicking it stops the application. But the user form
doesn't appear, and the application's icon doesn't appear at the
bottom of the screen. When I build the application just prior to
running it, I seem to have better luck, but I didn't think this was
necessary if I had not made any changes to the app. What's going on
and how do I remedy it?

TIA,
Andy Roe
Click to expand...

Best Regards - OHMBest Regards - OHM (e-mail address removed)
 
This frequently happens with Visual Studio 2002. I haven't seen it much (if
at all) with VS2003. If you are running VS 2002, I think you just have to
live with it; even "hello world" apps do this a lot.

Jerry

andy said:
I'm seeing some erratic behavior when running app's within the VB.NET
Click to expand...
IDE. When I select Run (F5 or >), sometimes my user form appears, and other
times it doesn't. The application appears to be running somewhere, because
when I click Debug, the Stop button is available and clicking it stops the
application. But the user form doesn't appear, and the application's icon
doesn't appear at the bottom of the screen. When I build the application
just prior to running it, I seem to have better luck, but I didn't think
this was necessary if I had not made any changes to the app. What's going on
and how do I remedy it?
 
Wow, I'm shocked !, I didnt realise that 2002 was so flaky, after all Hello
World is not exactly a taxing proposition for any development environment is
it !

Regards - OHM

Jerry said:
This frequently happens with Visual Studio 2002. I haven't seen it
much (if at all) with VS2003. If you are running VS 2002, I think you
just have to live with it; even "hello world" apps do this a lot.

Jerry


IDE. When I select Run (F5 or >), sometimes my user form appears, and
other times it doesn't. The application appears to be running
somewhere, because when I click Debug, the Stop button is available
and clicking it stops the application. But the user form doesn't
appear, and the application's icon doesn't appear at the bottom of
the screen. When I build the application just prior to running it, I
seem to have better luck, but I didn't think this was necessary if I
had not made any changes to the app. What's going on and how do I
remedy it?
Click to expand...

Best Regards - OHMBest Regards - OHM (e-mail address removed)
 
* "=?Utf-8?B?YW5keQ==?= said:
I'm seeing some erratic behavior when running app's within the VB.NET
IDE. When I select Run (F5 or >), sometimes my user form appears, and
other times it doesn't. The application appears to be running somewhere,
because when I click Debug, the Stop button is available and clicking it
stops the application. But the user form doesn't appear, and the
application's icon doesn't appear at the bottom of the screen. When I
build the application just prior to running it, I seem to have better
luck, but I didn't think this was necessary if I had not made any
changes to the app. What's going on and how do I remedy it?
Click to expand...

Please wrap lines after ~76 characters.

Are you using VB.NET 2002? Maybe it's this bug:

<http://support.microsoft.com/default.aspx?scid=kb;en-us;Q326098>
 
* "Jerry Ham said:
This frequently happens with Visual Studio 2002. I haven't seen it much (if
at all) with VS2003. If you are running VS 2002, I think you just have to
live with it; even "hello world" apps do this a lot.
Click to expand...

It seems to be fixed in 99% of the cases, but on a friend's computer it
does even occur in VS.NET 2003 (French version).
 
* "One Handed Man said:
Wow, I'm shocked !, I didnt realise that 2002 was so flaky, after all Hello
World is not exactly a taxing proposition for any development environment is
it !
Click to expand...

It depends on the machine. On my machine the bug often occured, after
1/2 year of annoyance, it suddenly worked (maybe a patch from Windows
Update or an other application replacing a component fixed it?). On my
other computer, it never occured (VS.NET 2002).
 
Thats not exactly good news for developers though is it. I mean, they would
be blaming it on your application rather than the machine, the operating
system or the framework.

:(

* "One Handed Man [ OHM ]"
Wow, I'm shocked !, I didnt realise that 2002 was so flaky, after
all Hello World is not exactly a taxing proposition for any
development environment is it !
Click to expand...

It depends on the machine. On my machine the bug often occured, after
1/2 year of annoyance, it suddenly worked (maybe a patch from Windows
Update or an other application replacing a component fixed it?). On
my
other computer, it never occured (VS.NET 2002).
Click to expand...

Best Regards - OHMBest Regards - OHM (e-mail address removed)
 
I have the exact symptoms you report running VS Net 2002 on a Windows XP
box. I do not have
this problem on a box running the same version of VS Net 2002 under Windows
2000.

But my workaround is to do a Step Into <F11> before <F5>. This at least
seems to force the program to execute every time - albiet an annoying extra
step.
 
* "clr said:
I have the exact symptoms you report running VS Net 2002 on a Windows XP
box. I do not have
this problem on a box running the same version of VS Net 2002 under Windows
2000.

But my workaround is to do a Step Into <F11> before <F5>. This at least
seems to force the program to execute every time - albiet an annoying extra
step.
Click to expand...

As mentioned in the document I mentioned, you can order a patch at
Microsoft.
 
* "One Handed Man said:
Thats not exactly good news for developers though is it. I mean, they would
be blaming it on your application rather than the machine, the operating
system or the framework.
Click to expand...

Mhm... I posted a link to a Microsoft KB article about this problem in
my other reply. A patch is available.
 
Yes, I see that but in general its not good news to have something which is
going to break on one machine and run on another.

Regards - OHM

* "One Handed Man [ OHM ]"
Thats not exactly good news for developers though is it. I mean,
they would be blaming it on your application rather than the
machine, the operating system or the framework.
Click to expand...

Mhm... I posted a link to a Microsoft KB article about this problem
in
my other reply. A patch is available.
Click to expand...

Best Regards - OHMBest Regards - OHM (e-mail address removed)
 
* "One Handed Man said:
Yes, I see that but in general its not good news to have something which is
going to break on one machine and run on another.
Click to expand...

ACK -- even if it's "impossible" to repro it on the other machine.

;-)
 
VS.NET 2002 on Win XP

I upgraded from 256MB to 1 GB RAM, and problem dissapeared.

Prior to RAM upgrade it occured 2 out of 3 times I ran/compile my projects -
clicked 'save project' 1,2 or sometimes 3 times before running/compiling to
make it work.

Have found since the RAM upgrade it almost never occurs.


andy said:
I'm seeing some erratic behavior when running app's within the VB.NET
Click to expand...
IDE. When I select Run (F5 or >), sometimes my user form appears, and other
times it doesn't. The application appears to be running somewhere, because
when I click Debug, the Stop button is available and clicking it stops the
application. But the user form doesn't appear, and the application's icon
doesn't appear at the bottom of the screen. When I build the application
just prior to running it, I seem to have better luck, but I didn't think
this was necessary if I had not made any changes to the app. What's going on
and how do I remedy it?
 
A good old memory leak eh ?

Regards - OHM
VS.NET 2002 on Win XP

I upgraded from 256MB to 1 GB RAM, and problem dissapeared.

Prior to RAM upgrade it occured 2 out of 3 times I ran/compile my
projects - clicked 'save project' 1,2 or sometimes 3 times before
running/compiling to make it work.

Have found since the RAM upgrade it almost never occurs.



IDE. When I select Run (F5 or >), sometimes my user form appears, and
other times it doesn't. The application appears to be running
somewhere, because when I click Debug, the Stop button is available
and clicking it stops the application. But the user form doesn't
appear, and the application's icon doesn't appear at the bottom of
the screen. When I build the application just prior to running it, I
seem to have better luck, but I didn't think this was necessary if I
had not made any changes to the app. What's going on and how do I
remedy it?
Click to expand...

Best Regards - OHMBest Regards - OHM (e-mail address removed)
 
* "harry said:
VS.NET 2002 on Win XP

I upgraded from 256MB to 1 GB RAM, and problem dissapeared.
Click to expand...

Ouch. I upgraded my RAM to 1 GB too and since then it worked...
 
Hi Herefried - my system began life with one gig ram and it still happened
under vs 2002.

Bernie
 
Back
Top