> It could be that the problem is in the initialization code for frmStart.
> This will make it appear to bomb out on the application.run line... and
> you'll get no info whatsoever telling you why. Cool huh...
>
> When similar things happen to me I find I have to set a breakpoint in the
> form init code and then step through it line by line. It is painful but
> generally works. You might want to look at Microsoft's application blocks
> (on MSDN somewhere)... there is one that implements a global exception
> handler. This may (I emphasize MAY as I have not tried it yet) allow you
to
> catch and correctly handle the real culprit. Otherwise do the line by line
> step through.
>
> As for the renaming bit - you've got me there....
>
> I've also found that at times nuking the project's obj folder and
> recompiling helps.
>>

"Jens Burup" <jens.burup@mail.dk> wrote in message
news:eZJ4enJMFHA.3852@tk2msftngp13.phx.gbl...
> Hi
>
> I have a large App VS2003, that have started a very funny behaviar.
> Suddenly without changes in the code, when starting run(F5) the compiller
> starts doing its job,
> but then the program stops before screen form shows up, and whith no
> exceptions or errors thrown.
> In the Debug output I can see the normal loading information and at the
> end
> only this:
> The program'[3088] myAPP.exe' has exited with code 0 (0x0)
>
> I can trace the last line to be:
>
> Public sub Main
> Application.Run(New frmStart)
> end sub
>
> (This is my Startup object)
>
> I am 100% sure there is no code or breakpoints that stops the program.
>
> Now an even more strange things is, if I rename my app folder like Myapp
> to
> MyApp1 then everything works normal again.
>
> Is it posible this description could trick any hint where I should look?
>
> Regards
> Jens
>
>