Thank You Nick, but that's not exactly, what i need, because me and my
customers are using the EXE-file, which is generated by the build of the
bootstrapper-project.
Is there a chance to find the path of the final installfolder by - per
example - Bootstrapper.Engine.StringVariables[...]?
I have mad
On 12/02/2014 10:15 PM, Phil Wilson wrote:
> If you're saying that two MSI products are incompatible and you want
> to make sure that a product cannot be installed if another one is
> already installed then some choices are:
>
> You use Upgrade and UpgradeVersion elements with OnlyDetect="yes" that
An actual installation is detected by the product name and the GUID in the
registry.
Maybe You have a header like this in Your Product.wxs-file:
But when You change the Id to "*", then bye ach Rebuild a new GUID will be
generated.
In case You have no other detect mechanisms in Your Product
I was able to run the EXE package twice by changing the name.
I have requirement for MSI to work as similar to EXE.
On Wed, Dec 3, 2014 at 7:54 PM, Patrick Pirzer
wrote:
> The big question is: Why do You want to run Your MSI twice?
>
>
> -Ursprüngliche Nachricht-
> Von: Dileep S [mailto:
Does the workaround from the bug work for you? (removing the default value)
On Wed, Dec 3, 2014 at 12:45 PM, Rob Mensching wrote:
> Sounds like: http://wixtoolset.org/issues/4609/
>
> _
> Short replies here. Complete answers over ther
On 02-Dec-14 16:44, Steve-Ogilvie wrote:
> I have modified the theme for the boostrappers I am using
> but I noticed on the Welcome screen hitting the enter key does not advance
> to the next screen
>
> is this a bug in 3.8 or as designed?
Themes don't currently expose a way to set default buttons.
Can someone write up a bug on this? I've never seen this before.
On Tue, Dec 2, 2014 at 3:23 PM, Tunney, Stephen
wrote:
> Bingo! That did it :) Thank you for the heads up Phill!!!
>
> -Original Message-
> From: Phill Hogland [mailto:phogl...@rimage.com]
> Sent: December-02-14 2:15 PM
It is fixed, though I believe Bob did 2013 and I did 2015.
On Tue, Dec 2, 2014 at 9:05 AM, Rob Mensching wrote:
> Bug. I *think* this was fixed recently by Sean.
>
> _
> Short replies here. Complete answers over there:
> http://www.fir
Thanks for the leads to the vb code - looks promising - and I do still have
the mst files to apply to the base msi using Orca - I was trying to figure
that out before - That helps a lot. I'm going to mess around with the VB
code for a bit.
--
View this message in context:
http://windows-insta
Some more info:
http://stackoverflow.com/questions/16770848/how-to-read-msttransform-table-along-with-msi
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Embedded-Transforms-for-L10n-and-how-to-display-them-tp7598340p7598372.html
Sent from the wix
Sounds like: http://wixtoolset.org/issues/4609/
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenry.com]
Sent: Wednesday, December 3, 201
It looks like you have the .mst files because you are then embedding
into the MSI file. So you can open the base MSI file with Orca and use
the Transforms menu to apply them, the changes being highlighted. Do
you maybe no longer have the mst files or something?
---
Phil Wilson
On Wed,
I'm seeing a weird error on three products that all use the WixStdBa to install
a single MSI.
Install goes fine.
However, attempts to Repair, Uninstall, or Upgrade result in:
"0x80070057 - the parameter is incorrect."
This has only cropped up in the past two days, and the bundle authoring has
This probably isn't going to be helpful because I'm not that well-versed with
using Group Policy. But when I tried it once, the program ended up on a
different screen that regular programs. I had to go to *Control Panel ->
Programs and Features -> Install a program from the network*.
I base this
Hi
I am trying to install a test COM+ using WiX com plus extension.
Installation fails with following error in the log
MSI (s) (BC:88) [21:50:36:164]: Invoking remote custom action. DLL:
C:\Windows\Installer\MSI326D.tmp, Entrypoint: ComPlusInstallExecuteCommit
Action 21:50:36: RegisterComPlusAsse
There are way more downsides, for example rollback support is way more complex.
Shelling to an executable is never* the right thing to do.
* for very large sets of "never"
_
Short replies here. Complete answers over there: http://www.
Thanks for the replies fellas. Phill is right on - that's the way I do it,
and because I inherited this project and am fearful of making big changes
and screwing it up ;-) it is still done this way. Someday I'll upgrade to
using Burn, too, and get off of the old Wix 3.5.
Now back to the original
I suspect that wxl files were used to batch build the msi resulting in n msi
packages for n cultures defined. I used to do what I think he is doing,
using torch(or similar) to create mst files of the difference between my
base msi (english msi) and each of the other cultures, named ":lcid.mst".
I would only suggest uninstalling WiX and reinstalling. For me, when I do
Ctrl + SPACE, I get a list of WiX elements. I clicked just underneath the
Package element in the Product.wxs file and did Ctrl + SPACE.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.n
I tried repairing the Wix install, but no luck. I have VS 2013 professional
edition.
Syntax highlighting is available. For Intellisense, nothing shows up in
listing the attributes for a given xml element. The only available options
listed are !--, ![CDATA[ , ?
Are there any manual hacks to get
You're overthinking it. You can set up your Directory elements for whatever
directory structure you need and wherever the user changes INSTALLFOLDER to
be, its child Directory elements will follow it there. For example, if the
user changes the path of INSTALLFOLDER to C:\MyStuff, they'll get:
C:/
To bind the certificate to the Web site, you can do something like:
That should go into the same Component as your Certificate elements. That
should be enough to do the binding.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Iis-Schema-Usag
WiX has a Group element in the Util Extension that can find an existing
Windows group, but can't create one of any kind. Its User element can create
a user, but I'm not sure if it works with AD. It has a Domain attribute, but
that may only be for referencing an existing AD account.
--
View this
You don't need to put an Id attribute on the Fragment, it won't be used.
The Id attributes of Directory elements are themselves, properties. You can
see the full path to your install directory be looking at the value of the
property called INSTALLDIR. You can see it in the MSI log:
msiexec /i myi
How come you're using mst files for localization and not .wxl files that are
built into WiX?
http://wixtoolset.org/documentation/manual/v3/howtos/ui_and_localization/make_installer_localizable.html
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/
Do you mean, create a file share?
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Create-network-folder-tp7598287p7598356.html
Sent from the wix-users mailing list archive at Nabble.com.
If you want to install only for the current user, you should install to the
LocalAppDataFolder instead of ProgramFilesFolder. ProgramFilesFolder
requires elevated privileges since it's a machine-level folder.
LocalAppDataFolder is for current-user-only installs (Package/@InstallScope
= perUser)
Try posting this on the wix-devs forum.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Latest-build-wix-3-10-visual-studio-2013-problem-tp7598342p7598353.html
Sent from the wix-users mailing list archive at Nabble.com.
---
Nope. Installing the WiX Toolset should get you all set up with VS 2013. No
other setup is required. I've tried it several times and it works for me.
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Intellisense-in-Visual-Studio-2013-for-Wix-3-8-tp7
Hi,
Sorry, this is very basic question.
How do I enable intellisense in visual studio 2013 with Wix 3.8? In
Visual Studio 2010 (for wix 3.5), ProjectAggregator msi would add
intellisense. Do I need to run any such tool for visual studio 2013?
Do I need to copy any xml schemas to C:\Prog
Classification: Public
Why are you wanting to run the same MSI twice?
-Original Message-
From: Dileep S [mailto:dileep.sanamp...@gmail.com]
Sent: December-03-14 9:20 AM
To: General discussion about the WiX toolset.
Subject: Re: [WiX-users] [WIX]: Getting error 1316, While running the MSI
Another options is invoking certutil.exe (on Vista and newer versions of
windows) with a CAQuietExec. Here's an example that installs to the system
store, just tweak the certutil.exe command to go to the user store if that is
where you want it.
The one downside to this is i
Sorry!
This problem is already solved.
The solution is a MsiProperty inside the MsiPackage with the name "
IACCEPTSQLLOCALDBLICENSETERMS" and the value "YES".
Bye!
Patrick
-Ursprüngliche Nachricht-
Von: patrickpirzer [mailto:patrick.pir...@prosoft.net]
Gesendet: Dienstag, 2. Dezember
The big question is: Why do You want to run Your MSI twice?
-Ursprüngliche Nachricht-
Von: Dileep S [mailto:dileep.sanamp...@gmail.com]
Gesendet: Mittwoch, 3. Dezember 2014 15:20
An: General discussion about the WiX toolset.
Betreff: Re: [WiX-users] [WIX]: Getting error 1316, While runni
Thank you for the information.
In that case, we can not run same MSI package (by changing the name)
without un-installing the previous package.
Please help me if there is any other way to solve this issue..
On Wed, Dec 3, 2014 at 6:50 PM, Patrick Pirzer
wrote:
> It depends upon the name of th
It depends upon the name of the product, which Yous et in Your MsiPackage.
It's not relevant, if Your MSI-file is named Sample.msi or 1.msi.
When You start 1.msi, it detects the product name in the registry shows You the
message, that actual installation already exists.
Bye,
Patrick
-Ursprü
Dear All,
I have created MSI package using WIX.
MSI pacakge name: Sample.MSI
I have installed this 'Sample.msi' package for the first time.
After i have renamed the 'Sample.msi' as '1.msi'.
While running the changed MSI, it shows an error: The specified account
already exists.
Please solve me h
I have updated to the latest 3.10 build and I have reported this problem to the
Visual Studio 2013, when I open the property page of a c++ project I have no
more the property grid where are the properties of the project. Uninstalling
wix 3.10 all Return working normally.
Inviata dal mio Windows
38 matches
Mail list logo
