Find version of ActiveSync?

[Nathan]

Is there a way to find out the version of ActiveSync within the custom build
step of an MSI Installer?

I wouldn't normally want to do this. But apparently ActiveSync<4.0 doesn't
like to see cabs for WM5, and gives users an error message that implies the
device is not supported.

People who don't have WM5 shouldn't need to upgrade ActiveSync, and not all
will want to, since apparently 4x doesn't support synching over wifi
anymore.

Nathan

 

[Peter Foot [MVP]]

You can check the registry on the target PC:-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services
contains DWORD values "MajorVersion" and "MinorVersion"

Peter

 

[Nathan]

You can check the registry on the target PC:-
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows CE Services
contains DWORD values "MajorVersion" and "MinorVersion"

Thanks. This helps, but on further investigation it won't resolve the
problem.

The .NETCF 2.0 Cab won't install and says it is not a supported device. This
happens even if I remove wm cabs from the ini.

The obvious question is "Why?" That CAB file will install if you copy it
manually to a storage card. Why does it insist on ActiveSync 4.0 and give
this cryptic error message that implies that .netcf 2.0 won't run on the
device?

I don't think I'm supposed to hack the Cab. Is there anyway to work around
it in the ini file?

Nathan

 

[Ilya Tumanov [MS]]

You should not do anything with CAB, it should work as is. You can verify
that by using NETCF MSI deployment.



Common mistakes with INI:



1. Wrong INI version:



[CEAppManager]
Version = 2.0 <<< Wrong. This is not the product version, it's INI
version and it must be 1.0:



[CEAppManager]
Version = 1.0 << Correct



2. Attempt to use relative path to INI:



CeAppMgr.exe foo.ini << Wrong



CeAppMgr.exe C:\Whatever\Path\foo.ini << Correct - full path should be
provided.



3. Attempt to deploy several CABs with one INI:



CabFiles=Netcf.cab,Whatever.cab,Another.cab << Wrong, will deploy only one
of these.



4. List of CABs too long:



CabFiles=..... <very long list here> << Wrong, limit to ~220 characters.



5. Not all NETCF CABs can be deployed via AS:



http://blogs.msdn.com/netcfteam/archive/2005/10/11/479793.aspx


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

 

[Nathan]

You should not do anything with CAB, it should work as is. You can verify
that by using NETCF MSI deployment.

The same message happens with the MSI deployment.Are you saying it should
work with ActiveSync 3.7? It says right there in the MSi download page that
it uses ActiveSync 4.0. I thought that woudl be enforced by the MSI, though,
and not the CAB itself.

Common mistakes with INI:

1. Wrong INI version:

[CEAppManager]
Version = 2.0 <<< Wrong. This is not the product version, it's INI
version and it must be 1.0:

[CEAppManager]
Version = 1.0 << Correct

Checked - I have:

[CEAppManager]

Version = 1.0

Component = "Compact Framework"

2. Attempt to use relative path to INI:



CeAppMgr.exe foo.ini << Wrong



CeAppMgr.exe C:\Whatever\Path\foo.ini << Correct - full path should be
provided.

Checked - I'm using absolute paths - a pain to do but it works.

3. Attempt to deploy several CABs with one INI:

CabFiles=Netcf.cab,Whatever.cab,Another.cab << Wrong, will deploy only one
of these.

CabFiles = NETCFv2.ppc.armv4.cab,NETCFv2.wm.armv4i.cab

That's one CAB for each platform - that used to be okay.

4. List of CABs too long:



CabFiles=..... <very long list here> << Wrong, limit to ~220 characters.

55 characters.

5. Not all NETCF CABs can be deployed via AS:

http://blogs.msdn.com/netcfteam/archive/2005/10/11/479793.aspx

Now this may be helpful.

This matches the error:
http://support.microsoft.com/default.aspx?scid=kb;en-us;824409

So this could be a rare condition based on an old 2003 version?

The workarounds there seemed to assume I own the CAB file.

Nathan