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
Hey, Alexander.
Try to use DetectRelatedMsiPackage. It detects installed products based on
Upgrade Code, but not on Product Code.
Best regards,
Vadym
--
Date: Mon, 4 Jul 2011 10:52:50 +0200
From: Alexander Kriv?cs Schr?der
Hi Rob,
Appreciate your reply on this and will look through the MSI SDK to
understand this.
Regards,
Anil.
On Mon, Jul 4, 2011 at 6:29 PM, Rob Mensching r...@robmensching.com wrote:
What you are describing is the expected behavior of the Windows Installer.
The MSI SDK explains the Windows
Hi,
I want to start an application after burn has finished setup. This
appliation needs administrator privileges. Is it possible start the
application without prompting for elevation (using the same elevation
mechanism as the setup)?
Michael
Upon uninstallation, I have a RegistrySearch to get the installation
path that I stored during install . And this path is than used for
searching a file with directorySearch.
This works find in XP but in Win 7 the registrySearch seems failed
because it get nothing.
I have set the InstallPrivilege
If you run a process that requires admin privileges then it will prompt, unless
you run it from a
process that is already elevated. If Burn is elevated then you'll be fine,
otherwise you'll get the
prompt.
Rob
On 05/07/2011 11:30, Michael Stoll wrote:
Hi,
I want to start an application
Check a verbose log.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the Virtual Environment**
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered
I'm using Burn v3.6.1803.0.
Here's the detect section of the log file:
[1708:1F44][2011-07-05T12:35:51.683+01:00]: Detect 11 packages
[1708:1F44][2011-07-05T12:35:52.097+01:00]: Condition 'Netfx4FullVersion AND
(NOT VersionNT64 OR Netfx4x64FullVersion)' evaluates to true.
Is it Win7 64 bit? If so, are you sure the correct registry is being
checked/written to (32-bit vs. 64-bit)?
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, July 05, 2011 6:57 AM
To: General discussion for Windows Installer XML toolset.
Subject:
Is the problem on a 32 bit or 64 bit system?
Make sure the registry search matches the bit level that was set for component
containing the initial registry write.
-Original Message-
From: yheip p [mailto:zyhp...@gmail.com]
Sent: Tuesday, July 05, 2011 5:51 AM
To: General discussion for
What kind of code are you trying to run? You can definitely run an ExePackage
(EXE file) at any point before, after, between installing any of your 3 MSI
files, without writing a complete BA. It's true you cannot run the UI inside
the MSI though.
However, and this is an ugly hack, but I have
I don't know much about how Burn works, sorry. The only thing that springs to
mind is if Burn
itself was elevated.
Rob
On 05/07/2011 14:54, Michael Stoll wrote:
I tried starting the application in the close command of the mba. But
then the user is prompted twice for administration
Okay, Vadym is pointing you in the right direction. DetectPackage tells you
the state of *this* package where package is defined by ProductCode. You
will get superseded from DetectPackage only when you try to install the same
ProductCode with a lower version number (basically a minor downgrade).
Burn doesn't have anything built in to do this yet, although we've talked
about it a lot. Currently, you'd have to schedule your ExePackage as the
last thing in the Chain and mark it @PerMachine=yes. Then you'd have to
have your BA or a very cleverly designed InstallCondtiion control when the
Hi,
I was wondering if there were techniques, methods for accommodating both
single-level and multi-level install directory structures using the same set of
Wix XML source files?
If I'm not mistaken, the directory structure is currently reflected directly in
the XML code. Example:
Directory
Off the top of my head, so no guarantees given ...
You could do it if you were prepared to pass (or write a program to pass)
public directory properties on the command line. Something like this:
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder
Hi all - I'm working on an install with a somewhat large number of older COM
objects and .NET classes exposed to COM. For the most part, heat.exe works
very well to move away from self-registration; very impressive.
We have had some issues, like how to deal with the inability of heat to
Hi David,
Thanks for the information. I'm writing the registry data to
HKLM\Software\Classes since the is a per machine installer.
Thanks a lot,
Miaohsi
-Original Message-
From: David Watson [mailto:dwat...@sdl.com]
Sent: Thursday, June 30, 2011 10:01 AM
To: General discussion for
Hello All,
I created a bootstrapper that installs .NET 3.5 on the target machine if it is
not present. The problem is that after its installation, the bootstrapper
prompts the user to reboot the machine. Is there a way to avoid this prompt?
Thanks a lot for your help.
Regards,
Miaohsi
***
I believe this has been seen before IIRC. Rob might still have an old
code review for the fix. Otherwise I can look for it when I am back
from vacation.
Sent from my Windows Phone From: robert_y...@non.agilent.com
Sent: Tuesday, July 05, 2011 9:55 AM
To: wix-users@lists.sourceforge.net
Subject:
So I added a feature request (3354758). I stick with the second prompt
for now, because I want to start the application when the boostrapper
closes.
Michael
Am 05.07.2011 17:20, schrieb Rob Mensching:
Burn doesn't have anything built in to do this yet, although we've talked
about it a lot.
I had a similar problem, and started hacking at a custom heat extension
to do a similar job. However, I then realized what I was doing would
violate many component rules due to the multiplicity of installation
instances I need to support.
I am currently prototyping a different approach using
It is a 32bit win7,
I tried to call the uninstallation from command prompt
msiexec /x myinstaller.msi
and the registry search works.
It also works when choosing uninstall in the right-click menu as well as
uninstalling from Control panel.
But it only fails when I choose Remove from the Installer
I have checked to log
msiexec /i myinstaller.msi /l* log
for both XP and Win7 32bit
and right after ExcuteAction
MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property INSTALLLOCATION
MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property FILEEXISTS
MSI (s) (58:C0) [11:34:23:511]:
Adding Secure=yes to that two property solve to problem. thanks:)
2011/7/6 yheip p zyhp...@gmail.com
I have checked to log
msiexec /i myinstaller.msi /l* log
for both XP and Win7 32bit
and right after ExcuteAction
MSI (s) (58:C0) [11:34:23:511]: Ignoring disallowed property
25 matches
Mail list logo
