We'll definitely want to look at the GenerateBootstrapper package
definitions and see how much we can borrow/steal.
On Tue, Jun 28, 2011 at 3:08 PM, Dan Puza dp...@ultra-scan.com wrote:
Is there a community location where standard package definitions are
publicly available in one common
Burn will support an immediate (aka: forced) restart. You should map exit
codes from the MSI4.5 installer using the ExeEngine/ExitCode element so that
restart means force restart.
Actually, looking at the documentation, it looks like candle is missing
suport for that. Heh, the engine (Burn)
Kryschan wrote:
I'm trying create a bootstrapper containing some 64bit MSI packages, which
(of course) shall be installed on a x64 system. As the MSIs are installed
in silent mode, my bootstrapper should gather the required information
from the user, which also includes reading values from
Did you find any solution?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Application-launched-from-setup-is-displayed-in-background-tp5960313p6528067.html
Sent from the wix-users mailing list archive at Nabble.com.
Dear Rob,
Thank you for your answer. I filed a bug report for the Wine developers at
http://bugs.winehq.org/show_bug.cgi?id=27646.
Best regards, Zoltan
2011/6/28 Rob Mensching r...@robmensching.com
It seems like Wine hasn't implemented the MsiGenerateTransform() function.
Without that Torch
I once asked a question on StackOverflow and never really got an answer
for various MSFT packages there is usually a 'fwlink' URL for web download.
Are these documented anywhere? Can they be counted on in the future? This
is a critical building block for community bootstrapper
Hi i use wix 3.5 with this code to create a shortcut
Directory Id=ProgramMenuDir Name=XXX
Component Id=CompProgramMenu Guid=e89955e2-daae-4b83-b3a4-644ee504c6ee
Shortcut Id=SQLManualStartMenuShortcut
Name=!(loc.MANUALDESCRIPTION)
Description=!(loc.MANUALDESCRIPTION)
I am out of the office until 06/30/2011.
I will be out of the office, with limited email and phone access.
Note: This is an automated response to your message [WiX-users] Remove
Shortcut on uninstall sent on 6/29/2011 7:31:03 AM.
This is the only notification you will receive while this
For your RemoveFile element to work you'll need to specify .lnk as part of
the filename otherwise Windows Installer won't find the file.
However you shouldn't need a RemoveFile to remove a Shortcut which your
installation creates unless it's modified in some way after installation. Same
goes
This works great. Thanks!
On Tue, Jun 28, 2011 at 10:43 AM, Castro, Edwin G. (Hillsboro)
edwin.cas...@fiserv.com wrote:
Create a x86 msi package and use the following authoring
Component Id=C_UriInRegistry Guid=*
RegistryKey Id=RG_RegistryKey
Root=HKLM
You can use the util:RegistrySearch element in your Bundle definition to
read 64bit values.
On Wed, Jun 29, 2011 at 12:55 AM, Kryschan
christian.hennig@wincor-nixdorf.com wrote:
Kryschan wrote:
I'm trying create a bootstrapper containing some 64bit MSI packages,
which
(of course)
I've been googling the net, off and on, for 3 weeks now, and I can't find any
documentation for Burn.exe anywhere. I understand that
it is still under development (and has been for almost a year now), but unless
the developers are planning to wait till the last minute
(BIG mistake in my opinion)
Thank you very much Rob for this information.
The exit code thing was also something I had been meaning to ask about. I had
written my own simple MapExitCode.exe and RunCommand.exe to use within an
ExePackage because I couldn't find that type of functionality in Burn. Glad to
hear about
There's a section within the WiX 3.x manual from the WiX home page.
http://wix.sourceforge.net/manual-wix3/authoring_bundle_intro.htm
-Original Message-
From: Dane Anderson (Wicresoft) [mailto:v-dan...@microsoft.com]
Sent: Wednesday, June 29, 2011 1:03 PM
To:
Ok, I've got the common file folder setup.
Directory Id=TARGETDIR Name=SourceDir
Directory Id=ProgramFilesFolder Name=PFiles
Directory Id=CommonFilesFolder Name=CommonFilesFolder
Directory Id=NWSHARED Name=NW Shared
Component
What am I missing ?
I would like the setup to launch my UI application after installation
completes successfully.
My .wxs files are modularized as:
*InstallSequences.wxs*
Fragment
InstallExecuteSequence
..
Custom Action=LaunchAppCA After='InstallFinalize'NOT
Installed/Custom
..
Thank you. While examining that site and the ones it has links to (recursive) I
found a broken
Link:
http://wix.sourceforge.net/manual-wix3/authoring_burn_package_manifest.htm
Date: Wed, 29 Jun 2011 17:13:51 +
From: Dan Puza dp...@ultra-scan.com
Subject: Re: [WiX-users] Documentation
Thanks David, that worked for me!
On another note, can anyone confirm that when something has been
bootstrapped its executable/installer file gets embedded in the MSI? That's
what we would like to happen in our MSI as we want to include everything in
the media and avoid any downloading from the
As an update to my post below ...
I enabled Assembly Binding Logging and according to the log file, windows was
not even checking the system path (%Path%) .. it just made some checks in the
current directory using probing search technique and then seeing how it did not
find anything, it threw
That depends on the value of the ComponentsLocation attribute of the
GenerateBootstrapper Task in your wixproj file, as well as the CopyComponents
attribute.
See: http://msdn.microsoft.com/en-us/library/ms164294.aspx
For example, if ComponentsLocation=Relative, and CopyComponents=true, then
Greetings,
Ok, I've got to ask this question even if it makes me look like a wix idiot
(I am, but keep it quiet) as I've spent way too much time trying to find the
answer on my own.
I've created a dialog (code below) that contains a PathEdit control, a
DirectoryList (and some other controls) so
I agree this is very much a .NET issue rather than WiX.
Check out How the Runtime Locates Assemblies,
http://msdn.microsoft.com/library/yx7xezcf
Pay particular attention to the probing section, Step 4: Locating the Assembly
through Codebases or Probing,
22 matches
Mail list logo
