CF 2.0 SP2 installation on development machine

BrianK

unread,

Oct 4, 2008, 12:20:01 AM10/4/08

to

I downloaded the msi file for CF 2.0 SP2 and ran it on my XP development
machine with VS2005 and Platform Builder.
The rebuilt CE image is not including CF 2.0 SP2.
cgacutil on the CE device reports CF build number 2.0.6129.0 which is SP1.
How can I get SP2 to include in the CE image?

Chris Tacke, eMVP

unread,

Oct 5, 2008, 9:30:40 PM10/5/08

to

Why would updating the CF on the machine affect PB? You need to install all
of the PB QFEs. If the correct files still aren't present (I honestly don't
know which SP level the QFEs bring you up to) then you need to either
manually patch it or just create your own BIB/REG files for installation.

--

Chris Tacke, Embedded MVP
OpenNETCF Consulting
Giving back to the embedded community
http://community.OpenNETCF.com

"BrianK" <Bri...@discussions.microsoft.com> wrote in message
news:B1E8A2A7-286A-4153...@microsoft.com...

BrianK

unread,

Oct 6, 2008, 9:35:01 AM10/6/08

to

"Chris Tacke, eMVP" wrote:

> Why would updating the CF on the machine affect PB? You need to install all
> of the PB QFEs.

I don't know the answer to this question. Are you saying that I need a PB
QFE in order to for PB to pick up on the CF SP2 I installed n my development
machine?

If the correct files still aren't present (I honestly don't
> know which SP level the QFEs bring you up to) then you need to either
> manually patch it or just create your own BIB/REG files for installation.

How is PB at present determining the need for CF SP1?

Paul G. Tobey [eMVP]

unread,

Oct 6, 2008, 12:11:44 PM10/6/08

to

Of course. You can't expect Platform Builder to grab code from some other
piece of software that you might or might not have installed. Even if it
did, that might not be what you want. Install all of the PB QFEs and you'll
have the latest version of .NET CF 2.0 when you add the .NET CF 2.0
components from the catalog.

Paul T.

"BrianK" <Bri...@discussions.microsoft.com> wrote in message

news:84DFE4F9-4EC4-4F84...@microsoft.com...