Debugging after installing the v2.0 SP1 QFE to platform builder

Hi,

I have just installed the newly released QFE for v2.0 SP1 in our
Windows CE target device.

Everying thing works fine on the device. However, when debugging using
Visual Studio 2005, it tries to install:
NETCFv2.wce5.armv4i.cab

I assume this is the original v2.0 CF and Visual Studio is trying to
install it because the one on the device reports a different (newer)
version. Unfortunately, it can't install it on our device because it is
too big and so debugging fails.

Anyone know a resolution for this problem?

TIA,
- John

Alex
Fri Jul 21 04:33:31 CDT 2006

> Anyone know a resolution for this problem?

Hi John,

I had a similar problem after rebuilding Platform Builder with
all updates to M06.

If you go to the properties of your project in VS.NET 2005 and
click the 'Devices' tab you'll see 'Deploy the latest version
of the .NET Compact Framework (including Service packs)'. Uncheck
that and it shouldn't download any more.

That said, something that happened in my updates to Platform
Builder has meant that I can't set breakpoints when debugging
any more. Instead I get a message about the breakpoint not
being hit because symbols are not loaded (when they it says they
are loaded in the modules window). If I go back to an unpatched
PB tree I can set breakpoints so I know it isn't VS.NET...

Can I ask - do you see the same behaviour when trying to set a
breakpoint?

Thanks,

Alex/

john
Fri Jul 21 12:32:56 CDT 2006

Thank you, changing that property did indeed allow me to deploy.

And yes, I see the exact same problem as you regarding breakpoints -
exactly the same as you have described. This is obviously a serious
problem - do you know if it has been reported to Microsoft?

TIA,
- John

Alex
Sat Jul 22 03:06:32 CDT 2006

john@tvcompass.com wrote:
> Thank you, changing that property did indeed allow me to deploy.
>
> And yes, I see the exact same problem as you regarding breakpoints -
> exactly the same as you have described. This is obviously a serious
> problem - do you know if it has been reported to Microsoft?
>
> TIA,
> - John
>

Hi John,

Thanks for the feedback. I'm glad that it isn't just something foolish
I've done with my Platform Builder tree but clearly if you are seeing
this too it is going to be a pretty serious problem for people.

I don't know if this has been reported officially - I haven't yet made
any report to Microsoft.

I assume I'll now have to spend another day backing files out of the
updates backup directory and sysgenning until I find out what fixes the
problem. If I do I'll post. Perhaps you might be able to do the same?

Best Regards,

Alex/

Alex
Sat Jul 22 04:38:14 CDT 2006

John,

I think I've worked out how to fix the problem. I had the .NET Compact
Framework 2.0 installed on my desktop system. I installed the .NET
Compact Framework 2.0 SP1 which first required me to manually uninstall
the .NET Compact Framework 2.0.

http://support.microsoft.com/kb/912706

With SP1 installed on my desktop system I can now set breakpoints with a
target running the latest and greatest PB kernel. I'm guessing something
has changed in the debugging support between CF2 and CF2SP1 which breaks
backward compatibility. I see from the change notes that there were
debugging changes, "New debugging features", "Device debugging by using
Mdbg.exe", so I guess that all makes sense.

Does this work for you too?

Best,

Alex/

john
Mon Jul 24 16:23:37 CDT 2006

Hi Alex,

Yes it does, thank you. Breakpoints are working again with SP1...

Many thanks!
- John