On 3/10/2010 12:01 PM, Cody Gibson wrote:
> I'm not the original person posing the question... but I did try that when I
> wanted the functionality that Jeff is asking for. The problem I ran into
> with the CloseApplication element is that it would either forcefully close
> the application or sched
On 3/10/2010 10:34 AM, Oleksandr Y. Nechyporenko wrote:
> If I will use Component/@Guid="*", it will produce different GUIDs for
> components even inside same product after the each MSI rebuild.
No, it generates stable IDs.
--
sig://boB
http://joyofsetup.com/
--
On 3/10/2010 11:15 AM, Oleksandr Y. Nechyporenko wrote:
> But unfortunately it don't work. Am I missing something?
Check a verbose log to see if MSI is showing the feature changes being made.
--
sig://boB
http://joyofsetup.com/
--
On 3/9/2010 11:14 AM, Oleksandr Y. Nechyporenko wrote:
> will be better to generate new GUIDs for components in different products,
> but it is a little difficult to generate different GUIDs for each component.
>
Use Component/@Guid="*" (or omit it in recent WiX v3.5 builds) to have
WiX genera
On 3/10/2010 8:05 AM, Sagar wrote:
> i have the following requirement
> 1)install an xml file.
> 2)to modify the installed xml file
>
Use XmlConfig.
--
sig://boB
http://joyofsetup.com/
--
Download Intel® Parall
On 3/10/2010 1:38 AM, nro...@gmail.com wrote:
> I'm seeing a situation in which a major upgrade fails to uninstall the
> previous version. I have three package versions like this:
>
Check a verbose log to see why MSI didn't remove the product.
--
sig://boB
http://joyofsetup.com/
--
On 3/9/2010 10:11 AM, Oleksandr Y. Nechyporenko wrote:
> Are there easy way to select language(s) at first step of installation and
> automatically include language depended components to related features?
>
MSI doesn't support multi-language installers (e.g., UI) but you can
include language
On 3/10/2010 6:21 AM, Kristoffer Danielsson wrote:
> That checkbox looks ugly. How do you make it transparent (or solve it some
> other way)?
>
Checkboxes can't be transparent. You can customize the dialog to remove
or resize the bitmap.
--
sig://boB
http://joyofsetup.com/
--
On 3/9/2010 1:33 PM, Sachin Dubey wrote:
> During the change only the properties set in UI sequence are not getting
> forwarded to Install sequence. and this happens only on machines with UAC
> enabled and logged in user is non build-in Admin.
>
See the Property/@Secure attribute.
--
sig:/
On 3/9/2010 9:28 AM, Tom Crozier wrote:
> Or is there an existing property that lets me know how it was invoked?
>
See the MSI SDK for the UPGRADINGPRODUCTCODE property.
--
sig://boB
http://joyofsetup.com/
--
Downlo
On 3/10/2010 3:44 AM, Christian Kraut wrote:
> How can I get the return value of the above query?
>
Custom actions only return success or failure. If you need more control,
you need to wrap the code in a DLL custom action.
--
sig://boB
http://joyofsetup.com/
--
On 3/9/2010 12:10 AM, puyo puy wrote:
> mean I cannot use bootstrapper. I’m think of creating msm for each product
> and
> assign a feature for each msm.
There's no need for merge modules; use a ComponentGroup instead.
--
sig://boB
http://joyofsetup.com/
On 3/8/2010 9:11 AM, Arun Perregatturv wrote:
> For COMServer - Only FeatureF should be selected and displayed(cannot uncheck
> this feature for this type of install) and rest is displayed but unchecked.
> Is this possible?
>
The selection tree control doesn't support that.
> Do have I have
On 3/8/2010 12:10 PM, Johann Taferl, T-AU wrote:
> I have to install some driver to a given folder. For Win Vista, they
> have to- and for all previous Win-versions, they must not be signed. To
> solve this problem I thought of two separate merge-modules. To install
> the correct one, I use conditi
On 3/8/2010 7:56 AM, Andy.Kruger wrote:
> I have added custom action to Finish button that launches a C# exe.
> Also I have added an admin manifest to say that it requires elevation. It
> sets the registry value on Windows XP. But when i run the installer on Vista
> with UAC enabled and click finis
On 3/6/2010 8:22 PM, Paul Baker wrote:
> We're now thinking of registering our COM server using RegistryValue
> elements, where RegistryValue/@Key contains "Wow6432Node". Does anyone
> know of any potential problems with this approach?
>
You might want to listen to what the code is telling you
On 3/6/2010 3:06 PM, Sachin Dubey wrote:
> My installer creates a registry key in HKLM and stores the INSTALLDIR value.
> It provides default INSTALLDIR, however user can change it and the changed
> value gets stored in registry.
>
MSI doesn't persist property values for you, so you need to w
On 3/6/2010 12:04 PM, Richard Fine wrote:
> I don't see any. The same line in a later attempt:
> MSI (s) (48:A8) [20:04:24:913]: Executing op:
> ActionStart(Name=ExecXmlConfig,,)
> MSI (s) (48:A8) [20:04:24:914]: Executing op:
> CustomActionSchedule(Action=ExecXmlConfig,ActionType=3073,Source=Binar
On 3/5/2010 1:05 PM, admiristra...@cox.net wrote:
> I was searching around for a solution to easily update my MSI version
> numbers with each build, but I couldn't find one. So I wrote this and now I
> don't have to remember. Thought I'd share...
>
Even easier method: Use binder variables to
On 3/5/2010 4:32 PM, Uma Harano wrote:
> Can I use the "Greater than equal to " operator for this?
Yes, for the simple case of "4" > "3" but all the operators in MSI are
ordinal comparisons, so "3.0.200" is not greater than "3.0.1000."
--
sig://boB
http://joyofsetup.com/
-
On 3/5/2010 6:08 PM, Sachin Dubey wrote:
> I have a WIX 3.0 installer that deploys SSRS reports using a differed C#
> custom actions.
>
> The impersonation it set to "yes".
>
Impersonated custom actions aren't elevated. If you need elevation, it
must be "no."
--
sig://boB
http://joyofsetup
On 3/5/2010 12:34 PM, admiristra...@cox.net wrote:
> I know we can configure a Launch Condition to check for the existence of
> another installed product before installing, but is there a way to enforce
> or at least warn the user if they later attempt to uninstall the
> prerequisite (especially if
On 3/5/2010 8:31 PM, Alec Taylor wrote:
> Unfortunately, cannot access that website: Parse error: parse error,
> unexpected $ in /w/d/d...@interware.hu/wix/st882/var/access.php on
> line 113
>
Works fine now.
--
sig://boB
http://joyofsetup.com/
-
On 3/5/2010 4:40 AM, Nicole Zheng wrote:
> My codes below works fine (pls ignore the line in italic at this moment).
> However, there's new requirement to config the service during installation.
> I can't use under each (just like the code
> in italic below) because ServiceConfig table requires u
On 3/4/2010 2:33 PM, David Largen wrote:
> C:\Program Files (x86)\MSBuild\Microsoft\WiX\v3.5\Wix2010.targets (1730):
> The specified task executable location "C:\Program Files (x86)\Windows
> Installer XML v3\bin\candle.exe" is invalid.
>
Do you get this error from new projects or just upgra
On 3/4/2010 5:52 AM, Pally Sandher wrote:
> I guess you can't really know success until you've failed.
>
Well, you know it *really* well then.
--
sig://boB
http://joyofsetup.com/
--
Download Intel® Parallel Studio
On 3/4/2010 11:32 AM, Brendan Rice wrote:
> Source="[MYTESTDIR]fileToCopy.dat">
> DestinationProperty="WEBSERVICEBINFOLDER" />
>
>
If you want to copy a file that's already installed on the system (as
opposed to being installed by your packa
On 3/4/2010 3:17 PM, Arun Perregatturv wrote:
> I am using WIXUI_FeatureTree with removal of License and including a custom
> dialog which has 3 radiogroups. Based on the radio group selection I have
> display the feature set in the feature tree. Is it possible?
>
Yes. Use AddLocal and Remov
On 3/4/2010 3:50 PM, Richard Fine wrote:
> MSI (s) (48:34) [19:55:31:273]: Invoking remote custom action. DLL:
> C:\Windows\Installer\MSIBFC7.tmp, Entrypoint: ExecXmlConfig
>
What's after that line? There should be a bit of logging if it couldn't
process an XmlConfig row.
--
sig://boB
http:
On 3/4/2010 11:01 AM, admiristra...@cox.net wrote:
> I guess I'm completely missing how to version files then. I don't
> find any attributes or child elements of component or file that seem
> related. I'm not aware of any consistent file-versioning aspect of
> the windows file systems. Also,
On 3/3/2010 10:50 AM, Pally Sandher wrote:
> Moral of the story, be absolutely certain when you're changing Product
> Codes (still can't believe I made such an error, hoist by ones own
> petard).
>
A higher-level moral: Test serviceability before shipping; afterward is
too late to fix whole c
On 3/3/2010 4:14 PM, admiristra...@cox.net wrote:
> Can someone please detail how Merge Module versioning is supposed to work?
>
There's no such thing. Merge modules are a collection of tables and rows
that are merged into your .msi package, losing their identities in the
process. All versio
On 3/2/2010 10:21 AM, Tabmow wrote:
> I know the PrepareDlg pops up (modeless dialog) briefly at very
> beginning, but is there a way to 'pause' it there or slow it down from
> disappearing so fast? I want to check one thing out on the layout and it
> disappears too fast for me to tell.
>
On 3/3/2010 5:02 AM, Jacek Pospychała wrote:
> anyway, I'm still interested to learn, how the DLL is processed that it can
> throw a popup..
>
Self-reg runs code in the DLL; it can do anything, which is one of the
reasons it's evil in an installer.
--
sig://boB
http://joyofsetup.com/
On 3/1/2010 10:14 AM, Tim St. Clair wrote:
> Custom config file, but it resembles an ini file without any tags/keys.
>
MSI supports .ini files and WiX additionally supports XML. No arbitrary
text support, however.
--
sig://boB
http://joyofsetup.com/
---
On 2/28/2010 5:06 PM, Sanjay Rao wrote:
> MSI (s) (7C:90) [03:01:26:656]: Component: CheckerServerServiceComp;
> Installed: Local; Request: Absent; Action: Null
> I am not able to find any issue in this file. please suggest.
There are several entries of the form
MSI (s) (7C:90) [03:01:26:656
On 3/1/2010 5:39 AM, Paul Baker wrote:
> Is this the intended behavior?
>
Sounds like a bug, though it might be intentional, to let you run WixCop
over a tree. Please file a bug so the triage group can debate it.
--
sig://boB
http://joyofsetup.com/
-
On 2/28/2010 1:09 PM, Semion Prihodko wrote:
> So how can I make a patch replacing two files in old installation which is
> probably doesn't presume patches? Is there really no way to simply replace
> two files? Thanks.
>
MSI doesn't support downgrades except via patching. If you didn't create
On 3/1/2010 1:13 AM, hila toronchik wrote:
> The problem is - that an empty file named Global.jpeg need to be placed the
> development machine in order to build the msi.
>
WiX needs the file to fill out the details of the file (size, e.g.) in
the MSI database.
--
sig://boB
http://joyofsetup
On 3/1/2010 5:22 AM, Igor Paniushkin wrote:
> Is it a bug?
Yes, it's a bug that's already been filed.
--
sig://boB
http://joyofsetup.com/
--
Download Intel® Parallel Studio Eval
Try the new software tools for yourself.
On 2/28/2010 4:17 AM, Sanjay Rao wrote:
> I have a installer which works fine on windows XP and earlier. this
> installer installs some services on target machine. if target machine
> has windows server 2008, then while uninstalling my product installer
> does not removes services from target machi
On 2/28/2010 10:42 AM, Information Vision wrote:
> How can I get the setup to create app shortcut name and app target folder
> name based on the version of the app? Basically I need each version of the
> app to go into its own target folder and have its own unique shortcut name.
>
Use a prepro
On 2/28/2010 6:35 AM, Semion Prihodko wrote:
> The instresting thing is that if I change the content of these binaries on
> target machine (reduce their size down to several bytes) - the files are
> being replaced normally, but this don't work with original ones.
Make sure you update the files' ve
On 2/26/2010 4:47 AM, Andres Juarez wrote:
> Is there any tool or automated way of generating a WXI file from a WXS file?
>
Use an XSL transform. Or don't -- almost everything you can do with an
include file can be done with fragments.
--
sig://boB
http://joyofsetup.com/
-
On 2/26/2010 1:30 AM, simon.su wrote:
>My MIS built by WIX3.0, and I find that it took a lot time(about 2 minute)
> to execute the “SRSetRestorePoint" in the win7(chinese languge version).
>
That's Windows Installer creating a system restore point.
--
sig://boB
http://joyofsetup.com/
On 2/24/2010 9:17 AM, Thorsten Schöning wrote:
> Could you point me the right direction, too? :-) I don't understand
> how I could use Publish or a custom action to send events to the
> selection tree or a specific feature.
>
I'm saying that you can't use the selection tree control to show "li
On 2/24/2010 4:08 PM, Neil Sleightholm wrote:
> I don't remember ever editing that file, I have had many versions of
> WiX3 on this machine so it could be related to that.
>
There might have been a component rules violation when we moved the
.targets file to the v3.5 directory early in the v3
On 2/25/2010 5:36 PM, Rodney Schuler wrote:
> That makes errors like "error CNDL0010: The Component/@Directory attribute
> was not found; it is required.". Hmm... This is just a gob of HKCU entries
> why do I need a directory?
Because every component is associated with a directory. Just use one o
On 2/24/2010 11:37 AM, Jake Boone wrote:
> When is the best time to schedule the update to the table?
>
Before the InstallODBC and RemoveODBC standard actions.
> Looking through the available functions, it looks like rows can only
> be inserted or deleted, not updated. Is that correct?
>
On 2/25/2010 4:49 PM, Dan Vogel wrote:
> I have two installers for my application. The only difference between
> the two is that one includes a directory of demo images, the other does
> not. The installer with the demo images is large, so the second
> installer was created since not all customers
On 2/24/2010 10:33 AM, Rivera, Rafael wrote:
> I put together a WiX 3.0 package, utilizing the DIFx extensions, to
> install a Windows 7 Sensor (UMDF driver). During installation, DIFXAPP
> logged "No matching devices found in INF" and simply threw the driver
> into storage. I read I'm to populate
On 2/22/2010 3:38 PM, Jake Boone wrote:
> The only problem seems to be that ODBCDataSource/@DriverName and the
> nested Property/@Value are not formatted strings.
That's how the MSI ODBCDataSource table is set up, so WiX can't change
that behavior. You could write a custom action that updates the
On 2/24/2010 3:44 AM, Lisa Gracias wrote:
> I've tried the GenerateBootstrapper task in MSBuild but since it bootstraps
> all the prerequisites before calling the msi, it doesn't serve my purpose.
>
You can't install multiple .msis from within another .msi -- that's not
supported by the MSI e
On 2/23/2010 8:32 AM, Thorsten Schöning wrote:
> Is there any way to change the installation status of Feature 2.1
> depending on the status of Feature 1.1 at the time when the user
> chooses not to install for example Feature 1 and therefore not
> installs Feature 1.1?
>
The selection tree co
On 2/23/2010 1:54 AM, Eswari wrote:
> I have created msm using wix. but when i am running the below command
> msidoaction(handle,"CostFinalize") it is returning 1603 error. What did i
> missed in my merge module?
>
Check a verbose log.
--
sig://boB
http://joyofsetup.com/
On 2/24/2010 2:25 AM, Peter Joseph Solomon wrote:
> I have come across this bug posted on the wix bug list:
> SqlDatabase/@User - Change to formatted element - ID: 1520745
>
The bug was closed; I reopened it.
--
sig://boB
http://joyofsetup.com/
-
On 2/23/2010 11:25 PM, MYFLEX wrote:
> [407]: Component: ToolkitUICotent_ToolkitComponent; Installed: Local;
> Request: Absent; Action: FileAbsent
>
> Please tell me what happened. everything is as same as , earlier. only we
> changed the WIX version for building the MSI.
>
The most common c
On 2/23/2010 4:58 PM, Neil Sleightholm wrote:
> I did an upgrade from v3. Uninstalling v3 then installing v3.5 seems to
> work. When I get time I will go back v3 and try an upgrade again.
>
Did you touch the .targets file by chance? The upgrade would have to
rely on file timestamps because it
On 2/17/2010 10:42 AM, Jake Boone wrote:
> I have a custom action where I'm trying to use SourceDir.
See the MSI SDK for details about SourceDir; it's not always available.
--
sig://boB
http://joyofsetup.com/
--
Downlo
On 2/19/2010 8:13 PM, Sharath P R wrote:
> The above was for a CN Pseudo-Loc build. Does Wix V3 flag usage of
> non-codepage characters as errors now?
>
There were many enhancements in WiX v3 for codepage handling.
--
sig://boB
http://joyofsetup.com/
--
On 2/19/2010 4:39 AM, Bimali Ponnamperuma wrote:
> does "Order" attribute plays any role here?
>
Yes. See the MSI SDK ControlEvent documentation.
--
sig://boB
http://joyofsetup.com/
--
Download Intel® Parallel Stud
On 2/19/2010 9:36 PM, Sachin Dubey wrote:
> As per the article
> (http://msdn.microsoft.com/en-us/library/aa371175(VS.85).aspx) , I am setting
> REINSTALL = Feature1,Feature2 on VerifyReady dialog.
>
> Like this --
>
>Value="Feature1,Feature2">
>
The Reinstall control event isn't the sam
On 2/17/2010 8:49 AM, Michael Urman wrote:
> You can't change the type of an existing column, but you can add new
> columns in a transform. Patches are built on transforms, so they
> should be just as capable. As I understand it, the ExtendedType column
> was added (instead of a widened Type column
On 2/18/2010 7:47 AM, Tobi Ha wrote:
> Is there a good and secure way to detect if another MSI installation is
> allready running before starting another one which would fail with Error Code
> 1618?
>
No. And another installation could start immediately after such a check
anyway.
> Additio
On 2/19/2010 4:37 AM, Jacek Pospychała wrote:
> Do you know what extra does the installer do, that takes so much time?
It supports rollback which entails extra bookkeeping to be able to
restore files on failure.
> And
> does it make any change if I e.g. split it to more features, or more
> compo
On 2/18/2010 10:44 PM, Elisabeth Yusnita wrote:
> I have a question about installing apache tomcat as prerequisite using WiX
>
That's really driven by what the Tomcat installer can do. What does the
Tomcat team recommend?
--
sig://boB
http://joyofsetup.com/
---
On 2/18/2010 7:41 AM, Tom Crozier wrote:
> To keep the size of the released installer small do I need to create and
> release a patch instead of the full installer?
>
If you want to ship a subset, yes, you're looking at patches.
> With the recommended installer option to perform the above wh
On 2/15/2010 2:12 PM, Anurag Pahwa wrote:
> Thanks. We've built our MSI using wix 2.0 and if I edit the MSI using orca I
> don't see the ExtendedType column in the custom action table but If I look at
> any MSI which was built using Wix 3.0 and If I edit it using orca I can see
> the ExtendedTyp
On 2/16/2010 11:15 AM, Yan Sklyarenko wrote:
> It seems you are referring the "beta-exit" build of WiX. It can be found by
> this link: http://wix.sourceforge.net/releases/3.0.4805.0/, but it seems to
> be broken right now...
>
> Maybe, WiX admins at sourceforge.net can help here?
>
It's no
On 2/16/2010 4:17 PM, jnewton wrote:
>
> Trying to do
> property::get-value(var.lang + '_cost')
>
>
I don't think it's supported.
> If that's not possible, can I just create a wix extension in which I
> implement my own property::get-value function?
Yes, a preprocessor extension.
--
s
On 2/12/2010 6:19 AM, John Aldridge wrote:
> If I use WiXNetFxExtension to test for NETFRAMEWORK35, does this mean
> "3.5 itself is installed" or "3.5 or any later version is installed"?
>
The former but it's not practical to make generalizations for future CLR
versions since they can be side
On 2/13/2010 4:02 AM, Joergen Bech wrote:
> So I guess the WiX way is fine and I should not care about the Sources value
> not being updated explicitly by WiXUtilExtension.
>
Right. When I wrote EventSource, I went by the Windows documentation.
--
sig://boB
http://joyofsetup.com/
-
On 2/10/2010 11:50 AM, Tabmow wrote:
> Is it possible to change the error dialogs for some of the known types?
> Ie. If i know a certain Windows installer error code, can i override the
> default error dialog with my own dialog from my wix code?
>
No but you can use control conditions to
On 2/9/2010 12:04 PM, Jakub Gwóźdź wrote:
> But the more I think of them (and read on the web) the more scared I am.
> Since the only dlls installed in WinSxS comes from Microsoft (on a few
> computers I've checked so far) I'm starting to wonder why it isn't a
> popular solution.
>
Note that e
On 2/9/2010 2:47 PM, Tony Juricic wrote:
> Since my external UI is WPF I am really bothered, both by having to
> disambiguate several classes and by having to reference forms Dll just for a
> few enums, when calling Installer.SetExternalUI. Hopefully these enums will
> become UI-system-agnostic
On 2/4/2010 2:47 AM, Sanjay Rao wrote:
> I want to get a list of all standard control events used in publish
> element. Can anybody help me out ?
>
The WiX doc links to the ControlEvent table MSI SDK topic, which lists them.
--
sig://boB
http://joyofsetup.com/
-
On 2/5/2010 11:14 PM, sean farrow wrote:
> How do I go about adding an extension to the WiX build.
>
What kind of extension? Which build (WiX itself or your own WiX
project)? Please clarify.
--
sig://boB
http://joyofsetup.com/
--
On 1/24/2010 1:18 PM, Cody Gibson wrote:
> Depth="1" AssignToProperty="yes">
>
The AppSearch action doesn't guarantee an order the table's rows are
processed, so you can't rely on being able to use the results of one
search in another. The log has the details:
> Action start 19:23:35: AppS
On 1/17/2010 8:39 PM, Cody Gibson wrote:
> Why does this wxs file work (i.e. the single file to install is installed at
> the correct location)
>
Usually, people ask why things don't work. Can you clarify what you're
asking?
--
sig://boB
http://joyofsetup.com/
---
On 1/19/2010 5:23 PM, Robert Barnes wrote:
> Which version is the fix in? Is there any info on the web about the bug?
Sorry, I don't know.
--
sig://boB
http://joyofsetup.com/
--
Throughout its 18-year history, RSA Conf
On 1/21/2010 11:51 AM, Reinier Lamers wrote:
> Now according to the WiX documentation the condition of Publish is
> "optional", but it does not say what it defaults to when it is not
> present. I assumed it would default to "1", but apparently it doesn't.
> I still don't really understand what it d
On 1/22/2010 7:42 PM, Jacques Eloff wrote:
> I just ran into a problem. I created an MSI that contains two assemblies.
> Assembly 1 targets .NET 3.5. Assembly 2 targets .NET 4.
WiX v2 doesn't target CLR v4. V3.5 does. You can try adding
supportedRuntime entries for the v4 runtime, but it hasn't b
On 1/20/2010 1:19 PM, Blair wrote:
> Wix.targets uses the $(WixTasksPath) property,
See "Integrating WiX Projects Into Daily Builds" in WiX.chm for more info.
--
sig://boB
http://joyofsetup.com/
--
Throughout its 18-ye
On 1/17/2010 11:10 AM, Giora keinan wrote:
> I have a problem in minor update. In minor upgrade the msiexec is
> looking for the upgrade name, which should be the same as the original
> msi name.
> The problem is that sometimes the original setup filename is modified
> during download. For example
On 1/15/2010 2:52 AM, Robert Barnes wrote:
> actually a part of my product! However this same dll is used by both
> my product and the other program - same dll, same name but installed
> into two different directories, so the other program is not actually
> using the dll that is being installed it
On 1/13/2010 1:28 PM, Inbar, Ron wrote:
> Is there a built-in way in WiX to create such entities or is it necessary to
> write a custom action that calls the Windows API?
>
It's not natively supported by Windows Installer nor by WiX's standard
custom actions.
--
sig://boB
http://joyofsetup
On 1/12/2010 9:11 AM, Mihail Roman wrote:
> msiexec /i Package.msi REINSTALL=ALL REINSTALLMODE=vomus
>
What's the behavior if you use the /f switch instead?
--
sig://boB
http://joyofsetup.com/
--
Throughout its 18-
On 1/12/2010 10:15 AM, Sebastian Brand (Instyler Software) wrote:
> Thanks for the clarification, I thought the shortname was always used. So in
> real life it's probably "WINDOW~1.5" on most machines ( try DIR /X ) But you
> can't be sure... Short file name generation might even be disabled.
>
On 1/13/2010 3:04 PM, Ken Halprin wrote:
> Can I use setupbld to include both msi and exe files as prerequisites before
> my wix-built msi installer runs?
>
Setupbld doesn't support running .exes.
--
sig://boB
http://joyofsetup.com/
-
On 1/13/2010 1:45 PM, pmdarrow wrote:
> I guess that's one way. It just seems a little unintuitive to show pop-up
> dialogs for the requirements. I thought about this for a little while and
> came up with another method. Create one dialog with all of the possible
> requirements if every feature was
On 1/13/2010 2:14 PM, Cody Gibson wrote:
> I've found HEAT doesn't generate any output even for a brand new empty VS2010
> C# class library project.
Might be a missing feature: Heat has to take special steps to support
different versions of the CLR so it might not have been updated for CLR
v4 y
On 1/13/2010 8:07 PM, Navid Azimi-Garakani wrote:
> Is there a particular reason why Heat.exe is targeted and compiled
> specifically against the x86 architecture?
Because an MSIL .exe runs as a 64-bit process on an x64 system, so it
couldn't load x86 DLLs. I suspect there's a need for Heat64.
On 1/13/2010 4:35 PM, Neil Sleightholm wrote:
> I think there is a bug in the output generated when a .Net COM assembly
> is processed with heat but thought I would run it past the community
> before raising it.
If the assembly writes it, Heat includes it. Sounds like a reasonable
thing to drop f
On 1/8/2010 12:53 PM, Wilson, Phil wrote:
> It's like saying you don't support FilesInUse dialogs, requests for the
> original install source, reboots at the end of the install and other things
> that Windows will do whether you want to support them or not.
>
That's key: You can't disable or
On 1/7/2010 12:17 PM, Dominique Louis wrote:
>What would be the best way to add a custom ErrorLog Dialog that is
> only displayed if an error occurs during installation and it would
> appear right at the end of the installation in that case.
See InstallUISequence/Show/@OnExit for the different
On 1/11/2010 11:50 AM, Sebastian Brand (Instyler Software) wrote:
> The short name is generated randomly during the build of WiX installation.
> In my Wix3.5 install it's "nzj-aqro" (in Program Files folder)
>
1. It's not random: it's a stable hash, generated from the path
information so it d
On 1/7/2010 1:11 AM, Bryan Reich wrote:
> New member to the community. How do I file a bug?
>
https://sourceforge.net/tracker/?group_id=105970&atid=642714 (also
linked from http://wix.sourceforge.net/).
--
sig://boB
http://joyofsetup.com/
--
On 1/6/2010 8:17 PM, Jeff Perrigo wrote:
> I'm fairly new to WiX/Windows Installer, but I think things are starting to
> click. The keypath is set at the component level for the counters component.
> This one has been a little confusing since the component itself doesn't
> specify a directory.
Please keep /wix-users/ on the thread so everyone can participate.
On 1/5/2010 10:22 AM, Sean Farrow wrote:
> Just to clarify, is that aproperty?
> are there any examples?
>
Yes. See the MSI help file that's included in the WiX installer.
--
sig://boB
http://joyofsetup.com/
---
On 1/5/2010 12:39 PM, Sharat Janapareddy wrote:
> Hey Bob, the DialogRef element is not a part of the patch schema. I am
> looking at http://wix.sourceforge.net/manual-wix3/wix_xsd_patchfamily.htm. It
> is a child of UI element which can only be used to define UI elements for an
> MSI's WXS file
901 - 1000 of 4751 matches
Mail list logo