WINCE.NET 4.1, 4.2 and VS.NET 2003 Connection

K

keith

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
"connect"
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
VS.NET

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 ?
 
V

Volker Keith

Yes I have, but those tools are made to connect
without Active Sync.
But:
Even if a connection is possible using those utilities,
it does not explain, why we have to select a PPC if a
wince.net device is to be connected.
Have you made the same experiments like we have done ?
 
G

Ginny Caughey [MVP]

Volker,

I haven't experienced the same problems that you have with CE 4.1 devices, but I
do use the CE Utilities to tell VS 2003 which device to use for debugging.
 
G

Ginny Caughey [MVP]

Jens,

I also use the PPT8800, but I haven't seen this problem. What version of
ActiveSync are you using?
 
R

Rich Hanbidge [MSFT]

Hi Jens,
If you uninstall ActiveSync, you will lose some important information VS
places into the registry, which is used to enable debugging through AS.

Unfortunately, the only fix is to re-install VS. That will replace the
missing reg keys, and bring VS to the proper state. You should have a
number of registry values under this key:
"HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services\ProxyPorts" If
you only see one, than this is most likely the problem you are seeing.

Sorry for the hassle.

Rich

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: Jens Meyer <[email protected]>
| References: <#[email protected]>
| X-Newsreader: AspNNTP 1.50 (ActionJackson.com)
| Subject: Re: WINCE.NET 4.1, 4.2 and VS.NET 2003 Connection
| Mime-Version: 1.0
| Content-Type: text/plain; charset="us-ascii"
| Content-Transfer-Encoding: 7bit
| Message-ID: <[email protected]>
| Newsgroups: microsoft.public.dotnet.framework.compactframework
| Date: Mon, 18 Aug 2003 23:51:13 -0700
| NNTP-Posting-Host: actionjackson133.dsl.frii.net 216.17.147.133
| Lines: 1
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP12.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.dotnet.framework.compactframework:31291
| X-Tomcat-NG: microsoft.public.dotnet.framework.compactframework
|
|
| I tried both: 3.5 and 3.7. But i had big probs with 3.5 to get it to
| work or even get a working connection. I also use a MDA with an USB
| connection and i never had problems with it. I removed any other devices
| form the Desktop PC and also reinstalled activesync (I deinstalled
| activesync first, ofcourse :))
|
| Thanks for your help
|
| Jens
|
|
|
| Don't just participate in USENET...get rewarded for it!
|
 
R

Rich Hanbidge [MSFT]

Hi Keith,
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:
http://www.microsoft.com/downloads/details.aspx?familyid=033afc0e-b968-42f3-
9a19-b2e71040f0f0&displaylang=en

2. What type of device are you attempting to connect to? Specifically what
kind of CPU?

Rich
This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| Content-Class: urn:content-classes:message
| From: "keith" <[email protected]>
| Sender: "keith" <[email protected]>
| 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: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| 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
microsoft.public.dotnet.framework.compactframework:31024
| 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
| "connect"
| 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
| VS.NET
|
| 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 ?
|
|
|
|
|
 
T

Tom Bean

Ginny,

Does the "Windows CE Utilities for Visual Studio .NET 2003 Add-on Pack"
change the emulator to be more compatible with Windows CE 4.1 and later or
is it strictly for a device running Windows CE 4.1?

Thanks,
Tom
 
C

Chris Tacke, eMVP

What do you mean by "more compatible"? There is a Windows CE emulator,
which is CE 4.1.

--
Chris Tacke, eMVP
Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

Tom Bean said:
Ginny,

Does the "Windows CE Utilities for Visual Studio .NET 2003 Add-on Pack"
change the emulator to be more compatible with Windows CE 4.1 and later or
is it strictly for a device running Windows CE 4.1?

Thanks,
Tom

Ginny Caughey said:
Keith,

Have you installed the CE Utilities for VS 2003?
Click to expand...
http://www.microsoft.com/downloads/...A6-2095-4086-B0CC-7C6C39B28762&displaylang=en
Click to expand...
 
C

Chris Tacke, eMVP

You need to use the PPC03 emulator. Install the PPC03 SDK and you should be
all set.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

WinCE.Net 4.1 EMULATOR / C# / Webservice client / SoapException 1
Developing for Win CE.Net 4.2 5
Managed TypeLoadException ... 2
PocketPC 2003 -> WinCE 4.2 in VS .NET 2003 8
Custom PB SDK in VS.Net 3
Debugging CF2.0 SP1 app on CE 4.2 1
VS.NET 2003, CE.NET 4.2, MSMQ 14
VS.NET and CE 4.2 2

Top