S
Sandman
Hello,
my project was working yesterday when I closed up shop. Today, I
turned on Visual studio and before making any changes, I compiled a
copy of my app in debug mode. All of the components copied to the
emulator - but the app wouldn't launch. I waited 5-10 minutes, and
still it wouldn't launch. So I hard-reset the emulator. Tried
debugging again, and all the components copied over again, but the app
never launched!
So I rebooted my machine, put the ipaq in the cradle, and tried
debugging from there. On the PPC, the cursor just kept spinning for
about 60 seconds then went away. I verified that .NET apps were
working by launching another .NET app on the pocket pc. It ran just
fine.
I coped an old frmmain.vb backup to the compile directory and it
worked just fine, which makes me think it's something in the "Windows
generated code" that is messing things up. Is there an easy way to
find out what it is? My backup is from last week, so I'll lose 10
hours if I have to redo.
Thanks,
B.
my project was working yesterday when I closed up shop. Today, I
turned on Visual studio and before making any changes, I compiled a
copy of my app in debug mode. All of the components copied to the
emulator - but the app wouldn't launch. I waited 5-10 minutes, and
still it wouldn't launch. So I hard-reset the emulator. Tried
debugging again, and all the components copied over again, but the app
never launched!
So I rebooted my machine, put the ipaq in the cradle, and tried
debugging from there. On the PPC, the cursor just kept spinning for
about 60 seconds then went away. I verified that .NET apps were
working by launching another .NET app on the pocket pc. It ran just
fine.
I coped an old frmmain.vb backup to the compile directory and it
worked just fine, which makes me think it's something in the "Windows
generated code" that is messing things up. Is there an easy way to
find out what it is? My backup is from last week, so I'll lose 10
hours if I have to redo.
Thanks,
B.