I have the ComponentsLocation and CopyComponents set to 'Relative' and
'True' respectively. I'm also seeing two new folders, DotNetFX40 and
WindowsInstaller4_5, under my project directory and they seem to have the
related executables. So does it mean I should be copying these two folders
to the roo
What happens when I have the SQL Server 2008 Express R2 bootstrapped, and
the target machine already has the SQL Server 2008 Enterprise or SQL Server
2005 Enterprise/Express installed? I am asking because I can't find in the
bootstrapping section of the wixproj file any means to do a conditional
i
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", http://msdn.microsoft.com/en-us/libra
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 t
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
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
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 in
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
> Subject: Re: [WiX-users] Documentation for Burn
> To: Gene
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*
..
NOT
Installed
..
*CustomActions.wxs*
..
..
Intention is to launch the application once the instal
Ok, I've got the common file folder setup.
Needed files...
After the install, I echo %Path% and the does show the addition of the NW
Shared directory. Th
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: wix-users@lists.sourceforge
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 E
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)
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
You can access the x64 registry from within a x86 process. See
http://msdn.microsoft.com/en-us/library/ms724878%28v=vs.85%29.aspx. The
RegistrySearch element supports switching between x86 and x64 registry
by using Win64 attribute.
Michael
Am 29.06.2011 09:55, schrieb Kryschan:
> Kryschan wro
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
>
>
>Root="HKLM"
> Action="createAndRemoveOnUninstall"
> Key="SOFTWARE\MyCompany"
> >
>
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 f
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 pe
Hi i use wix 3.5 with this code to create a shortcut
But after uninstallation the shortcut always exists.
The Setup installs an AddIn so the shortcut directory is not empty after
remove the "SQLManualStartMenuShortcut"
Mit freundlichen Grüssen
Peter Glatzer
_
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 defi
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
> It seems like Wine hasn't implemented the MsiGenerateTransform() function.
> Without that Torch isn't going to be mu
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.
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 f
23 matches
Mail list logo