I have an exe which installs my system, I am trying to create a small update
which will amend 6 dlls and add a new file.
As a small update I have changed the version, updating from x.x.0 to x.x.1, of
the bundle itself and both chained msi's. I have left the product id
unchanged, package id
I think the standard is to have the deferred action make a call to
MsiProcessMessage (not MessageBox), passing in a reference to the Error table
(that way your displayed strings won’t live inside dll resource files).
https://msdn.microsoft.com/en-us/library/aa371247%28v=vs.85%29.aspx
On Feb
You can have a type-34 custom action launch “C:\Windows\explorer.exe path”.
CustomAction Id=“LaunchExplorer” Directory=“[WindowsFolder]”
ExeCommand=“explorer.exe quot;[MyPath]quot;” Execute=“whatever”
Return=“ignore” /
On Feb 4, 2015, at 9:52 AM, Tall Tyke chris.mo...@eque2.com wrote:
Hi,
My per-user, non-elevated install's directory structure looks like this...
Directory Id=TARGETDIR Name=SourceDir
Directory Id=AppDataFolder
Directory Id=XXX Name=Xxx/
/Directory
/Directory
I use it in ComponentGroup like this...
ComponentGroup Id=MyComponents
The proper way is RemoveFile. Windows Installer supplies these things
so you don't need to write code and get yourself in this kind of
trouble :)
---
Phil Wilson
On Wed, Feb 4, 2015 at 7:47 PM, Sarvagya Pant sarvagya.p...@gmail.com wrote:
Hi Phil and Jacob. One approach I could do
5 matches
Mail list logo