VS2005 Beta2 and Pocket PC 2003
I get the error "Connection failed. The current version of ActiveSync is not supported. Install the latest version from www.microsoft.com".
Could someone help me with resolving this problem.
Thanks
-Anthony
I get the error "Connection failed. The current version of ActiveSync is not supported. Install the latest version from www.microsoft.com".
Could someone help me with resolving this problem.
Thanks
-Anthony
http://blogs.msdn.com/vsdteam/
Thanks
Amit
Neil Cowburn - MVP wrote:
Until ActiveSync 4.0 is available, you can use the fantastic new emulator. I highly recommend it. It even works in Virtual PC and VMWare
And very cool it is, but for those of us doing anything remotely associated with Pocket PC hardware (i.e. graphics accelerated apps) this is basically a complete brick wall to moving further with the VS2005 IDE.*please* can someone post the updated version of ActiveSync ASAP - making it available after releasing the IDE that requires it is to put it mildly unusual planning.
Greg
Peter
Neil Cowburn - MVP wrote:
Until ActiveSync 4.0 is available, you can use the fantastic new emulator. I highly recommend it. It even works in Virtual PC and VMWare
\Documents and Settings\<local user>\Local Settings\Application Data\Microsoft\CoreCon\1.0
Also install the connectivity patch from here:
Thanks,
Vladimir
Most likely explanation is that you were targetting an image without DMA support - only PPC standard and SP standard are updatated by the patch. So if you tried to use DMA to connect to VGA PPC or QVGA SP - the connection would always fail.
If that is not the case could you expand a little on what happened and what you were trying to do ? Were there error messages ? Or did you get any errors during patch installation ?
Thanks,
Vladimir
I think that you know Jeff Abraham ,he helped me so much when
i met the error with DMA.
When using DMA,my solution can compile well but i can't run
debug with emulator or with Device.
It make an error:
Unable to start program %CSIDL_PROGRAM_FILES%\JT\JT.exe
so after a lots of time,Jeff sugest that using explicitly the remote
path and debugger target.
And it seems so well until now.So hope that help to other people.
JulienT
I spoke with Jeff today and it seems that your issue is not related to the transport. It shows up for both device (TCP transport) and emulator (DMA transport) - the problem is more likely to be due to project configuration. I think you already have an email thread going with Jeff so lets resolve this offline and if we uncover something that applies generally - we'll bring it back to the forum.
Thanks,
Vladimir