Why not just copy the header files to your own folder?
Best regards,
Sebastian Brand
sebast...@instyler.com
Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841 4544567
www.instyler.com - Instyler Setup: Create WiX-based MSI installations,
elegantly.
Have you tried it without the .0 at the end?
Best regards,
Sebastian Brand
sebast...@instyler.com
Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841 4544567
www.instyler.com - Instyler Setup: Create WiX-based MSI installations,
elegantly.
www.traveladdin.com -
The link points to ICE testing. I assume the author is looking for some
testing method that includes the actual installation/repair/remove actions.
I currently use a couple of VMs to test created MSI. To check if the
components get installed correctly I normally have a test program. E.g. if
you
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
Hello Brian,
The CancelDlgText is used on the CancelDlg. When removing the product using
the Maintenance Mode it will show the CancelDlg as you described. This is
probably also the reason why the ActionText on the progress dialog for most
installations is just The installer is performing the
Hi Sean!
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)
Burn is in hot alpha but working I guess :) You can try it in the current
WiX 3.5 release.
Best regards,
Sebastian Brand
You may only show dialogs during uninstallation via a custom action, the
dialogs from the msi won't be shown.
Best regards,
Sebastian Brand
sebast...@instyler.com
Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841 4544567
www.instyler.com
Whereever you want, use add Installed as condition. This tells the
installer to run the customaction if the application is being uninstalled.
Best regards,
Sebastian Brand
sebast...@instyler.com
Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841
Hi Rich,
I think the Certificate tags are for installing a new certificate, not
using an existing. Rob? J
Best regards,
Sebastian Brand
sebast...@instyler.com
Geisenfelder Str. 53a
85053 Ingolstadt, Germany
EU VAT ID: DE219712370
Phone: +49 841 4544567
www.instyler.com
dialog in uninstall process
using Wix
I am not aware, how to show dialogs via custom actions. Please help with
some sample code.
Thanks Regards,
Sanjay Rao
Sebastian Brand (Instyler Software) wrote:
You may only show dialogs during uninstallation via a custom action
Hello,
Note that the .msi file type does not have an icon, the icon you see in
Windows Explorer is from msiexec.exe of the local system. It's not in the
.msi file itself. You can only change that icon if you use an .exe file
instead of the .msi
Best regards,
Sebastian Brand
Deployment
There's no option to find out if the property was set using the command
line. You'll have to handle your defined default value for the property
instead. For example, set the default value of your property PROPERTY_RUNCA
to Secret. For the custom action, set a condition to
PROPERTY_RUNCA=Secret.
Do not use 0 and 1 as values as 0 is recognizes as uninitialized.
Have you tried strings like yes and no?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Blog: www.sebastianbrand.com
-Original Message-
From: Sudripta Nandy
There is a wixui_zh-cn.wxl for Wix2, but not for Wix3.
You could use a converter like
http://www.khngai.com/chinese/tools/convert.php
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Blog: www.sebastianbrand.com
-Original Message-
From: Tony
I think you need to keep this table to ensure others your app was ICE
validated, I remember this was part of the Designed for Windows
requirement or so.
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Blog: www.sebastianbrand.com
-Original Message-
You can create an image that looks like a hyperlink and use that on the
button.
Also note, that MSI 5 supports hyperlink controls. Unfortunally it's not
backward compatible, the UI cannot even be launched anymore, so the whole
installation must be MSI 5 only...
Best regards,
Sebastian Brand
How's the service pack deployed? Is it a patch (.msp) that the user has to
run manually?
The 1334 error normally occurs if a file cannot be found in the source
msi/cab file. I could imagine that some users are running the cached msi
file instead of the original msi file to apply the patch file
Have you tried Clean Solution / Rebuild All?
Does the Compiler output say something about unchanged project?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Blog: www.sebastianbrand.com
-Original Message-
From: spsingam
Unfortunally, Windows Installer resolves this when creating the shortcut:
From the doc:
The references are resolved to an actual path when the installer resolves
the working directory to create the shortcut.
- http://msdn.microsoft.com/en-us/library/aa371847%28VS.85%29.aspx
Best regards,
If you have a radio button group, we don't use the property you have associated
with the radiobutton group in the commandline.
How are you setting the InstallLevel using the radio buttons?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup -
Untested but'll you get the idea:
Set installer = Wscript.CreateObject(WindowsInstaller.Installer)
Set database = installer.OpenDatabase(c:\path\toyour\msifile.msi, 0)
query = SELECT 'Value' FROM Property WHERE Property='ProductCode'
Set view = database.OpenView(query)
view.Execute
Set record =
Can you post the .wxs with the ConfigureIIS customaction tags?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On 19.11.2009, at 08:36, Kusuma Sudheer Kumar (Tata
to in order to run CustomAction commandline.
Maybe if I can check the value of INSTALLTYPE in CustomAction I can do it,
but how do I check that value?
Thanks,
Arun Perregattur
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent
Directory=APPLICATION_TOOLS_DIRECTORY
ExeCommand=[SERVERVALUE]
Return=asyncWait /
This is right?
Arun Perregattur
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us
Can you give us the corresponding .wxs code?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On 18.11.2009, at 21:13, Rich Daniel wrote:
I'm in the process of
Add to the conditions your are check a NOT Installed to check them only if
the application isn't installed yet
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On
When you cannot merge these two installers into one, it's recommended to use a
bootstrapper to check and run necessary installations. I'm not sure if WiX'
burn can handle this already..
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup -
Doesn't the msi verbose log say anything?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On 17.11.2009, at 22:55, Tom Crozier wrote:
I created an installer that
I'd also like to point out to http://www.tramontana.co.hu/wix/lesson3.php
, a detailed tutorial about custom actions...
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
Hi,
Have you checked (using ORCA) if the conditions are written to the MSI file?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Dan
It seems that the Custom Actions are scheduled after the Welcome dialog or
somehow. How and where did you schedule them?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
What happens when you try to uninstall the patch?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Andy2k8 [mailto:appr...@gmail.com]
Hello Prabhakaran,
Does the Vista run as x64? Then it's possible that MSI checks for the 32-bit
registry key (Wow6432Node) instead of the 64-bit. To do that set @Win64=yes
in the RegistrySearch element.
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler
Hello,
I don't think this relates to the installer or WiX. Is .NET installed on the
target machine?
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original
installations, elegantly.
http://www.instyler.com
On 30.09.2009, at 15:35, danimian wrote:
Hi,
yes .NET Framework 3.5 SP1 is our basic requirement and it is already
installed on target machine.
How to deal with this? Any Idea?
Best Regards and Thanks for quick reply
Adnan
Sebastian Brand
On 30.09.2009, at 17:38, danimian wrote:
I just tried to install it manually, it's not working manually.
Sebastian Brand (Instyler Software) wrote:
I think, it's still something bigger than just a WiX issue...
Can you manually install the application on the without using an
MSI/
WiX
Can you tell us why you wanted to create a MSU file?
In most places where one would be able to use MSU (MDT and SCCM) there are
also possiblities to have msi or exe installations.
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating
the path in PathEdit, then click Next. The installation will
start. All other files are copied to changed path, say PathB, only the two
files in SQL folder. It is still copied to original APPLICATIONFOLDER
Regards,
Chunyan
-Ursprüngliche Nachricht-
Von: Sebastian Brand (Instyler Software
Hello,
Unfortunally it seems that only using a Custom Action can resolve Trimming
and most string manipulation issues. Fastest way would be a small vbscript
to change the property value.
Oh, we have some nice weather here too. Greetings from southern Germany. :-)
Best regards,
Sebastian Brand
Hello,
I'd recommend to following:
First, use a RegistrySearch or FileSearch to find the existing product
and installation path. The found value is stored in a Property.
Then, if that property is set (=old version exists), show a dialog to warn
the user. On that dialog run a Custom Action that
This sounds pretty harsh imho. :) I think it is indeed allowed to set
*user* settings during a per-user installation and even All-Users or
Default-User settings in a per-machine setting. If I remember
correctly, Microsoft Office is using the Pinning feature in the 2010
version as well.
You'll have to stick with a custom action for that. To read a text
file, I'd just use VBScript to read the text file ( fso.OpenTextFile
(...).ReadAll ) and store it in a property (if it's a short text).
Otherwise it depends on your purpose.
Best regards,
Sebastian Brand
Deployment
Can you see any pattern of the files not having the Path changed?
Is the path stored in a public secure property? (Uppercase property name and
@Secure=yes)
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations,
.
And I didn't see the secure property there.
Best regards,
Chunyan
-Ursprüngliche Nachricht-
Von: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Gesendet: Montag, 28. September 2009 16:11
An: 'General discussion for Windows Installer XML toolset.'
Betreff: Re: [WiX-users
Create a custom action that triggers your command and schedule it using the
condition Installed in the InstallExecuteSequence after the sequence
position of the other custom program that iss sequenced during installation
(set that condition to NOT Installed to ensure it doesn't get ran during
Hello,
You'll have to fill properties and use them in the Script with Session
(MYPROP) for example.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
On 18.09.2009, at 05:11, puyo puy wrote:
Hi there,
I want to send
Since MSI does not support dialogs in the uninstallation of a product,
you'll have to create a Custom Action for asking the user.
Best regards,
Sebastian Brand
Deployment consultant
E-Mail: sebast...@instyler.com
Instyler Setup - Creating WiX-based MSI installations, elegantly.
Setting the ProductCode to Autogen (Product Id=* .. ) will create
independent products for each new version. When you set OnlyDetect=yes
this will not remove the older versions but only set the
PREVIOUSVERSIONSINSTALLED Property to the product guids of the older
versions.
Best regards,
The $env.WinDir variable is only available during built time - on your PC,
not at the end-users. Use MSI properties like [WindowsFolder] instead.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
Hello,
Are you sure the INSTALLDIR property is set already when the FileSearch
begins?
Also try removing the @Id from the FileSearch, I remember there was an issue
with that when trying to get sub-directories.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations,
Can you post some wix code?
I'd set the other properties when the user clicks Next on that custom dialog
with the radio buttons. Use the Publish element at the Next control.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
Hi,
Add a Condition right under Product. The message in the @Message
attribute will be shown whenever the condition is false, and setup is
aborted.
The condition should contain a Property that gets initialized with
RegistrySearch or FileSearch to find a registry value or file from the
other
You must add -ext WixIISExtension to the light.exe command line.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Jaspreet Nabha [mailto:jaspreet.na...@headstrong.com]
Sent: Friday, August
use the said command ?
Thanks
Jaspreet Singh
From: Sebastian Brand (Instyler Software) [wix+us...@instyler.com]
Sent: Friday, August 28, 2009 1:18 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Problem while
.
Subject: Re: [WiX-users] Problem while creating virtual directory
Hi Sebestian,
I am using VS 2008 for the build process. Can you please let me know how can
use the said command ?
Thanks
Jaspreet Singh
From: Sebastian Brand (Instyler Software) [wix+us
Hi,
Instead of using SKIP_MERGE_MODULES I'd just check for ALLUSERS=1 in die
Condition.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: asanami [mailto:alexsan...@gmail.com]
Sent:
You can suppress harvesting that using the -sreg argument in heat.exe.
Sample:
heat dir c:\folder\with\files -out dynamic.wxs -ag -sreg
-ag sets to component guid to * to have them autogenerated during compile
time.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI
Hello,
Windows Installer executes uninstall in Silent mode (no UI) mode only. To
show a dialog, you'll have to create a custom action to show a dialog, then
schedule that during uninstall.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
PhysicalMemory returns the size of RAM in MB. This should work. Where are
you using this property?
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Sunkesula, Srivardhan
When sequencing the custom action, use MyFeature=3 to schedule it whenever
the MyFeature feature is being installed.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Yan Sklyarenko
Hello,
It's not built-in yet. One could extend the Wix Preprocessor to
automatically generate new File elements.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Jaspreet Nabha
Hi Sebastiaan,
Windows Installer only supports BMP and JPG, and I remember the built-
in reszing method looks horrible too. I also remember JPEGs are shown
badly sometimes (like being compressed to 10% or so), so BMP is still
the best option.
Best regards,
Sebastian Brand
Instyler Setup -
Hi guys,
Does anybody know why the following standard sequence actions are allowed in
the adminUIsequence table? I thought they should be authored into
adminEXECUTEsequence only. Wix though allows to add them to adminUIsequence
as well:
- InstallValidate, InstallInitialize, InstallAdminPackage,
Hi,
Can the service be started manually after it got installed?
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: bonn deng [mailto:bonnd...@gmail.com]
Sent: Thursday, August 20, 2009
Hi Sean,
To get the registry values use the RegistrySearch element to set the value
to a property. Then use a CustomAction with a condition using that
property. Schedule that custom action after InstallInitialize in the
InstallExecuteSequence.
Best regards,
Sebastian Brand
Instyler Setup -
Hello,
Check the order of the events in the resulting MSI in the ControlEvent
table. Maybe the Publish event you are adding with Order=1 is set after the
NewDialog element to show the next page...
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
Hello,
By default, Windows Installer never deletes files it doesn't know of (user
files). So how is this accomplished in v1.0.0?
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From:
-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent: 20 August 2009 11:30
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Obtaining a property and running an exe if,and only
if a property contains a value
Hi Sean,
To get
=REMOVEDIRS Property=CMD ExeCommand=/C rd /S /Q
quot;[INSTALLDIR]quot; Return='asyncNoWait' Impersonate=yes /
:)
2009/8/20 Sebastian Brand (Instyler Software)
wix+us...@instyler.comwix%2bus...@instyler.com
Hello,
By default, Windows Installer never deletes files it doesn't know of
(user
ui.
Sean.
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent: 20 August 2009 12:34
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX-users] Obtaining a property and running an exe if,and only
if a property contains
I think you have to create 2 setups, one for x64 and and for x86. In your
current situation it will copy everything to Program Files (x86) because the
msi package is x86, so the msiexec is running in x86 mode and does not know
about x64...
Best regards,
Sebastian Brand
Instyler Setup - Creating
Hi Ben,
The only valid options are using ARPNOMODIFY and ARPNOREMOVE to
disable the change and/or remove button. The ARP control panel seems
to know when a Windows Installer package handles Modify different from
Remove, so you'd have to remove some registry values from the HKLM\..
This should only happen if the key was existing prior to the installation
already.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: sandun css [mailto:sandun...@gmail.com]
Sent: July 27,
Hi,
First, check that your Windows Installer Version is current, I remember
Error 2902 was part of a MSI engine fix sometime ago.
If that's not it, try splitting the cab file. Unfortunally, WiX doesn't seem
to support this yet.
More about #2902 -
And -cultures:en-us too :-)
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Konstantin Vlasenko [mailto:konstantin.vlase...@gmail.com]
Sent: July 22, 2009 7:43
To: General discussion for
Hi Tuanqing,
Can you post some Wix code you are using? Is it possible that the shortcut
gets modified somehow (maybe it links to DOS command which automatically
modifies .lnk to .pif files)
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
Hi Hukum
It seems that ReserveCost supports 2GB at maximum. Have you tried adding
five ReserveCost elements to get 5x2 GB=10GB ?
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From:
Hi,
A bootstrapper is planned with burn for WiX 3.5 pretty soon (*wink to
Rob*). So far, there's no built in exe packaging in WiX.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: A.S
Hello Sandun,
You cannot initialize the property default value with another property value
or environment variable.
You may either use a SetProperty custom action or get the default value from
the registry using a RegistrySearch within that Property to get the
environment variable value from
Hi Libin,
Create a property and add a FileSearch to find out if Mono is installed
already. Then change the condition of the InstallMono action to run only
when that property is not set (ie. Mono was not found on the system).
You may want to do the same with the GTK action to avoid reinstallation
If the installer runs in 32-bit mode, the registry value is written in the
Software\WOW6432Node\Microsoft\... key. 32-bit applications will still find
it at the right place as Windows maps that.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
and I don't know most of the keywords and functions.
Thanks a lot
Libin
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent: Thursday, July 16, 2009 2:02 PM
To: 'General discussion for Windows Installer XML toolset.'
Subject: Re: [WiX
Hello Natalia,
The SelectionChange event is only published by a DirectoryList, so it won't
update your Edit box when the folder selection in the listbox is changed.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
We had a similar problem. When using the transform trick, the initial
language of the msi package has to be the language of the system (regional
settings - location) or the transforming won't find the right mst file...
Solution: set the Package Languages field to 0.
Best regards,
Sebastian
Hello,
You can use the ReserveCost element under any component to reserve
additional disk space.
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Hukumchand Shah
Hello,
The @Source is used by the WiX compiler when creating the .msi file to read
the file you want to add to the msi. WiX does not handle any [] Properties
during compile time - Properties are handled by the MSI Engine during
installation.
To achieve your goal use a compiler variable, e.g.
of feature can only be got in run time...
So, I want to set a property only based on feature selection and use it in
Source attribute of File element..
On Thu, Jul 9, 2009 at 3:14 PM, Sebastian Brand (Instyler Software)
wix+us...@instyler.com wix%2bus...@instyler.com wrote:
Hello,
The @Source is used
Hello,
All values except 0 and (empty string) are interpreted as TRUE. So you
may use the condition
MYFLAG AND (Installed OR (POWERSHELL = 1.0))
and have the commandline msiexec /i installer.msi MYFLAG=anyvalue
Best regards,
Sebastian Brand
Instyler Setup - Creating WiX-based MSI
Message-
From: Sebastian Brand (Instyler Software)
[mailto:wix+us...@instyler.com]
Sent: Tuesday, June 30, 2009 4:34 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] wix3_x64.msi
Hello,
I was just installing the x64 version of WiX and noticed the files
are
identical
I got it working. I compiled winterop.dll as 64-bit.
Back on Route 64...
Sebastian Brand
Instyler Setup - Creating WiX-based MSI installations, elegantly.
http://www.instyler.com
-Original Message-
From: Sebastian Brand (Instyler Software) [mailto:wix+us...@instyler.com]
Sent
Hello,
I was just installing the x64 version of WiX and noticed the files are
identical as in x86. All binaries are Any Cpu assemblies. Can someone tell
me what (besides the installer) are the differences in the x64 release of
WiX?
Best regards,
Sebastian Brand
Instyler Setup -
91 matches
Mail list logo