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

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.

--
Ginny Caughey
..NET Compact Framework MVP


"Lonifasiko" <mloichate@gmail.com> wrote in message
news:1128516979.658421.59180@g47g2000cwa.googlegroups.com...
> 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.
>

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?

On 5 Oct 2005 08:15:57 -0700, "Lonifasiko" <mloichate@gmail.com>
wrote:

>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!

Lonifasiko,

I have not had the problem you are describing. Did you uninstall Activesync
3 before installing Activesync 4, or did you upgrade?

--
Ginny Caughey
..NET Compact Framework MVP


"Lonifasiko" <mloichate@gmail.com> wrote in message
news:1128525357.035696.154120@z14g2000cwz.googlegroups.com...
> 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!
>

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.

Hi again guys, there is no way! I can't get ActiveSync working together
with VS.NET 2003!

After some googling I found this post, advising to install these tools
that worked well for the user who initiated the post:

http://groups.google.es/group/micro...5dcaa8cecf8050e

I've installed this tools after installing AS 4.0 but neither this way
works!

I need urgent solution on this matter. 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.

--
-Robert Levy
Program Manager, Windows Mobile Developer Experience
http://blogs.msdn.com/windowsmobile

"Beebs" <ABieberitz@charter.net> wrote in message
news:mju7k15kspq249bqdqvc9asdllv7ee5csj@4ax.com...
> 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?
>
> On 5 Oct 2005 08:15:57 -0700, "Lonifasiko" <mloichate@gmail.com>
> wrote:
>
>>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!
>

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...framework?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).

"Lonifasiko" <mloichate@gmail.com> wrote in message
news:1128582451.980719.76380@f14g2000cwb.googlegroups.com...
> Hi again guys, there is no way! I can't get ActiveSync working together
> with VS.NET 2003!
>
> After some googling I found this post, advising to install these tools
> that worked well for the user who initiated the post:
>
> http://groups.google.es/group/micro...5dcaa8cecf8050e
>
> I've installed this tools after installing AS 4.0 but neither this way
> works!
>
> I need urgent solution on this matter. Thanks.
>

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.

On Thu, 6 Oct 2005 08:22:21 -0700, "Robert Levy [MS]"
<rlevy@online.microsoft.com> wrote:

>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.