If nothing has changed on device, it is likely something has changed on PC
(Visual Studio machine). Otherwise the message of CF newer on device does
not make sense. My suggestion is
1. Check the dlls in <VSInstallDir>\CompactFrameworkSDK\v1.0.5000\Windows
CE\ and the corresponding netcf cab in one of the CPU directories. See if
there is anything suspicious, e.g. older timestamps.
2. Delete all the xsl files from \Documents and
Settings\<CurrentUser>\Local Settings\Application
Data\Microsoft\visualstudio\devices\7.1\. Restart VS and open a device
project to regenerate those files.
If nothing is found, I'd suggest they uninstall SDE and reinstall it.
Cleaning the xsl files and the CompactFrameworkSDK tree before the
reinstall.
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: "Chris P" <
[email protected]>
| References: <
[email protected]>
<
[email protected]>
<DwS#
[email protected]>
<
[email protected]>
| Subject: Re: Can deploy but cannot debug on CE 4.1 device
| Date: Thu, 13 Nov 2003 12:42:41 -0500
| Lines: 114
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <
[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| NNTP-Posting-Host: 12.41.171.130
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:38516
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
| I have this problem very often. They I get around it is to change the
proj
| properties to NO DEBUG, save the properties, then switch the properties
back
| to DEBUG. This seems to work for us.
|
|
| | > Yes, toolhelp.dll exists on the device. The customer claims that the CE
| > image itself is unchanged, and it was working previously. The problem
| > exists when using USB and ConMan for connecting.
| >
| > I walked him through using SDAuthUtil over ethernet and that seems to
| work,
| > but understanding why ConMan won't work would be useful.
| >
| > --
| > Chris Tacke, eMVP
| > Co-Founder and Advisory Board Member
| >
www.OpenNETCF.org
| > ---
| > Windows CE Product Manager
| > Applied Data Systems
| >
www.applieddata.net
| >
| >
| > | > > Has the existence of toolhelp.dll on device been verified?
| > >
| > > This posting is provided "AS IS" with no warranties, and confers no
| > rights.
| > > --------------------
| > > | From: "Chris Tacke, eMVP" <
[email protected]>
| > > | References: <
[email protected]>
| > > | Subject: Re: Can deploy but cannot debug on CE 4.1 device
| > > | Date: Wed, 12 Nov 2003 13:45:43 -0500
| > > | Lines: 48
| > > | X-Priority: 3
| > > | X-MSMail-Priority: Normal
| > > | X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| > > | X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| > > | Message-ID: <
[email protected]>
| > > | Newsgroups: microsoft.public.dotnet.framework.compactframework
| > > | NNTP-Posting-Host: nat2.applieddata.net 64.72.200.61
| > > | Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| > > | Xref: cpmsftngxa06.phx.gbl
| > > microsoft.public.dotnet.framework.compactframework:38402
| > > | X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
| > > |
| > > | As an added piece of information, when deploying the app, Studio
gives
| a
| > > | warning that the CF on the device is *newer* than the CF on the PC.
| I'm
| > > not
| > > | sure how this is possible. The CF on the device is the standard RTM
| > from
| > > | Platform Builder, and there is no QFE to put CFSP1 on a CE 4.1
device
| > > (only
| > > | 4.2). The customer is using the standard Studio installed CF, which
| is
| > > also
| > > | supposed to be the RTM. What's going on there?
| > > |
| > > | --
| > > | Chris Tacke, eMVP
| > > | Co-Founder and Advisory Board Member
| > > |
www.OpenNETCF.org
| > > | ---
| > > | Windows CE Product Manager
| > > | Applied Data Systems
| > > |
www.applieddata.net
| > > |
| > > |
| > > | | > > | > Alright, so the problem seems to have returned. Using a very
simple
| > > | "hello
| > > | > world" app, the Studio will push a binary down to the device but
| will
| > > not
| > > | > launch the debugger.
| > > | >
| > > | > Of course the customer has been debugging for weeks now without
| > problem,
| > > | but
| > > | > for some reason it no longer works. The following actions have
not
| > > fixed
| > > | > the problem:
| > > | >
| > > | > - Reboot the PC
| > > | > - Hard reset the CE device
| > > | > - Delete the persistent CE registry
| > > | > - Run DelCryptoKeys on both ends
| > > | > - Import proxyports.reg
| > > | >
| > > | > --
| > > | > Chris Tacke, eMVP
| > > | > Co-Founder and Advisory Board Member
| > > | >
www.OpenNETCF.org
| > > | > ---
| > > | > Windows CE Product Manager
| > > | > Applied Data Systems
| > > | >
www.applieddata.net
| > > | >
| > > | >
| > > | >
| > > |
| > > |
| > > |
| > >
| >
| >
|
|
|
