S
Serge Wautier
Env.: WM6, CF 3.5
Hi All,
My question is more WM than CF oriented. So please feel free to redirect me
to a more appropriate NG if you know one.
I wanted to provide my users an upgrade.cab file that is much smaller than
the initial setup.cab: It contains only the new exe and not all related dlls
and data files). The problem is when users install it, it first uninstalls
the whole app (after prompt). How can I avoid this?
I assumed that WM identified the original app based on the name and path of
exe file in my upgrade cab. But now that I think of it, there might be a
better explanation: To create upgrade.cab, I simply copy/pasted the VS setup
project, renamed it and removed all the unnecessary stuff. Would the package
contain some kind of id such as a GUID that I should modify?
TIA for your lights,
Serge.
Hi All,
My question is more WM than CF oriented. So please feel free to redirect me
to a more appropriate NG if you know one.
I wanted to provide my users an upgrade.cab file that is much smaller than
the initial setup.cab: It contains only the new exe and not all related dlls
and data files). The problem is when users install it, it first uninstalls
the whole app (after prompt). How can I avoid this?
I assumed that WM identified the original app based on the name and path of
exe file in my upgrade cab. But now that I think of it, there might be a
better explanation: To create upgrade.cab, I simply copy/pasted the VS setup
project, renamed it and removed all the unnecessary stuff. Would the package
contain some kind of id such as a GUID that I should modify?
TIA for your lights,
Serge.