Hi,
I’m trying to create a file share with the FileShare element. The setup
should create permissions to a user group. So I created a permission entry
with FileSharePermission element. Because the FileSharePermission element
only accepts a reference to the user element (and not group) I defined
1) This http://support.microsoft.com/kb/834549 ?
2) Heat thinks the .exe is a com server, as it is another installer you can
ignore it. If you are bundling several packages together you may want to look
at the burn bootstrapper which will handle this much better than embedding
the sub installers
If you want some more logic to the installation of pre-requisites, I think
you'll need to make another Burn Bundle to act as your pre-requisite.
That's what we had to go to get .net 4 and Windows Imaging Component to
install as a prerequisite on Server 2003. This will just be a super simple
I also would prefer to make a prerequisite bootstrapper without WPF UI to
install .net 4.5. If you install an update of .Net in a managed bootstrapper
you propably will ran into a system reboot, cause .Net assemlies are loaded
which might be replaced during .Net 4.5 Installation.
If you do not
If this is a major upgrade, you can add another custom action that reads the
value from this file and sets a property in the installer that your dialog can
use for displaying to the user. The new custom action would have a condition
that makes it run only during upgrade.
-Original
Hello everyone,
I'm a new to WIX and I'm a little lost.
I want to create a .msi file from my project (with lots of files and
folders), so I use HEAT.
Heat works as exepcted and a new file is created (SampleGroup.wxs).
Then I try to compile all : C:\Program Files\WiX Toolset
v3.7\bin\candle
The usual thing to do here is generate wix file with everything in
componentgroup , then include a componentgroupref in a feature in your main
wxs file.
You can use Orca or Insted to open an msi file to see if contains what you
want.
Dave
-Original Message-
From: BGINFO4X
Nothing is encrypted, so the link didn't help, though I did see that
'solution' before.
Per your request, I removed all the variables, simplified the problem to
one wxs file, packaging 2 text files, no variables, and I still get the
error system cannot open the device or file specified.
The
Are you not referencing SampleGroup.wxs?
Feature Id=ProductFeature Title=yourtitle Level=1
ComponentGroupRef Id=SampleGroup.wxs /
J
On Fri, May 17, 2013 at 8:55 AM, BGINFO4X bginf...@kztsoftware.com wrote:
Hello everyone,
I'm a new to WIX and I'm a little lost.
I want to create
Take a look at that folder and the file at
C:\cygwin\home\build\current\EUROPA\MyProgram.msi .
That looks like a user-created folder, and it seems that the install fails
as soon as it switches to the service to do the install. That file/folder
may not allow access by the SYSTEM account.
Phil
Which custom action do I use to read the value from the XML app config file?
Marty Offe
Sr. Software Developer
Harland Financial Solutions
Portland, OR
503-274-7280 x2376
www.harlandfinancialsolutions.com
-Original Message-
From: Sharon Pierson [mailto:sharon.pier...@netiq.com]
Sent:
Hello,
I see the problems:
The First one was that light needs all the *.wixobj
The Second one was that light needs the -b parameter.
Now, I do the following:
C:\Program Files\WiX Toolset v3.7\bin\heat dir BGINFO4XW -cg
SampleGroup -out SampleGroup.wxs -gg
C:\Program Files\WiX
I am using the setting on the ExitDialog to allow the user to launch the
application when setup is complete. I want to hide this option if a reboot
is going to be required. Are there any properties that survive the
transition of the InstallSequence back to the UISequence that I can use to
The problem you're running into is that the generated components are by
default generated under a directory under TARGETDIR, not INSTALLDIR. To
override this:
1) Add (for example) -dr foo to your heat commandline to generate them
under a directory of ID foo
2) In your main authoring file, you
Ah, so your building your MSI via command line. Good to hear you figured it
out.
J
On Fri, May 17, 2013 at 12:48 PM, BGINFO4X bginf...@kztsoftware.com wrote:
Hello,
I see the problems:
The First one was that light needs all the *.wixobj
The Second one was that light needs the -b
2013/5/17 Jeremiahf jeremi...@gmail.com:
Ah, so your building your MSI via command line. Good to hear you figured it
out.
Yes, I'm doing only a .msi package, not a visual project with c# or similar ...
Thanks.
--
1) Add (for example) -dr foo to your heat commandline to generate them
under a directory of ID foo
Done:
C:\Program Files\WiX Toolset v3.7\bin\heat dir BGINFO4XW -cg
SampleGroup -out SampleGroup.wxs -gg -dr basedir
2) In your main authoring file, you then need to define a directory of ID
I don't see any option to use a predefined wix element. I think you'll need to
write your own code for a custom action. There are lots of good sources
showing you steps for doing that. I'd start with the WIX tutorial, here:
Classification: Public
And / or take a look at this:
http://blogs.technet.com/b/alexshev/archive/2009/05/27/from-msi-to-wix-part-25-installable-items-updating-xml-files-using-xmlfile.aspx
-Original Message-
From: Sharon Pierson [mailto:sharon.pier...@netiq.com]
Sent: May-17-13 3:23 PM
Phil,
You are a genius! I dragged the MyProgram.msi to the desktop, double
clicked the msi, and it installed! Happy Day.
Permissions address issue 1.
So why are the permissions wrong, and how to I solve this?
From cygwin or cmd, built via ant or calling wix commands directly,
trying to
Hi,
Is there a way by which I can log (to the msi log) the stdout and strerr while
running my custom action that is written in C++? I am calling a process using
java.exe and I need to log the output to the msi log. Is this possible?
Thanks!
Uma Harano
Your problem is that basedir isn't a child of INSTALLDIR, it's a child
of ProgramFilesFolder. Here is your current code:
Directory Id='ProgramFilesFolder' Name='PFiles'
Directory Id='INSTALLDIR' Name='BGInfo4X for Windows
$(var.ProductVersion)'/Directory
Directory
I don't know the direct answer to your question, but taking a step back,
have you considered any alternatives instead of adding a custom action?
Custom actions are notoriously difficult to write correctly, and very, very
easy to get wrong. A custom action that invokes an external process (such
as
Hi,
I created following bootstrapper ,it install perfectly. now I am looking to
upgrade the msi installed by my boostrapper . if I give same upgrade and
greater version , it does n't update my msi instead create two entries in
control panel . please advise .
?xml version=1.0 encoding=UTF-8?
Wix
Here is the configuration I use in product.wxs
!--UPGRADE CONFIGURATION SECTION--
Upgrade Id=$(var.UpgradeCode)
UpgradeVersion Minimum=$(var.InstallerProductVersion)
OnlyDetect=no Property=NEWERVERSIONDETECTED/
!-- The next one will become useful if we apply conditional logic to
The service I have been asked to create can only be created by calling the java
process.
-Original Message-
From: Mike Carlson [mailto:corf...@gmail.com]
Sent: Friday, May 17, 2013 2:11 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] log stdout and
Found a workaround to permissions issues.
icalcs MyProgram.msli /grant Everyone:(F)
Not sure why it's an issue, but this gets around it.
On Fri, 2013-05-17 at 13:03 -0700, jo...@msli.com wrote:
Phil,
You are a genius! I dragged the MyProgram.msi to the desktop, double
clicked the msi,
Is this a Windows (NT) service? (ie net start servicename)
From: Uma Harano uhar...@esri.com
Sent: Friday, May 17, 2013 4:51 PM
To: General discussion for Windows Installer XML toolset.
wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] log stdout
You could also look at ReplacedInUseFiles:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa371219(v=vs.85).as
px
Phil
-Original Message-
From: John L Krupka [mailto:john.kru...@nmwco.com]
Sent: Friday, May 17, 2013 10:32 AM
To: wix-users@lists.sourceforge.net
Subject:
29 matches
Mail list logo
