UNSUBSCRIBE
--
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk take
Since this thread was about generating a MSM in WiX and consuming it in
InstallShield I wanted to point out some behavior differences in WiX and
InstallShield as it relates to ModuleDependencies.
WiX: Module dependencies are informative only. They don't constitute an
implicit MergeRef and w
What you are describing is the expected behavior of the Windows Installer.
The MSI SDK explains the Windows Installer behavior in a lot of detail...
but is pretty dense material.
On Fri, Jul 1, 2011 at 8:32 AM, Anil Patel wrote:
> Hello,
>
> As this is my first time in authoring WiX source files
What version of Burn are you using? Can you share out the detect section of
the Burn log file?
On Mon, Jul 4, 2011 at 4:58 AM, Rob Hamflett wrote:
> Ah. I haven't looked at Burn. Sorry. Hopefully someone else has the
> answer to that one.
>
> Rob
>
> On 04/07/2011 12:13, Alexander Krivács Sch
PS: MergeRedirectFolder isn't a special name or anything. It's just what the
template calls the Directory that is parented to TARGETDIR and thus can be
retargeted by the merge process. The gory details are spelled out in the
MSI SDK: http://msdn.microsoft.com/en-us/library/aa367787(v=VS.85).aspx
Hello Sameer.
The error you are getting is because a "commit" custom action is to be run
inside the installation script.
And you give a contradictory command by telling
After='InstallFinalize'
Try changing that to
Before='InstallFinalize'
and you should get back in your feet with the linker.
H
Ah. I haven't looked at Burn. Sorry. Hopefully someone else has the answer
to that one.
Rob
On 04/07/2011 12:13, Alexander Krivács Schrøder wrote:
> Hi Rob.
>
> I probably should have mentioned that the bootstrapper we're using is WiX's
> burn, and the managed GUI we're making is for it. The
Hi Rob.
I probably should have mentioned that the bootstrapper we're using is WiX's
burn, and the managed GUI we're making is for it. The BootstrapperApplication
class has an event called DetectPackageComplete. In this event, one gets the
following EventArgs class:
public class DetectPacka
If you were using native code, then you'd want MsiEnumRelatedProducts(). A
Google search provides a
bunch of links with info on how to call it from C#. I don't know if you're
using C# or VB, but a
bit of searching around that function name should get you there.
Rob
On 04/07/2011 09:52, Alex
I guess in that case then the user would need to perform a repair to put the
inf file back before
doing the uninstall. Either that or you need to keep a copy of the INF file
somewhere else. Maybe
have a DLL custom action that contains a copy of the inf, extracts it, and then
calls DPInst. T
Hey.
According to the Windows Installer specifications, we change the Product Code
of our product with every release (We just use ) and we
keep the Upgrade Code the same. That way, when the individual MSIs are run, if
any previous versions exist, they are first uninstalled.
At the moment, we'r
Oh..what I meant was , the file are deleted manually after the installation.
So, when launching the installer for uninstallation, the installer couldn't
find that inf.
2011/7/4 Rob Hamflett
> You could schedule it before the RemoveFiles action.
>
> Rob
>
> On 04/07/2011 08:56, Yuk Hei Pang wrote
On 04/07/2011 08:56, Yuk Hei Pang wrote:
> Hi, I am currently having a msi created with wix 3.5 to install a driver
> package along with an application.
> The following custom action is used for uninstalling the driver package.
>
>
I know this doesn't answer your question, but I think Microsoft
r
Hi WiX gurus,
Once the files from my embedded MSM have been installed can I launch this
other install before the main install finishes? Or should rip the MSM out and
chain the 2 MSI's instead?
Thanks,
Dominique Louis.
##
Att
You could schedule it before the RemoveFiles action.
Rob
On 04/07/2011 08:56, Yuk Hei Pang wrote:
> Hi, I am currently having a msi created with wix 3.5 to install a driver
> package along with an application.
> The following custom action is used for uninstalling the driver package.
>
>
Hi, I am currently having a msi created with wix 3.5 to install a driver
package along with an application.
The following custom action is used for uninstalling the driver package.
but if the file mydriver.inf is deleted , DPInst would not be able to remove
the driver package.
Is there any way
16 matches
Mail list logo
