Quote:
Originally Posted by guybrush
@adrenaln: hmm, I can remember, that I actually didn't have this issue until a certain point (RC5 or so)...  |
Although my memory does fail me sometimes, I'm pretty sure this existed even in 1.2 for me. Stupid question but, you didnt by any chance have a mouse plugged in during testing on earlier releases? Perhaps Scott or someone from Flux can confirm if the resume code was inserted or changed in a particular release, or if it has always existed largely unchanged.
Quote:
Originally Posted by guybrush
Although I believe that this is not a CF issue, HiJack is somewhat right that this issue could have been triggered by a windows update; even tough I do not have a persistent internet connection in the car i sometimes did windows updates via WLAN when I was at my home base...
|
Like I stated above, I have gone to the trouble of even testing the .NET class on clean SP1,2,3 (no updates whatsover, just XP and .NET 2.0) machines with not even CF installed and the "bug" exists.
Quote:
Originally Posted by guybrush
I will do a fresh windows & CF install this weekend, so i can see than if this was caused by an update or not.  |
Good luck with that, I'd really like it to work for you, but I'm 99.999% sure it wont make any difference for you
(I'll leave 0.001 just in case I'm wrong - Its happened before
)