[FAQ] Clarification on SP2 and using it for development/deployment

[Alex Feinman [MVP]]

There are several frequently asked questions related to Compact Framework
service packs, so I thought I'd shed some light.

Q0: Do I want to use SP2?

Yes, you do. The list of fixes speaks volumes. The list is available on the
download page

Q1: How do I use SP2 (or SP1) for development:

If you are a developer, you will want a Developer redistributable:
http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en
This download is for Visual Studio 2003 users
Developer redistributable contains ARM, SH3, MIPS and x86 cabs for 2002 and
2003 devices and can be used to install SP2 on the devices as well as on the
emulators. Developer redistrnbutable *does not* contain the installer - you
will need to deploy and launch cabs yourself.
Once the CAB is on a device(emulator), you can click on it in File Explorer
and it will install automatically
To copy cab onto device you can use ActiveSync Explorer. To copy CAB onto
the emulator you can use EmuCpy utility from
http://www.alexfeinman.com/download.asp?doc=emucpy.zip (command line), or
http://www.alexfeinman.com/download.asp?doc=EmulatorCopy.msi (GUI tool.
Integrates with Windows Shell, provides context menu option Copy To
Emulator - beta )

The other redistributable is for everyone (not only developers)
http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en

This one contains an installer that will attempt to update the connected
device (and can be launched again later to update another device)
If you provide an application to the end-users, you can direct them to this
download or bundle it with your application on CD


Q2: Can I update my Visual Studio installation to use SP2.

Currently, Microsoft position on this is that this is not recommended. I'm
not aware of this doing any harm, but it is entirely unnecessary, at least
not with devices. With emulators, which often end up being hard-reset,
reinstalling SP2 becomes a bit of a chore. EmuCpy utility makes it somewhat
less painful and if there is a demand, I could add an option to
automatically launch copied file.

If you decide to update VS installation with SP2 cabs, use the Developer
redist. Also make absolutely sure you copy cabs into correct directories
under <Visual Studio root>\CompactFrameworkSDK\v1.0.5000\Windows CE\wceX00

Alex Feinman

 

[Alex Feinman [MVP]]

Just in case this did not come through clear enough:
Installing the SP2 does not update the emualtor automatically, nor does it
update Visual Studio installation

 

[garfitz]

Surely Microsoft can handle software releases in a less confusing manner ?
Marks out of 10 ?

 

[Geoff Schwab [MSFT]]

Thanks Alex,

I may add some of these to the next release of our FAQ if you don't mind.

--
Geoff Schwab
Program Manager
Excell Data Corporation
http://msdn.com/mobility
http://msdn.microsoft.com/mobility/prodtechinfo/devtools/netcf/FAQ/default.aspx

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Me]

Hi Alex,

Thanks for the FAQ!

Which cab file should I use for Intel Xscale PXA255 processor for the iPAQ
4350?

Thanks,

Gigi

 

[Me]

I found the answer. It is an ARM.

Best regards,

Gigi

 

[Me]

Alex,

I loaded the emucpy util onto my development system. I received the
following message:
creates a "system.runtime.InteropServices.COMexception" error in
EmuCcpy.exe":

This is what I typed in on the command line
emucpy 3 netcf.core.ppc3.x86.cab PPC2003_MIN

PPC2003_MIN Is the Device ID for the Pocket PC 2003 emulator.

What am I doing incorrectly?

Thanks,

G

 

[Alex Feinman [MVP]]

First, there is no 3rd parameter. Second, is Visual Studio 2003 installed on
this machine and can it communicate with the emulator?

 

[Me]

Hi,

Sorry for taking so long to get back. I had technical difficulties with my
Internet service.

Yes, VS 2003 is installed and can communicate with the emulator.

Gigi

 

[PCUser]

I was recently given an ARM4I CPU device to test. My original install of
Visual Studio 2003 compact framework was set up for ARM4 and ARM4T but the
ARM4I installed with SP2 in a different folder. When I build a cab file the
4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe
"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf
" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab file to
install the app on the device it errors out.

How do I update my application in Visual studio to support the new ARM4I CPU
so it will build a proper executable and create a CAB file using the VS
tools?

I have searched hi and low for how to reconfigure the Studio to use the SP2
updates. Do I have to reinstall SP2 and specify the VS folder? It seems to
me that, while it may install there, visual studio won't "See" it regardless
until I tweak some configuration somewhere.

Kindest Regards,

Cindy Cruciger

 

[Chris Tacke, eMVP]

Use the ARM4T stuff.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

I was recently given an ARM4I CPU device to test. My original install of
Visual Studio 2003 compact framework was set up for ARM4 and ARM4T but the
ARM4I installed with SP2 in a different folder. When I build a cab file the
4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe
"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf
" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab file to
install the app on the device it errors out.

How do I update my application in Visual studio to support the new ARM4I CPU
so it will build a proper executable and create a CAB file using the VS
tools?

I have searched hi and low for how to reconfigure the Studio to use the SP2
updates. Do I have to reinstall SP2 and specify the VS folder? It seems to
me that, while it may install there, visual studio won't "See" it regardless
until I tweak some configuration somewhere.

Kindest Regards,

Cindy Cruciger

There are several frequently asked questions related to Compact Framework
service packs, so I thought I'd shed some light.

Q0: Do I want to use SP2?

Yes, you do. The list of fixes speaks volumes. The list is available on the
download page

Q1: How do I use SP2 (or SP1) for development:

If you are a developer, you will want a Developer redistributable:

http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en

This download is for Visual Studio 2003 users
Developer redistributable contains ARM, SH3, MIPS and x86 cabs for 2002 and
2003 devices and can be used to install SP2 on the devices as well as on the
emulators. Developer redistrnbutable *does not* contain the installer - you
will need to deploy and launch cabs yourself.
Once the CAB is on a device(emulator), you can click on it in File Explorer
and it will install automatically
To copy cab onto device you can use ActiveSync Explorer. To copy CAB onto
the emulator you can use EmuCpy utility from
http://www.alexfeinman.com/download.asp?doc=emucpy.zip (command line), or
http://www.alexfeinman.com/download.asp?doc=EmulatorCopy.msi (GUI tool.
Integrates with Windows Shell, provides context menu option Copy To
Emulator - beta )

The other redistributable is for everyone (not only developers)

http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en

This one contains an installer that will attempt to update the connected
device (and can be launched again later to update another device)
If you provide an application to the end-users, you can direct them to this
download or bundle it with your application on CD


Q2: Can I update my Visual Studio installation to use SP2.

Currently, Microsoft position on this is that this is not recommended. I'm
not aware of this doing any harm, but it is entirely unnecessary, at least
not with devices. With emulators, which often end up being hard-reset,
reinstalling SP2 becomes a bit of a chore. EmuCpy utility makes it somewhat
less painful and if there is a demand, I could add an option to
automatically launch copied file.

If you decide to update VS installation with SP2 cabs, use the Developer
redist. Also make absolutely sure you copy cabs into correct directories
under <Visual Studio root>\CompactFrameworkSDK\v1.0.5000\Windows CE\wceX00

Alex Feinman

 

[Stephanie Gardner]

IDM Is Brill!!!!!
Everyone has to have this its so brill!!!!! Try it out the people who don't use it

www.internetdownloadmanager.com/index.html?affilid=9875-194</a>

 

[Peter B]

So ...\wce400\netcf.all.wce.armv4t.cab is replaced by
....\wce400\netcf.all.wce.armv4I.cab?

What about ...\wce300\wce420x86? There is 1 netcf.ppc3.x86.cab file in SP2
package, should it replace cabs in both x86 and wce420x86?

thanks,

Peter

Use the ARM4T stuff.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

I was recently given an ARM4I CPU device to test. My original install of
Visual Studio 2003 compact framework was set up for ARM4 and ARM4T but the
ARM4I installed with SP2 in a different folder. When I build a cab file the
4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe

"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf

" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab file to
install the app on the device it errors out.

How do I update my application in Visual studio to support the new ARM4I CPU
so it will build a proper executable and create a CAB file using the VS
tools?

I have searched hi and low for how to reconfigure the Studio to use the SP2
updates. Do I have to reinstall SP2 and specify the VS folder? It

seems

to
me that, while it may install there, visual studio won't "See" it regardless
until I tweak some configuration somewhere.

Kindest Regards,

Cindy Cruciger

on
the

http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en

2002
and on
the installer -
you

http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en

 

[PCUser]

Tried that. It didn't work.

Use the ARM4T stuff.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

I was recently given an ARM4I CPU device to test. My original install of
Visual Studio 2003 compact framework was set up for ARM4 and ARM4T but the
ARM4I installed with SP2 in a different folder. When I build a cab file the
4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe

"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf

" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab file to
install the app on the device it errors out.

How do I update my application in Visual studio to support the new ARM4I CPU
so it will build a proper executable and create a CAB file using the VS
tools?

I have searched hi and low for how to reconfigure the Studio to use the SP2
updates. Do I have to reinstall SP2 and specify the VS folder? It

seems

to
me that, while it may install there, visual studio won't "See" it regardless
until I tweak some configuration somewhere.

Kindest Regards,

Cindy Cruciger

on
the

http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en

2002
and on
the installer -
you

http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en

 

[Chris Tacke, eMVP]

Strange. I have several PXA255 devices which all have 4I-built images.
I've been able to use the 4T and pure 4 builds without any problems. Have
you tried just the 4?

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

Tried that. It didn't work.

Use the ARM4T stuff.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

I was recently given an ARM4I CPU device to test. My original install of
Visual Studio 2003 compact framework was set up for ARM4 and ARM4T but the
ARM4I installed with SP2 in a different folder. When I build a cab

file
the

4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe

"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf

" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab file to
install the app on the device it errors out.

How do I update my application in Visual studio to support the new

ARM4I
CPU

so it will build a proper executable and create a CAB file using the VS
tools?

I have searched hi and low for how to reconfigure the Studio to use

the
SP2

updates. Do I have to reinstall SP2 and specify the VS folder? It

seems

to
me that, while it may install there, visual studio won't "See" it regardless
until I tweak some configuration somewhere.

Kindest Regards,

Cindy Cruciger

There are several frequently asked questions related to Compact Framework
service packs, so I thought I'd shed some light.

Q0: Do I want to use SP2?

Yes, you do. The list of fixes speaks volumes. The list is available on
the
download page

Q1: How do I use SP2 (or SP1) for development:

If you are a developer, you will want a Developer redistributable:

http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en as

on line),
or

http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en

recommended.
I'm

 

[PCUser]

Here's how my testing progressed:
I tried installing the compact frame work for 4 - errors
I tried installing the compact frame work for 4T - errors
I found and installed the 4I compact framework. - working - happy

From my application which is working fine on an ARM4 I took the cab file for
4 - errors
I tried the cab file for 4T - errors
I found the executable to make a cabfile routing the logic to the 4I that
you see below. That succeeded. I moved it to the device - same errors.
So. Is it possible to build specifically for a 4I the way we do for 4T and
4? Or is there something else I am missing or that I did incorrectly?

The application works on three other devices with three different
processors. I didn't rebuild it for this device - just created a new cab
file.

Thanks,

C

Strange. I have several PXA255 devices which all have 4I-built images.
I've been able to use the 4T and pure 4 builds without any problems. Have
you tried just the 4?

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

Tried that. It didn't work.

Use the ARM4T stuff.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net


I was recently given an ARM4I CPU device to test. My original

install
of

Visual Studio 2003 compact framework was set up for ARM4 and ARM4T

but
the

ARM4I installed with SP2 in a different folder. When I build a cab file
the
4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe

"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf

" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab

file

to available
on

http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en

as

http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en them

to

 

[PCUser]

What are the chances that the image wasn't built for a 4I? This is an
experimental device after all?

Strange. I have several PXA255 devices which all have 4I-built images.
I've been able to use the 4T and pure 4 builds without any problems. Have
you tried just the 4?

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

Tried that. It didn't work.

Use the ARM4T stuff.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net


I was recently given an ARM4I CPU device to test. My original

install
of

Visual Studio 2003 compact framework was set up for ARM4 and ARM4T

but
the

ARM4I installed with SP2 in a different folder. When I build a cab file
the
4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe

"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf

" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab

file

to available
on

http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en

as

http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en them

to

 

[Chris Tacke, eMVP]

WHen you deploy through debug in Studio, the output window will tell you
exactly what CAB file it's pushing down. You might take a look and see what
it thinks is the right file. That's all I can think of offhand.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

Here's how my testing progressed:
I tried installing the compact frame work for 4 - errors
I tried installing the compact frame work for 4T - errors
I found and installed the 4I compact framework. - working - happy

From my application which is working fine on an ARM4 I took the cab file for
4 - errors
I tried the cab file for 4T - errors
I found the executable to make a cabfile routing the logic to the 4I that
you see below. That succeeded. I moved it to the device - same errors.
So. Is it possible to build specifically for a 4I the way we do for 4T and
4? Or is there something else I am missing or that I did incorrectly?

The application works on three other devices with three different
processors. I didn't rebuild it for this device - just created a new cab
file.

Thanks,

C

Strange. I have several PXA255 devices which all have 4I-built images.
I've been able to use the 4T and pure 4 builds without any problems. Have
you tried just the 4?

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net

Tried that. It didn't work.


Use the ARM4T stuff.

--
Chris Tacke, eMVP
Co-Founder and Advisory Board Member
www.OpenNETCF.org
---
Windows CE Product Manager
Applied Data Systems
www.applieddata.net


I was recently given an ARM4I CPU device to test. My original install
of
Visual Studio 2003 compact framework was set up for ARM4 and ARM4T but
the
ARM4I installed with SP2 in a different folder. When I build a

cab
file

the
4I version doesn't get built. I tried to fake it out by writing the
following bat file
[
cd\
cd "C:\Program Files\Microsoft Visual Studio .NET
2003\CompactFrameworkSDK\v1.0.5000\bin"
cabwiz.exe

"C:\eHomeDelivery\WindowsCE\eHomeDelivery\obj\Release\eHomeDelivery_WCE4.inf

" /err MyDeviceApp.err /cpu arm4i
]
This creates the 4I cab files but I'm guessing the inf file from my
application isn't kosher with the 4I because when I use that cab

file

to
install the app on the device it errors out.

How do I update my application in Visual studio to support the new ARM4I
CPU
so it will build a proper executable and create a CAB file using

the
VS

tools?

I have searched hi and low for how to reconfigure the Studio to

use
the

SP2
updates. Do I have to reinstall SP2 and specify the VS folder? It
seems
to
me that, while it may install there, visual studio won't "See" it
regardless
until I tweak some configuration somewhere.

Kindest Regards,

Cindy Cruciger

There are several frequently asked questions related to Compact
Framework
service packs, so I thought I'd shed some light.

Q0: Do I want to use SP2?

Yes, you do. The list of fixes speaks volumes. The list is available
on
the
download page

Q1: How do I use SP2 (or SP1) for development:

If you are a developer, you will want a Developer redistributable:

http://www.microsoft.com/downloads/...43-09B3-46D8-BA28-BC494BC20D26&displaylang=en

well
as

http://www.microsoft.com/downloads/...DA-FC5D-41CC-AC04-7BB50A134556&displaylang=en

them

unnecessary,

at