Use of an Inf file when manually installing.

[John Atkins]

Sometime ado I created my own RAPI application on the PC to install my PPC
applcation on the PPC. I use an XML file of my own to tell my installation
program how and where to install my files. I use WCELoad from within the
install program to install the Compact Framework and/or SQL Server CAB
files.

My problem is that I need to install the program onto a WM 2003 SE device
and hence I require an INF file to get rid of the Legacy Application
Installation warning message. That is, I need an INF file with the
Buildmax=0xE0000000 line in it.

Can anyone tell me what name to give the INF file and where it should be
installed to so that the WCELoad program does not give the warning messages
when it installs SQL Server etc?

John.

 

[Peter Foot [MVP]]

This INF file is the one used to build your application cab files. If you
use the Build CAB function of Visual Studio you can go in and edit this file
in the /obj/Release/ folder within your project folder and then execute the
BuildCab.bat file to rebuild the cabs with the new settings.

Peter

 

[John Atkins]

Unfortunatelty I don't create any CAB files so I don't have an inf file. My
RAPI application creates folders, shortcuts etc and copies the CF and SQL
Server CABs to the PPC along with my exe. I then invoke WCELoad using
CreateProcess and execute the CAB files to install them.

With this approach, do you know if there is any way I can avoid the popup
dialog on the PPC complaining that the application was created for an older
version of WM 2003. The dialog appears a few times so I think it appears
when WCELoad executes each of the CF and SQL Server CABs. Incidentally,
these CABs are the ones that came with VS.Net.

John.

 

[Peter Foot [MVP]]

I see sorry. In the case of the SqlServerCe and NETCF cabs, these have not
been updated to be marked as WM2003 compatible so the warning will appear.
This may be addressed in a future service pack.

Peter

 

[John Atkins]

Peter, thank you very much.

I hope this is tackled sooner rather than later. It looks very bad when a
new user installs software and the first thing they see is a warning that
the software is old and might not work!

John.