location of current CF for PPCs?

J

Jim

I've reinstalled development environment from the latest MSDN DVDs, and
seem to have taken a step backwards. -- Visual Studio 2003 from the MSDN
Universal DVD (Oct 2003, Disc 2435), followed by reinstalling the Software
Development Kit for Windows Mobile 2003-based Pocket PCs from the MSDN
Universal DVD (Nov 2003, disc 2426.1).

After reinstalling, I rebuilt my app and get a warning when attempting to
deploy it that the CF components on the target device are later than what I
just tried to deploy. (Freshly installed Emulator - cgautil shows Microsoft
..NET Compact Framework [1.0.2268.00], while the version on my real Pocket PC
(before reinstalling) shows version [1.0.3111.00].

What is the current CF version and where do I get it? Is the latest
(November 2003) DVD shipping an old version? Is there a mismatch between the
latest Compact Framework and latest Mobile 2003 SDK?

Also what URL should I direct customers to, to ensure they have the most
current Compact Framework installed?

Thanks,
Jim
 
J

Jim

Thank you Maarten and Bardak,

First link (from Maarten) is self-extracting CAB files. I've copied these
to the respective places (CompactFrameworkSDK\v1.0.5000\Windows
CE\wce300\arm etc and ..\wce400\armv4 etc.

One of the 14 CAB files had no place to go, and coincidentally, one original
CAB file has no replacement:
(Original: without a match is Arm4VT.cab; new without a match is
ARMV4I.cab)
Is this a typo in creating the CABs? should I just rename this file?

Second link (from Bardak) is to an MSI download that updates the target
devices. - suitable for end user usage.
Is this a stable. long term link, or is there a sequence an end-use should
go through to get there ... Microsoft downloads, click something, click
something. click something?

Thanks
Jim
 
J

Jesse Vaught [MSFT]

Jim,

1) The ArmV4I & ArmV4T cabs are identical, you should just rename the file.
2) The MSI is intended for end-users to install on their desktop system.

--

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this
message are best directed to the newsgroup/thread from which they
originated.
--------------------
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top