That is what I posted earlier, but without seeing that area in the final MSI
file it's not clear that's actually what's going on.
Phil W
-Original Message-
From: David Connet [mailto:d...@agilityrecordbook.com]
Sent: Friday, March 30, 2012 1:59 PM
To: General discussion for Windows Inst
If you sequence before InstallFinalize, you need to also schedule
InstallExecute (and REP is sequenced after that.)
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371197%28v=vs.85%29.aspx
Dave
On 3/30/2012 1:40 PM, Wilson, Phil wrote:
> There may not be enough context in that WiX to
There may not be enough context in that WiX to see what actually gets generated
in the MSI file. That sequence is certainly allowed because other tools have
been generating it for years.
Phil W
-Original Message-
From: Meera Jindal [mailto:meera.jin...@gmail.com]
Sent: Thursday, Marc
Hi Rob, I'm not sure what you mean by debug. Does burn have a verbose command
line option? I'm not that familiar with window installer and wix. Just
started using wix for msi 6 months ago and burn a week ago.
Wes
-Original Message-
From: Rob Mensching [mailto:r...@robmensching.com]
Hi,
Complete WiX beginner here. I've managed to create a Start Menu folder with
shortcuts to files in it (by using Shortcut elements nested inside the File
element of the destination, which in turn is inside a Component element).
But I want to create a shortcut to the installation *directory*
After some trial and error I've found that adding the following to my
Component (containing the Shortcut)
...makes it all work. I'm a bit concerned because I've used the
Software\[Manufacturer]\[ProductName] registry key as the "key path" for
another component (the start menu folder itself)
Hi,
Complete WiX beginner here. I've managed to create a Start Menu folder with
shortcuts to files in it (by using Shortcut elements nested inside the File
element of the destination, which in turn is inside a Component element).
But I want to create a shortcut to the installation *directory* its
Actually, this is a bug. The wixstdba should go straight back to progress
after a force reboot and it obviously is not. Can you open the bug?
On Thu, Mar 29, 2012 at 12:55 AM, Sergey Yukhno <
sergey.yuk...@visutechsystem.by> wrote:
> Hello.
> Can I switch off install dialog after forceReboot?
> E
ThmViewer.exe might help as well. It isn't perfect right now but it can
rapidly speed up thm development.
On Thu, Mar 29, 2012 at 12:12 PM, robert_h_yang wrote:
> I started tinkering with this, and got something like this to work :
>
> Id="WixStandardBootstrapperApplication.RtfLicense">
>
Based on what you've described it sounds like a bug. Can you debug it and
see? Can you open a bug if it looks like something is messed up?
On Thu, Mar 29, 2012 at 8:23 AM, Wesley Manning wrote:
> Hi,
>
> I create a burn exe and as long as I don't specify a "LogoFile" attribute
> for the elemen
Burn engine does not help with that today. Your BA can do it.
On Fri, Mar 30, 2012 at 5:09 AM, Vadym Verba wrote:
> Hello.
>
> I have a question: my BA shows feature selection screen, where user can
> choose what features of what packages he wants to install, and I wonder is
> there any mechanis
Well, the only benefit to running smoke.exe as an Exec process is that I can
set the ConinueOnError process to keep it from breaking the build. I also have
an interesting error message from smoke.exe during the run:
smoke.exe: An unexpected Win32 exception with error code 0x643 occurred: Action
May be not helpful enough. Enabling validation still gets me:
light.exe: Error executing ICE action 'ICE01'. The most common cause of this
kind of ICE failure is an incorrectly registered scripting engine. See
http://wix.sourceforge.net/faq.html#Error217 for details and how to solve this
probl
Any takers? Any tips?
Thanks
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Native-language-OS-install-vs-language-pack-tp7414229p7421594.html
Sent from the wix-users mailing list archive at Nabble.com.
When I ran into that error/warning, it was because I had some custom actions
that where scheduled before the removeexistingproducts.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/RemoveExisitngProducts-and-deferred-CA-tp7418399p7421588.html
Sent
Well, that was a helpful clue. I was able to get smoke.exe to run without
error on my newest Server 2008 R2 build agent by:
1) disabling the Application Identity Service;
2) enabling for autostart and starting the Application Information service;
3) enabling for autostart and starting the Applic
Hello.
I have a question: my BA shows feature selection screen, where user can
choose what features of what packages he wants to install, and I wonder is
there any mechanism in BA that I can use to validate if there is enough disk
space for installation? For simple msi launch there are CostInitial
17 matches
Mail list logo
