On 17-Feb-11 05:15, Lukas Haase wrote:
> And what is the option in my case?
> I.e. when there are already deployed per-machine packages and I want to
> change to per-user?
MSI doesn't support upgrades in that case. You might be able to use a
bootstrapper.
--
sig://boB
http://joyofsetup.com/
--
On 16-Feb-11 21:34, John Robbins wrote:
> Good to know my beloved PDF files are there for 3.6. Good job! Sadly, we are
> using 3.5 for this project. :(
Yeah, this was only in v3.6, as of late December.
--
sig://boB
http://joyofsetup.com/
---
On 16-Feb-11 17:13, Lukas Haase wrote:
> However, what happens when program with same UpgradeCode is first
> installed globally as administrator and the next version installed as
> non-admin user?
MSI doesn't support a per-machine package upgrading a per-user package,
or vice-versa. It's best to
On 16-Feb-11 19:15, John Robbins wrote:
> Also, I'm going to file a bug report for WiX 3.6 that they start adding the
> PDB files for the CAs to the distributions. If I had those, I'd break in and
> be able to debug the CA myself.
You misspelled "feature request." Alas, it's already implemented,
On 16-Feb-11 13:35, Gregg Swanson wrote:
> How do I use the "InstallCondition" on a MsiPackage?
Burn expressions support the same syntax as MSI, so you'd use
FOO = "ALL"
--
sig://boB
http://joyofsetup.com/
--
The ulti
On 14-Feb-11 14:06, John Thornborrow wrote:
> I've just updated my installation to 3.6.1321.0, and when reloading existing
> wix projects, I am prompted with "Access to the path 'C:\Program Files
> (x86)\MSBuild\Microsoft\Wix\v3.x\wix200x.targets' is denied." Error. Upon
> checking, this is beca
On 13-Feb-11 14:25, ERWLive wrote:
> The output window is included below. -ext looks properly set.
It works for me on Visual Studio 2010:
http://schemas.microsoft.com/wix/2006/wi";
xmlns:util="http://schemas.microsoft.com/wix/UtilExtension";>
On 13-Feb-11 10:55, Rob Mensching wrote:
> I *think* Bob fixed this in a recent build.
That was just a schema fix.
--
sig://boB
http://joyofsetup.com/
--
The ultimate all-in-one performance toolkit: Intel(R) Parallel S
On 08-Feb-11 13:23, Mike Edenfield wrote:
> Since I am referencing the MsiDigitalCertificate record in
> MsiPackageCertificate, I shouldn't be getting this warning. I'm
> assuming that the ICE validation routines run by WiX aren't updated for
> Windows Installer 4.5; is there a way to get them upd
On 07-Feb-11 09:44, maksim.vazhe...@emc.com wrote:
> Robocopy to a temp directory is not a very good solution for it... There can
> be problems, if many people will build package at one time on a build server,
> there can be not enough space in %temp% directory.
Use hard links. They take up no s
On 13-Feb-11 01:29, ERWLive wrote:
> Error4The Component element contains an unhandled extension element
> 'util:RemoveFolderEx'. Please ensure that the extension for elements in the
> 'http://schemas.microsoft.com/wix/WixUtilExtension' namespace has been
> provided.
That almost always
On 02-Feb-11 08:43, Tobias S wrote:
> Just did some dialog modifying. When combining WiXUI_FeatureTree.wxs +
> WiXUI_InstallDir.wxs I mentioned the property WixUI_Mode which is set
> accordingly to the name of the dialog theme. Has this property
>
> some special function except for UIDecompiler
On 31-Jan-11 14:23, Chad Petersen wrote:
> Thanks for your help. Turns out the customer did not have IE or any
> other browser installed on this particular computer. Hadn't run into
> that before.
Heh, funny. Can you enter a feature request to add a ContinueOnError
attribute, like exists for some
On 27-Jan-11 03:44, Rune Moberg wrote:
> "Error 1001. An exception occurred while uninstalling. This exception
> will be ignored and the uninstall will continue. However, the
> application might not be fully uninstalled after the uninstall is
> complete. --> The specified service does not exist as
On 31-Jan-11 08:49, Poulopoulos, Vassilis wrote:
> If I create a trivial installer and specify ALLUSERS 1 then the
> Add/Remove Programs window does not show a 'Remove' (or any other)
> button if I'm logged as a non-admin user. Other installed applications
> however do, and clicking on the their re
On 01-Feb-11 20:11, Hoyt, David wrote:
> I'm chaining several MSIs and believe it or not, I want to show the UIs of
> each package. Is there a way to turn that on/off per package (and
> subsequently remove the default burn UI's install location?)?
Not today.
--
sig://boB
http://joyofsetup.com/
On 30-Nov-10 02:43, Neil Sleightholm wrote:
> The problem with this is that there isn't a reference to any of the
> components in the main install so none of the components are included in
> the msi.
Component/@Feature doesn't change the requirement that references flow
from the entry section to
On 30-Nov-10 02:17, Neil Sleightholm wrote:
> If you run the install on a clean machine then the welcome page is
> displayed during the initial page and then it jumps straight to the
> licence page.
That's not the welcome page; it just looks like it.
https://sourceforge.net/tracker/?func=detail&a
On 29-Nov-10 12:04, Neil Sleightholm wrote:
> I'd have to agree that this change in functionality should be optional.
> As it stands upgrading to 3.5 has changed the way it worked and I now
What change? WiX has used the WixUI_Advanced set (which combines the
welcome and license pages on clean ins
On 26-Nov-10 06:31, Rob Hamflett wrote:
> Slight typo. This was meant to say "It would be nice to know what I can
> expect to happen if costing
> *hasn't* completed yet"
AFAICT, costing completed; only the property wasn't updated.
--
sig://boB
http://joyofsetup.com/
-
On 27-Sep-10 12:55, John Fry wrote:
> The value that gets inserted into the MSI when we get the error is:
>
> [%CommonProgramFiles]\path\to\folder;[%CommonProgramFiles(x86)]\path\to\folder;[~]
Which is correct -- it looks like MSI doesn't like the parentheses.
> And you're saying that an equiva
On 27-Sep-10 08:17, Naufal Basheer (Aditi) wrote:
> We have an installer for which we are using both built-in Wix and custom
> dialogs. Is there a way to use the existing WixUIExtension.dll resource file
> for build-in resource strings and use a separate resource file for our custom
> strings?
On 28-Sep-10 01:26, akshi_gupta wrote:
> I can use .wxl file to localize the text for each dialog. But is it possible
> to customize the width or height of a dialog (or one of its control)
> differently for each locale?
Yes, the X, Y, Width, and Height attributes can be set to localization
stri
On 27-Sep-10 16:43, gapearce wrote:
> I have a reason to have a checkbox appear on a different place in the same
> dialog, based on a condition. I was trying to use propertyRef to allow both
> checkbox controls to use the same property, but I can't get that to work.
That's what CheckBoxProperty
On 26-Sep-10 17:28, Bruce Cran wrote:
> I had hoped that would work, but it doesn't seem to. The combination of
> InstallPrivileges="elevated" and InstallScope="perUser" doesn't result
> in any elevation prompt (and the "Install" button in the MSI doesn't
> have a UAC shield).
InstallScope doesn
On 23-Sep-10 10:31, Mark Simonetti wrote:
> It doesn't seem to be working for some reason, whether the initial
> install has them turned off or on, I never seem to be able to change
> it.
Transitive component conditions are re-evaluated only during a
reinstall; a change operation doesn't trigge
On 24-Sep-10 19:36, John Fry wrote:
> as it gives: error LGHT0204 : ICE03: Invalid format string; Table:
> Environment, Column: Value, Key(s): OURPROD_TGT_PATH.GUID_HERE
What value ends up in the .msi?
You can fix the problem using built-in MSI properties, like
CommonFilesFolder.
--
sig://bo
On 24-Sep-10 08:02, Sean Farrow wrote:
> I am in the process of writing a custom action to run an executable, can I
> concatenate a property name with a string literal of my executable?
FOO[BAR]BAZ[#asdf.exe]
--
sig://boB
http://joyofsetup.com/
--
On 24-Sep-10 15:55, Bruce Cran wrote:
> which is written using WiX 3.5 but I just get a permission denied error
> if I try and do a perUser installation which installs to
> ProgramFilesFolder - as I know I should do! As far as I know I can't
You need to set Package/@InstallPrivileges to elevate
On 26-Sep-10 12:41, Sean Farrow wrote:
> I only want to create one install, as this is the one file that differs.
MSI doesn't support 64-bit components in a 32-bit package. You need two
packages.
--
sig://boB
http://joyofsetup.com/
On 26-Sep-10 10:07, Sean Farrow wrote:
> How do I go about solving this ,do I need to rename my dialog set?
Yes.
--
sig://boB
http://joyofsetup.com/
--
Start uncovering the many advantages of virtual appliances
and s
On 25-Sep-10 07:41, fiordean dacian wrote:
> Now back to my problem, can you see any problem in the log I posted below or
> is the fact that I'm using a UI and schedule MigrateFeatureStates which
> creates me problems?
The MigrateFeatureStates SDK doc describes its limitations, including:
The
On 23-Sep-10 05:31, Pally Sandher wrote:
> In my defence Bob I wrote my patching code when I was using WiX 2.0 thus
> the only method available to me was the PatchWiz method. When I moved
> over to using WiX 3.0 I looked at the Pyro method as the idea of using
> purely WiX appealed but as time is
On 24-Sep-10 03:48, David Amey wrote:
> Thankyou for this, but it's not quite the solution I need. I need the
> option of the language selection, as the client needs different
> languages on different machines.
MSI doesn't support multi-lingual UI.
--
sig://boB
http://joyofsetup.com/
---
On 26-Sep-10 13:39, Sean Farrow wrote:
> I need to use the RegistrySearch element in a property. I need to look a key
> who's default key has no default value (regedit show "value not set"). What
> will the property be set to?
Nothing. See the RegLocator doc.
--
sig://boB
http://joyofsetup.c
On 22-Sep-10 13:07, Matt Walker wrote:
> I don't know if I mentioned this before, but my Deferred Custom Action
> fires an .exe stored in the Binary Table with the following command line
> parameters being passed [ProductCode] [OURVERSION], the later being the
> pre-populated property.
The reaso
On 20-Sep-10 13:09, Sean Farrow wrote:
> Is it possible within the current user interface of wix to have a
> listbox/listview with checkboxes in?
MSI doesn't support that.
--
sig://boB
http://joyofsetup.com/
--
Star
On 22-Sep-10 12:13, pcristini wrote:
> And I don't want the Plugin.Users.wxs file to have any reference to the
> Plugin.UserSync.wxs
The most likely cause is that the fragment containing the child feature
isn't getting linked in. WiX follows references from the entry section
(Product) to its c
On 22-Sep-10 20:15, Dario Amiri wrote:
> So it looks like no one has any advice for this issue. Is there any way
> I can submit this as a bug?
The WiX home page has links to the bug database: https://wix.codeplex.com/
--
sig://boB
http://joyofsetup.com/
--
On 22-Sep-10 18:11, David Amey wrote:
> Basically I'm using heat to harvest a folder, simples. However I'm using the
> "-var" property in the command line (to replace the "sourceDir" in the output
> component's source attribute), using a variable declared in the main.wxs.
> This replaces the "
On 20-Sep-10 06:44, Pally Sandher wrote:
> IIRC I had similar issues when attempting to create patches using the
> Pyro method in WiX 3.0 hence I've stuck with the PatchWiz method. I'm
> sure if I stuck at it I could probably work out what's going wrong when
> I try using the Pyro method but sinc
On 17-Sep-10 14:17, Oleksandr Y. Nechyporenko wrote:
> I've assumed that it is a good idea to group files which used for same
> function into one component.
Not if you want to patch them independently.
> Anyway it seems to be a problem with pyro.exe when RegistryValue is used as
> keypath.
You
On 18-Sep-10 07:03, GB wrote:
> when I try to set a specific user for a WebAppPool using Identity=other"
> and User="MyUser" I get an error stating that User must be specified if
> Identiy="other" is used. But that's exactly what I did! Could anyone
> shed some light on this?
https://sourceforge
On 17-Sep-10 03:23, Renegade Angel wrote:
> kind of upgrade problems could I run into exactly ?
IDs must be stable.
--
sig://boB
http://joyofsetup.com/
--
Start uncovering the many advantages of virtual appliances
an
On 16-Sep-10 09:58, Nick Ramirez wrote:
> 2. Use the CustomAction element with Id, Directory and Value attributes to
> set the path of the directory during the Execute sequence
Or SetDirectory.
--
sig://boB
http://joyofsetup.com/
--
On 16-Sep-10 14:00, Michael_A wrote:
> What is " set the property to the associated value" mean, if its
> SQLINSTANCENAME initially I have no idea what the values are.
Selecting an item in a combo box sets the combo box's property to the
value of the item (separate from the text). The revert i
On 16-Sep-10 09:08, Oleksandr Y. Nechyporenko wrote:
> Since RegistryValue allowed as KeyPath, there should be way to notify that
> KeyPath file was changed, but I can't understand how to do it.
It's allowed but that doesn't mean it's a good choice. If you want to
create patches, use one file p
On 15-Sep-10 14:58, jhennessey wrote:
> It seems that lit.exe includes all project references in the resulting
> library(?) I don't think it should be this way though.
It's valid to create a library from the contents of another library. I'm
not sure how we'd support both, but feel free to file
On 14-Sep-10 18:46, Wix User wrote:
> The DLL and the manifest files are located under system32\. I
> notice that 32-bit MsiExec.exe and Lodctr.exe are invoked to register the
> performance counters. These processes are not able to see the files under
> the system32 folder. So the installat
On 13-Sep-10 16:49, John L Krupka wrote:
> error CNDL0038: The iis:WebAppPool/@User attribute's value, 'AdminUserReg',
> cannot be specified without attribute Identity present with value 'other'.
Please file a bug. Looks like a simple bit check error.
--
sig://boB
http://joyofsetup.com/
On 14-Sep-10 14:51, pcristini wrote:
> I'm trying to use the variable in the main Product.wxs file and a couple
> other referencing wxs files like this:
>
>
> Any ideas why this value would not be working?
Your code didn't come through.
--
sig://boB
http://joyofsetup.com/
On 13-Sep-10 09:35, Ken Powers wrote:
> C:\delivery\Dev\wix36_public\src\ext\UIExtension\wixlib\ResumeDlg.wxs(18,0):
> error LGHT0197: The Windows Installer XML variable
> !(wix.WixUICostingPopupOptOut) is unknown. Please ensure the variable
> is declared on the command line for light.exe, via a
On 14-Sep-10 09:21, Renegade Angel wrote:
> -> If key exists in hashtable generate a new key (actually I just append _1,
> _2, ... if necessary) and change it in setup.wixobj
You've almost guaranteed you can't patch and will run into upgrade
problems. Can you open a bug on the underlying probl
On 10-Sep-10 22:30, TedG wrote:
> Is there something I'm missing on the maintenance mode? Is it really not
> designed to do this kind of manipulation?
No. "Change" is used to add or remove features and components; it
doesn't reinstall existing components, so nothing happens with them. For
tha
On 10-Sep-10 23:24, tltabor lists wrote:
> Does it work with Visual Studio 2010?
http://robmensching.com/blog/posts/2010/4/28/Change-of-plans-for-WiX-v3.5
--
sig://boB
http://joyofsetup.com/
--
Start uncovering the m
On 06-Sep-10 03:40, Grigory Petrov wrote:
> I have checked "single package authoring" and it seems that for Windows
> Vista it's not possible to create an MSI installer with WixUI_Advanced so
> the "install just for you"radio button on 'advanced' tab work. Am i correct?
No, it's possible to crea
On 11-Sep-10 06:18, Fabio Di Lorenzo wrote:
> WiX seems to use "FormattedSddl" as category for this column in the
> validation table.
>
> But thats wrong, the correct one should be "FormattedSDDLText".
Please enter a bug.
--
sig://boB
http://joyofsetup.com/
--
On 02-Sep-10 17:12, Dave DaveLists wrote:
> Thanks for the thought. I checked this out when I started having
> trouble, actually, along with removing the reference and putting it
> back in manually. But it is indeed present on the command line.
Never seen that. It might be a problem with upgradi
On 05-Sep-10 04:36, Tenzen wrote:
> C:\delivery\Dev\wix35_public\src\ext\ComPlusExtension\wixlib\ComPlusExtension.wxs(44,0):
> error LGHT0102: The localization variable !(loc.ComPlusInstallExecute) is
> unknown. Please ensure the variable is defined.
Provide a .wxl file with those strings defin
On 03-Sep-10 04:54, Grigory Petrov wrote:
> 64-bit. The installer GUI for "Install just for you" says thet "you do not
> need local administrator privileges'. But it is not true - local
> administrator priviliges are required. What i'm doing wrong?
See "Single Package Authoring" in the MSI SDK f
On 02-Sep-10 22:29, Gao SuoLi wrote:
> After press Finish pushbutton, one executable app is triggered in one
> CustomAction.
>
> Because the app writes some values to registry, it demands administrator
> privilege.
>
> In fact, the UAC promote dialog is not shown, the app is failed to run.
MSI
On 03-Sep-10 01:59, Andres Juarez wrote:
> Ok, so if I use "*" as component GUIDs, this means that small updates are out
> of the questions for this approach, right?
No. "*" component guids are stable, not randomly generated.
> If a 32-bit component is contained in both a 32-bit installation
On 30-Aug-10 01:36, Andres Juarez wrote:
> So, running candle with teh -arch switch does take care of marking the
> components at 64 bits, but if using the same Wix source file for the
> 32 and 64 bits installer with the only difference of the candle -arh
> switch, the Components GUIDS for the
On 27-Aug-10 13:53, Dave DaveLists wrote:
> Yes, we're referencing the DLL in the project.
Take a look at a verbose MSBuild log to see what -ext switches are being
passed to Candle.exe. My bet is that the reference isn't turning into an
-ext switch.
--
sig://boB
http://joyofsetup.com/
On 30-Aug-10 12:41, alexander.nevs...@acronis.com wrote:
> Of course, there is no custom action "[CustomSerialValidateProp]". But
> property CustomSerialValidateProp contains actual custom action.
As in VBScript or JScript? It looks like that's not supported. Feel free
to file a bug -- and get
On 02-Sep-10 06:10, Satyaprakash J wrote:
> I would like to know from where I can download the source
> code for Wix 3.0 . The links on the web seem to be broken.
Which links?
--
sig://boB
http://joyofsetup.com/
-
On 01-Sep-10 03:38, Valentijn Makkenze wrote:
> I'm using Wix 3.5.2020 and the WixIIsExtension and WixUtilExtension
No, nobody's contributed localizations for nl-NL for those extensions.
--
sig://boB
http://joyofsetup.com/
-
On 28-Aug-10 14:40, Rafael Campana wrote:
> 1
Properties must be marked Secure="yes" to be used from both UI and
execute sequences.
--
sig://boB
http://joyofsetup.com/
--
This SF.net Dev2Dev email is sponsored by:
On 30-Aug-10 10:12, Christopher Hughes wrote:
> I've looked at the log file (using /lv) but can't quite see which dlg the
> error originates from. I looked up WixUIValidatePath you mentioned and tried
> adding the following property to supprress it, but to no avail:
>
>
Then it's not WiX thro
On 02-Sep-10 06:13, Pally Sandher wrote:
> I have personally fixed things like that myself. Last year one of our dev's
> decided to implement the use of CAPICOM for some basic password encryption&
> MD5 checking& thought it was OK to tell me "just self-register the CAPICOM
> DLL in the insta
On 31-Aug-10 13:41, Maillet, Ed wrote:
> The Preprocessor.GetSourceLineNumbers doesn't work because the preprocessor
> extension doesn't get the XmlNode. (Or it's hiding somewhere I haven't seen).
Please enter a bug to have it exposed.
--
sig://boB
http://joyofsetup.com/
---
On 02-Sep-10 06:03, maksim.vazhe...@emc.com wrote:
> I have the following question: why there is no version of wcautil
> library for ia64 platform in wix SDK?
Probably because nobody noticed or complained: IA64 isn't exactly a
popular platform nor is it gaining in popularity. Feel free to enter
On 25-Aug-10 09:37, Ross Inglis wrote:
> I've tried installing the 'final' WIX 3.0 build, but the errors remain.
> I'm thinking this looks like it
> 'might' be an installer SDK issue, but as far as I know, the installer
> SDK comes in with the Visual
> Studio 2008 (SP1) I'm using for this build (
On 24-Aug-10 12:16, Chunlin Liu wrote:
> Without requiring Installer 4.5 or higher, is there any other way to support
> it?
See Pally's reply. I doubt the MSI team would have added it had there
been an easy workaround.
--
sig://boB
http://joyofsetup.com/
---
On 24-Aug-10 21:00, Dave DaveLists wrote:
> we expected to be able to reference XmlFile using util:XmlFile but
> this is failing at compile time.
It might help if you described how it was failing...
--
sig://boB
http://joyofsetup.com/
-
On 24-Aug-10 17:45, bdwain wrote:
> the case on the upgrade too. But when upgrading, I want the box to be
> checked by default if the user has the shortcut there already, and unchecked
> otherwise. I've been having trouble getting that to work. I've tried making
> the shortcuts in components in t
On 24-Aug-10 14:50, ldy...@vorum.com wrote:
> I now wish to run the just-installed application from the installation (at the
> end), but, owing to the above, the EXE is not available till it's been
> launched
> from the shortcut!
As long as it's installed to a per-machine path, it's available t
On 24-Aug-10 11:43, Alexander Kozlenko wrote:
> Is it possible to use MsiLaunchApp in my case?
MsiLaunchApp is a control event so it's used only in the UI.
--
sig://boB
http://joyofsetup.com/
--
Sell apps to millions
On 23-Aug-10 06:11, David Watson wrote:
> I tried using to set this at link time but the @Win64 will
> not accept them unfortunately, just 'yes' or 'no'.
Yes, that's by design. Like I said, the linker doesn't generally change
the data it's linking and the Win64 attribute changes the data in th
On 24-Aug-10 07:26, Alexander Kozlenko wrote:
> Hello. I didn't find an answer so will ask in this mailing list. Anybody can
> explain how can I migrate from WinShellExec custom action to MsiLaunchApp in
> WiX 3.5? Thanks.
It depends on how you use WixShellExec. Note that MsiLaunchApp is
support
On 23-Aug-10 16:57, Wheeler, Blaine (DSHS/DCS) wrote:
> C:\delivery\Dev\wix35_public\src\ext\UIExtension\wixlib\ResumeDlg.wxs(18
> ) : error LGHT0197 : The Windows Installer XML variable
> !(wix.WixUICostingPopupOptOut) is unknown. Please ensure the variable
> is declared on the command line for
On 19-Aug-10 19:07, Kyle McClellan wrote:
> Is there a way to say 'Remove the entire directory tree on uninstall'?
RemoveFolder
--
sig://boB
http://joyofsetup.com/
--
This SF.net email is sponsored by
Make an app t
On 20-Aug-10 13:47, Chunlin Liu wrote:
> either A_sp1.msp or B_sp1.msp, those shared files rolled back to previous
> version. My questions is: Is there a way to make those updated shared files
> not roll back to previous version if any of A_sp1.msp or B_sp1.msp is not
> uninstalled?
See the M
On 19-Aug-10 12:48, David Watson wrote:
> Do I need to do the obvious and make x64 wixlibs as well as x86 even
> though the files are identical or is there some setting that I am
> missing that will allow the components bitness to be flagged at link
> time. I should also point out that I currentl
On 19-Aug-10 07:26, Nicolas Laurent wrote:
> I create a wix project in my solution. Whenever i try to build it, i get the
> following error message :
> light.exe : error LGHT0001: Unable to load DLL 'winterop.dll': The specified
Please file a bug.
--
sig://boB
http://joyofsetup.com/
---
On 18-Aug-10 07:41, Cristian Libardo wrote:
> However, when I try to find this guid in *vs_setup.msi I can't find this
> component guid*. What I do see is this component: VWDExpress_Exe_27323.*
> 3643236F_FC70_11D3_A536_0090278A1BB8*. Is it possible the component guid has
> changed?
Yes. Please
On 8/17/2010 7:58 PM, Ashvin wrote:
>wstring command = wstring(L"\"") + sysDir + L"\\msiexec.exe\"" + L" /a \""
MsiInstallProduct wraps all that for you.
> // continue to next task. I NEED TO END UP HERE WHEN THE 'CLICK NEXT TO
> CONTINUE' BUTTON IS CLICKED.
The "EndDialog ControlEven
On 8/17/2010 9:13 PM, Maillet, Ed wrote:
> Is there a way in a Compiler Extension to create a hidden property.
There's an unreal table named WixProperty that has boolean columns for
all the "special" property attributes. The Compiler class has an
AddProperty method that takes care of all that;
On 8/11/2010 12:36 PM, Chad Petersen wrote:
> The rest of the log does seem to confirm a blank target.
Your CA to set the property is scheduled too late. Why use a secondary
property? You could use the value directly. Otherwise, schedule it
earlier, before WixSchedInternetShortcuts.
--
sig:/
On 8/13/2010 10:58 AM, gapearce wrote:
> Thanks Blair - That fixed it... it would be cool if your sentence explaining
> the problem was easily found or otherwise available in the doc...I was
> scratching my head for a long time over this.
It is, in the ControlEvent MSI doc.
--
sig://boB
http:/
On 8/15/2010 11:25 AM, Philip Garofalo wrote:
> locate files? Will it accept file specs with wildcards? Can it
> recursively search an uncompressed folder hierarchy on the distribution
> disk?
No. MSI requires you to explicitly identify files to be installed. You
could create a custom action th
On 8/11/2010 11:34 AM, Christian Tusch wrote:
> Yes, I'm using WixUI_InstallDir.
Are you running the install with UI? Check out a verbose log to see what
MSI planned.
--
sig://boB
http://joyofsetup.com/
--
This SF.n
On 8/10/2010 4:50 PM, John L Krupka wrote:
> Yes, Burn is the feature you are going to want, as do many of us. It has
> been delayed a couple of times and latest has is slated for version 4.0.
>
V3.6:
http://robmensching.com/blog/posts/2010/4/28/Change-of-plans-for-WiX-v3.5
--
sig://boB
ht
On 8/10/2010 3:54 PM, Chad Petersen wrote:
> Now that I'm past all my ICE errors I'm on to trying some new things.
> Never was happy with the old Desktop shortcuts, so I want to use the new
> InternetShortcut element. Here's what I'm trying to do.
>
> Name="Product" Type="url" Target="[TARGET1]" /
On 8/10/2010 4:52 PM, John Bergman wrote:
> C:\Program Files (x86)\Microsoft Visual Studio 2008
> SDK\VisualStudioIntegration\Tools\Wix
>
That comes from the VS SDK, which includes a subset of WiX for its needs.
> What I find to be particularly perplexing is that we are using the 32bit
> ve
On 8/10/2010 11:07 AM, marric01 wrote:
> But when i'm using the uninstall from the Add/Remove program, it doesn't
> open my custom dialog for uninstall. Do I need to do something special to
> make it use my custom dialog ? It is something possible ?
>
It's not supported by ARP -- it always run
On 8/10/2010 10:10 PM, Patrick van der Velde wrote:
> properties. So this leaves the question how can we populate a (text)
> file with the user names and place that in the application directory.
>
MSI supports writing to .ini files; WiX adds support for writing to XML
files (XmlConfig/XmlFile
On 8/10/2010 7:46 PM, Christopher Painter wrote:
> I was reading in the CHM/XSD that an Upgrade Element can belong to a Fragment
> element. Is this really true? I'm not sure I see what could reference it
> (UpgradeRef? ) in the schema.
>
Yes, it's supported. No, there isn't an explicit way t
On 8/9/2010 1:09 PM, Chad Petersen wrote:
> What would be appropriate defaults for these properties? It seems like
> it wants one of the choices from the RadioButtonGroup. For
> MaintenacneMode this would be either AddRemove, RemoveAll or Reinstall.
>
Yes, you have to provide a default propert
On 8/4/2010 9:57 AM, Pally Sandher wrote:
> You need to set the Win64 attribute on your components. If it's not set
> they default to 32-bit components in an x64 package.
> An easy way to do it is to use a pre-processor variable set to "no" or
> "yes" whether you're building x86 or x64 packages res
601 - 700 of 4751 matches
Mail list logo
