Here are a couple of questions which may shed some light on your problems.
1. Are you using Platform Builder 4.1 or 4.2? If you are using 4.1, you
must update the version of the NetCF, check out this link:
2. What type of device are you attempting to connect to? Specifically what
kind of CPU?
This posting is provided "AS IS" with no warranties, and confers no rights.
| Content-Class: urn:content-classes:message
| From: "keith" < XXXX@XXXXX.COM >
| Sender: "keith" < XXXX@XXXXX.COM >
| Subject: WINCE.NET 4.1, 4.2 and VS.NET 2003 Connection
| Date: Thu, 14 Aug 2003 15:05:27 -0700
| Lines: 38
| Message-ID: <039d01c362b0$2b7af370$ XXXX@XXXXX.COM >
| MIME-Version: 1.0
| Content-Type: text/plain;
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcNisCt6SpX3lwyASS6dvUjFWUL3tg==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
| NNTP-Posting-Host: TK2MSFTNGXA14 10.40.1.166
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
| Together with my new Visual Studio.NET 2003
| i made following experiences:
| 1)I cannot connect VS Studio via Active Sync with
| Wince.net devices without using one trick:
| First i select a PPC Device and i will get a
| Then i select Wince.net device and the connection
| is OK.
| 2.The wince.net images contain .NET runtime components
| but the VS deploys those components again, but non-
| persistant as it is deployed into the ram-filesystem.
| It seems, that programs, which are deployed manually
| are running without copying the runtime components from
| 3. Having done the quarterly update to wince.net 4.2
| the .net applications on the device do not even run
| if the the applications are deployed manually.
| 4. Removing the quarterly update confirm point 3.
| 5. As an extension to point 1: Even depoyment of software
| is possible choosing a PPC Device instead of a WINCE.NET
| device. The deployed software seems to run correctly.
| Has anybody made the same experiences ? Any hope to
| connect and deploy choosing the right device without
| deploying the instant .net framework inside the wince
| image again ?