VS.NET 2003/ActiveSync 3.8 and VS.NET 2005/ActiveSync 4.0

  • Thread starter Thread starter Lonifasiko
  • Start date Start date
L

Lonifasiko

Can VS.NET 2003/ActiveSync 3.8 and VS.NET 2005/ActiveSync 4.0 live
together without any incompatibility problems?

When deploying Smart Device application with VS.NET 2005 I got an error
message, googled and found posts about advising to install ActiveSync
4.0 Developer Preview.

Prior to installing this new version I would like to tell me any
problems I could suffer from.

Thanks in advance.
 
You can only have one version of Activesync on a machine (or virtual
machine) at a time, but I haven't had any problems using Activesync 4.0 with
VS 2003.
 
Implementation of PPC 2003 application developed with VS.NET 2003 via
ActiveSync 4.0 not working. :(
Output window tells me the implementation is not correct but 0 errors
are shown! Really frustrating!

How can we use both versions of VS.NET if they are not able to
implement applications via same ActiveSync version!!! I do not
understand anything :(

Has anyone else experienced this error before? Help please!
 
Not only that, but is anyone aware if any company or independent
developer out there is developing some type of utility or plug-in that
will allow .cdb files to be converted to .mdb, since Microsoft saw fit
to chop this functionality out of the new ActiveSync 4.0?
 
Lonifasiko,

I have not had the problem you are describing. Did you uninstall Activesync
3 before installing Activesync 4, or did you upgrade?
 
Hi Ginny, I uninstalled ActiveSync 2.8 and then install 4.0. I must
also say I'm working with VS.NET 2005 Beta 2, but now the porblem is
that works with 2005 Beta2 but not with 2003. Really annoying guys!

I'll try unistalling 4.0, cleaning registry keys and installing 4.0
again. I'll post my results here, but I wiuld much appreciate any
feedback around this issue.

Thanks.
 
The MDB conversion was removed because ADOCE (the APIs for working with .CDB
files) was officially deprecated in Pocket PC 2003 and, unfortunately, no
longer supported. There are, however, 3rd party tools out there for
converting MDBs to SQL CE files - that would be my recommendation.
 
You need to import ProxyPorts.reg manually. Please see tools readme for
details.

Best regards,

Ilya

This posting is provided "AS IS" with no warranties, and confers no rights.

*** Want to find answers instantly? Here's how... ***

1. Go to
http://groups-beta.google.com/group/microsoft.public.dotnet.framework.compactframework?hl=en
2. Type your question in the text box near "Search this group" button.
3. Hit "Search this group" button.
4. Read answer(s).
 
That's all fine and dandy, but when you have a complex application
using a .cdb to .mdb on the desktop and your client's customers are
installing 4.0 on their desktops and the whole app is going haywire,
that's not a prudent solution...having to reprogram the entire
application around SQL CE now, just because Microsoft decides to go
another direction, doesn't mean it's a wise decision, or even a
reasonable one.
 
Scott,

Yes, but it should work with both versions of Visual Studio as long as you
aren't using wireless networking for debugging. AS 4.0 is also the only
version that works with Windows Mobile 5.0.
 
Hi Ilya, I suppose you are talking to me ;-)

I've already read almost all readme files on the installed tools but I
can't obtain anything in clear.

Where do you exactly want me to manually place ProxyPorts.reg file?
could you explain me a little bit more in depth?

I've looked for that file on my PC and is placed on this directory:
C:\Archivos de programa\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\WinCE Utilities\WinCE Proxy Ports Reg
I've edited it, but I'd prefer not to change anything without expert
advice.

Hope you can give me more detailed instructions. Thanks very much.
 
Lonifasiko,

If you just double-click on the ProxyPorts.reg file, it will be inserted
into your registry. You do not need to edit ProxyPorts.reg or change it in
any way. Ilya and I assume that the ActiveSync connection with VS 2003 get
lost when you uninstalled AS 3 - a common problem. If you had upgraded to AS
4 rather than uninstalling and reinstalling, you would not have had this
problem. But by installing the ProxyPorts.reg file into your registry, it
should fix it.
 
Thanks Ginny,

Unfortunantly, using wireless for debugging & deploying is exactly what I
was attempting to do. I hope the final version will add this feature back
in.

In the mean time, after uninstalling 4.0, reinstalling 3.8, finding it
didn't work any more, going through the install log to locate all the files
left behind by 4.0 & manually deleting them, uninstalling 3.8, reinstalling
3.8, I found that going to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE
Services and changing MajorVersion to 4 and MinorVersion to 0 allowed me to
use 3.8 with VS2005 and still have my wireless. Not what I'd want to do on
a production machine, but that's a problem for another day.
 
Scott,

Thanks for reporting back. I assume you'll have problems targetting Windows
Mobile 5.0 devices however. Are you able to "dock" the emulators using
Activesync 3.8 ( from Tools, Device manager)?
 
Back
Top