Thank you
-Ursprüngliche Nachricht-
Von: Rob Mensching [mailto:r...@robmensching.com]
Gesendet: Mittwoch, 25. Mai 2011 10:54
An: General discussion for Windows Installer XML toolset.
Betreff: Re: [WiX-users] Turoial for Burn
WiX.chm has walk through for some basics.
On Wed, May 4, 2011
I did indeed retain the code. Since nothing has changed except the internals
of the two files, both heat-generated .wxs are identical.
I'm glad to hear that it looks OK since I was worried I had made some
obvious embaressing mistake... that said, it's quite unsettling that you
can't find any
That's a shame. We are currently struggling with a C#-based installation
product written in-house by another team so we've seen how trading for
short-term control yields long-term problems. Since we adopted Wix some years
ago, which admittedly has a big learning curve mostly due to the underlying
Hello,
I'd like to place a check in an install that confirms the version of the
application's database. This info is stored in a versions table.
The rationale is I'd only like install to go ahead once the database has been
updated, but I want to keep this process separate from the
Make a major upgrade of your existing MSI. There's a help topic in the Wix
help file called How To: Implement a Major Upgrade In Your Installer. Find
the Upgrade Code from the previous installer and set it in your new
installer. Make sure your new version number is higher than the old one. The
http://msdn.microsoft.com/en-us/library/aa370905(VS.85).aspx
AppDataFolder is for the current user.
CommonAppDataFolder is for all users.
-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
Sent: 14 June 2011 18:22
To: General discussion for Windows Installer XML
Hi Dave,
Thank you for this link.
I have been trying to implement it into my calls, but sadly it does not seem to
work.
I have tried the redirecting with a simple cmd call and it works fine.
However I am creating an automation process using autoit, and im not sure if I
would be using the
Hello,
I was wondering if it is possible to use XmlConfig in multiple merge modules,
that will later be used in a single installer.
For example, I have MergeModule1, which has:
Fragment
Component Id=appConfigEdit Guid={1F53A85E-07AD-47B5-890E-D6768A65E343}
Directory=MANAGEMENTTOOLFOLDER
Thanks Peter. As I've explained previously though each time I run the
installer the installation files are installed into one location, then
before the installer ends I need to have Network Service added to the
MachineKeys folder. After the installer completes and I navigate to the
following
As Pete says, you are using the wrong directory ID use CommonAppDataFolder in
place of AppDataFolder in your Directory.
-Original Message-
From: CoolBreeze [mailto:coolbreeze...@googlemail.com]
Sent: 15 June 2011 14:46
To: General discussion for Windows Installer XML toolset.
Subject:
I already made that change. I ran the installer with logging turned on and
saw where it executed my two CustomActions and the installation completed
fine. It's just that Network Service never gets added to the MachineKeys
folder nor are any permissions set in the folder.
MSI (s) (58:A4)
I'm just now migrating a wix project from wix 3.0 to wix 3.5. My 3.0 project
had a customization of InstallDirDlg.wxs to allow the user to decline
creation of a desktop icon. To add this customization required modification
of the InstallDirDlg.wxs file that was part of the wix 3.0 source. It seems
Hi David,
I am not expert in candle and light but I believe that redirection in DOS
should happen at the end of the line:
RunWait($WIX_FOLDER '\candle.exe -dmanufacturer='$MANUFACTURER_NAME'
-dproductName='$productName' -dcabName='$CABINET_NAME'.cab
-dcodepage='$wixInitLcidCode'
I'm looking at using the WiX toolkit to build an MSI from a Webpate. Our
current solution, which uses a script executed by the windows cscript
command, requires elevated permissions. On some systems, especially Windows
2008 R2, this causes some problems.
What I'm wondering is, will WiX be an
This is what I do
CreateFolder
Permission User=[SID_BUILTIN_USERS] GenericAll=yes /
/CreateFolder
Along with SIDLookup merge module so that the all the well know SIDs
language natural
--
Figured this out. It was as simple as reducing the length an XmlConfig Id
('ConnectorServiceRelativePathDefinition') which was too long to handle
-Original Message-
From: Stelios Kyprou [mailto:stelios.kyp...@formicary.net]
Sent: 15 June 2011 12:35
To: General discussion for Windows
The following works, I just tried it.
Directory Id=CommonAppDataFolder
Directory Id=Microsoft Name=Microsoft
Directory Id=Crypto Name=Crypto
Directory Id=RSA Name=RSA
Directory Id=MachineKeys Name=MachineKeys
Component
On Wed, 15 Jun 2011 07:54:43 -0700
Nuno Romao nro...@gmail.com wrote:
I'm just now migrating a wix project from wix 3.0 to wix 3.5. My 3.0
project had a customization of InstallDirDlg.wxs to allow the user to
decline creation of a desktop icon. To add this customization
required modification
True this does create the folder at the root of C:\ and adds the Network
Service user with the proper permissions. What I'm am trying to do though is
add the Network Service user with the permissions specified to the
EXISTING MachineKeys folder located at:
C:\Documents and Settings\All
I think somebody a while back reported an undocumented error 2623 during an
install. I just came across this error if anyone is still interested. It
turned out to be:
DEBUG: Error 2623: Calling ScheduleReboot from a multi-package transaction is
not supported.
This restriction is documented
Hi,
I plan to use a managed bootstrapper application that instantiates a WPF UI to
use with Burn chainer. I'd like to block users and provide a custom error
message if they don't have .Net 4.0 installed. I have two questions on this -
1. Given that my bootstrapper itself depends on .Net
21 matches
Mail list logo
