VS2005 Beta 2 Deploy to Device Requires Activesync 4

  • Thread starter Thread starter Darren Shaffer
  • Start date Start date
D

Darren Shaffer

Just to save all of you some frustration, if you decide to
download Visual Studio 2005 Beta 2 which was posted on
MSDN on Monday, you will not be able to deploy directly to device.

Deployment to the emulators works fine, however when you attempt
to deploy to device, you'll get a message that the version of Activesync
is not compatible (even if you have AS 3.8).

The VS for Devices Team will post information shortly concerning
the availability of an Activesync 4.0 beta to allow us to deploy to
device through VS Beta 2.

Note - in the meantime, you can always create a Smart Device Setup
project using VS2005 B2 (which is a good exercise anyway, because the
process is considerably different than 'Build CAB' in VS2003)
and drop the resulting CAB on your device through File Explorer.

--
Darren Shaffer
..NET Compact Framework MVP
Principal Architect
Connected Innovation
www.connectedinnovation.com
 
Hi Darren,

I just installed the beta 2 on 2 PC and I could even not deploy to the
device emulator. I have two PC with Win XP SP2 (German). On the same PC is VS
2003. I have had Dec CPT installed on the PC and deistalled them completly
before installing the new beta.

Do you have any tipps for me?

Thanks Thomas
 
Ok, I can't deploy directly to the emulator (Pocket PC 2003 SE).. but that
doesn't matter.. I can always do what you said - build a cab file.

But.. there's a problem.. it says that it needs a newer compact framework to
be installed on the device when I run the program.

And.. I can't find the damn .cab file for the setup of the compact
framework, so I can't install it :(

Anyone knows where it is, perhaps?

Cheers,
Tadej
 
is Virtual Machine Network Services one of the active protocols on
your network connection? I have seen upgrades from the CTP to a
Beta or a Beta to a later CTP encounter difficulties in getting
VMNS installed and started - there are some artifacts being left
behind after uninstall that cause this. Amit has some great advice on
fixing this over in microsoft.private.whidbey.smartdevices.
--
Darren Shaffer
..NET Compact Framework MVP
Principal Architect
Connected Innovation
www.connectedinnovation.com
 
Back
Top