you can create a dll with your C# code and make your required functions
available in dll.
this dll cane be registered as binary in WIX code base and it's exposed
function can be run as custom actions during installation.
- Original Message -
From: "Rob L"
To: wix-users@lists.sourceforg
On 10-Oct-14 18:01, Phill Hogland wrote:
> I have a chain of Burn driven MSIs. I implemented a MSILOGGINGVALUE property
> (and related variable which Burn initializes and the mba overrides). If the
> MSILOGGINGVALUE property is provided to the package I do a conditional
> SetProperty action on Ms
On 10-Oct-14 18:06, sceiler wrote:
> To my understanding this shouldnt happen with the use of wix binaries
> checked in to TFS.
You must install WiX to be able to build inside Visual Studio. You can
build outside Visual Studio (e.g., command line or Team Build) using the
checked-in WiX binaries.
On 09-Oct-14 19:15, Phill Hogland wrote:
> I see that I still have the -ext WixUtilExtension on the above candle
> command. I removed it but Light still fails saying that 'User' Table is
> not defined. I can't find anything else in my project related to the User
> table. When I first started th
I have a burn setup with custom WPF UI, the localization for this part is made
with custom localization using c#.I added the standard wix page for installing
Net Framework as prerequisites using the standard localization that use
#loc.STRINGNAME, but the dialog is displayed always in Italy, my c
It appears that MsiLogging needs to be either set in the Property table or
indirectly on the command line. It does not appear to support conditional
initialization:
The MsiLogging property sets the default logging mode for the Windows
Installer package. If this
optional propert
Is the WIX environment variable set appropriately, the path to the WIX toolset
is in the PATH environment variable, or are absolute paths used to each toolset
call?
You're going to also have to make sure that the .targets files can be resolved.
Once that is done, it will work fine. It will not
Hello,
I included wix binaries to my TFS and everything works fine for me (I have
got Wix installed) but other members of my team cant build an installer
because VS2013 prompt an error that .wixproj cannot be loaded and show an
migration report. This is expected because they dont have wix installe
I have a chain of Burn driven MSIs. I implemented a MSILOGGINGVALUE property
(and related variable which Burn initializes and the mba overrides). If the
MSILOGGINGVALUE property is provided to the package I do a conditional
SetProperty action on MsiLogging, scheduled after LaunchConditions. But
Classification: Public
Found a few answers...
The WiX Toolset integrates with Visual Studio as an extension. The Express
versions of Visual Studio do not allow extension nor addins. So, WiX will not
integrate with Express versions.
WiX does work with the free, open source SharpDevelop IDE
(htt
Classification: Public
I haven't used this, but try Wix Designer for Visual Studio Express:
http://www.add-in-express.com/wix-designer/index.php
or
https://social.msdn.microsoft.com/Forums/vstudio/en-US/5d18f6ae-fc3a-4e4b-a7f9-9bd763d4d75c/using-wix-with-vs-2013-express?forum=vssetup
Steve
Hi
Im just starting to learn about wix. I want to create an installer that copies
a couple files and then it runs some external c# code as well. I have visual
studio express 2010 and it does not support add ins. So, i dont have access to
using wix on visual studio and have to use it in msbuild.
Are the shortcuts advertised or not? The behavior of CreateShortCuts
is different in the advertised/non-advertised cases. If the shortcut
is advertised it's basically a pointer to the keypath of the
component, and that will result in a call to MsiProvideComponent () if
it's used. It's not advertis
Yes that is basically what InstallShield is doing and again the only reason
that we are still supporting this is that we still have administrators that
push out our software by .msi only and therefore we had to support a multi
.msi package so that they only had to push out a single .msi file instea
Concur 100%. The unified experience is also much better, particularly if your
product uses multiple MSI's.
--
jmc
-Original Message-
From: Hoover, Jacob [mailto:jacob.hoo...@greenheck.com]
Sent: Friday, October 10, 2014 2:28 PM
To: General discussion about the WiX toolset.
Subject: Re:
What I mean to say is I gave up on the Windows Installer UI long ago. It does
ok at very basic functionality. If you start trying to do anything remotely
complex you'll spend 3 x the time trying to get Windows Installer to do it than
you would if you just joined the "cool kids" club and wrote a
Ahh, that makes sense. Yes, if you use the "JoinTransaction" functionality of
the Windows Installer you'll get exactly that behavior.
Burn doesn't use that transaction functionality because we found enough bugs
that we bailed on it. No Microsoft products (that I'm aware of) use the feature
whic
An InstallShield chain of MSIs is the "single transaction" install,
the multi-package transaction where the whole transaction of multiple
MSIs isn't committed until the end. That seems to include committing
assemblies into the GAC, that's not MsiPublishAssemblies as much as
the Fusion API not doin
Should run.
Have a good weekend
Blaine Wheeler
Department of Social and Health Services
DCS IT Operations
360.664.5416
blaine.whee...@dshs.wa.gov
--
Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer
Achiev
I don't know if this comment relates to your concern, but, after some
experimentation, I have interpreted the last paragraph in Remarks, at the
following link to indicate that my Icon/@Id should be formated with an
extension which is the same as the file which the shortcut targets. So even
though
Hi John,
Thanks for your suggestions Jacob and John
You mean to say we need to validate everything through custom action after
clicking the Next button.
It will not work with the WIX inbuilt condition.
Regards
Balakrishnan.S
-Original Message-
From: John Cooper [mailto:jocoo...@jackhenr
I'm curious. What is a "suite admin installer .msi"? An MSI that installs a
bunch of MSIs? Is this using EmbeddedUI? Maybe I'm just confused.
I also couldn't parse this: " Since Wix does not support an admin chain install
that creates a output .msi we are using InstallShield to create our chain
No we are not doing nested installs. Since Wix does not support an admin
chain install that creates a output .msi we are using InstallShield to
create our chain installs to chain all out wix install projects.
We have quite a few wixlib 32 bit assemblies that we create to that gets
installed and ar
Today wixstdba displays the error message that Windows has associated with the
error code.
_
Short replies here. Complete answers over there: http://www.firegiant.com/
-Original Message-
From: DP [mailto:dpg_...@yahoo.com]
S
You're not trying to do nested installs are you? What are you putting in the
GAC and why are you putting it there?
As for the icons, I've always tried to use a resource only native DLL.
-Original Message-
From: TimM [mailto:timmay...@smarttech.com]
Sent: Friday, October 10, 201
The problem is inherent in Windows Installer Service Controls: they don't
expose focus change events. As Jacob says, to get full WPF control, you need
to write your own custom bootstrapper. The Windows Installer Service controls
just won't give you that degree of control.
It's not WiX specif
I believe the answer is the Windows Installer UI has limitations and the
recommendation would be to use a BA, and pass in the values to your MSI via
properties. This allows you to have full control over your UI and serves for a
unified installation experience (when you have prerequisites).
---
Coming back to this one just to see if there may be another reason for this
issue. Again it does not prevent out apps from running at the end of the
install, it is just an issue of seeing sxs errors in the Event Viewer.
I checked the app .exe manifest files and yes all the assemblies that are
decl
Hi
I have a dialog which has two edit boxes. One for username(USERNAME) and the
other for the password(PASSWORD). I am doing a small validation like "Next"
button will be disabled until the user types something in the username
password edit text box and my wix code snippet is written below:-
Wix
That looks better, but "removeFile is not always ok" isn't sufficient
to diagnose what's happening. Take a verbose log of the uninstall and
see what's happening around the place where the remove is happening.
msiexec /x /l*vx
should get you an uninstall log.
---
Phil Wilson
On Fri
I think the point Michael is making is that during the install you are
copying a file to APPLICATIONFOLDER as part of the "normal" MSI
install process, and then you're doing a separate copyfile of that
same file to the same location with the same name. This can't be
right, so maybe you've just made
The issue is not about the MSI's MajorUpgrade. This issue is about not able
to customize error message in Wix standard bootstrapper application during
downgrade case. No doubt, my MSI has MajorUpgrade element with proper
downgrade error message. This message is never shown (note that my MSI is
call
1. That's the same thing WixStdBA and the WixBA is doing.
2. That should all be transparent, you just need to plan the repair.
-Original Message-
From: robert_ort...@agilent.com [mailto:robert_ort...@agilent.com]
Sent: Thursday, October 09, 2014 4:45 PM
To: wix-users@lists.sourceforge.ne
Many moons ago we stopped adding a 'launch the installed app' check box
to our final dialog as we had intermittent issues with the launched app
window appearing behind other windows as per this WiX mailing list issue
from 2005:
http://sourceforge.net/p/wix/mailman/message/11428915/
We didn't imp
Add an Assembly=".net" to each relevant File element. This will add/remove
assemblies from the GAC, so make sure that's what you want.
--
John Merryweather Cooper
Senior Software Engineer | Enterprise Service Applications | Continuing
Development
Jack Henry & Associates, Inc.® | Lenexa, KS 662
IIRC that is the message which you define in the
MajorUpgrade/@DowngradeErrorMessage in the msi package.
There are other options to MajorUpgrade which do not display a message if
you do not want a down version to fail.
--
View this message in context:
http://windows-installer-xml-wix-toolset
Hi Rob, thanks for the replay, its much appreciated.
I found the issue, it was ignorant me who set the DefaulVersion on the files
that caused the MsiFileHash table not to populate :)
I Just have one question, how do I get the MsiAssembly and MsiAssemblyName
table to populate?
Thanks in adva
Hi,
For information, my WSX File is generated by the build of my JavaFX application.
I just have then to customize this WSX file : what was made.
"I thought WiX reported an error for that, maybe it's not fatal"
For me, I have no error reported by WIX and I confirm that the cleanup is
correctly
Hi,
For information, I use WiX 3.8.
"...copying a file that you're already installing, but I've never found a
good reason to use it in this way"
Yes I've a good reason : I want install certain files to the root of the
application folder for particular functional use-cases
and one of the ways t
39 matches
Mail list logo
