If you always want to restore it to "false", XMLConfig can be used to
set a value on uninstall. See
http://wix.sourceforge.net/manual-wix3/util_xsd_xmlconfig.htm
If you want to store what it is before installation & then restore that
value, you'll need to use a Custom Action to read it then use a
According to MSDN a Feature with Level="0" isn't displayed
(http://msdn.microsoft.com/en-us/library/aa368585(v=VS.85).aspx) Hence
you could try using the Property your RadioButtonGroup sets as Feature
Conditions for your 2 main Features & set the Level to 0 using mutually
exclusive Conditions. e.g.
Isn't the point of SharpSetup that it bootstraps .NET 2.0 when required
before running its .NET 2.0 bootstrapper/embedded UI? Also I don't think
Grzegorz was suggesting using SharpSetup as a full solution, merely as a
GUI for WiX projects.
I'd be interested to know how many computers running XP wo
To answer your question, no I don't think that's possible. I think you
need at least one Component under that Feature to enable that option.
FYI Features install Components not files & Components can contain more
than just files. You could try & work around that by creating a
Component which instal
If you don't want to use 1 file per component with "*" GUID, write an
app or script to parse through your .wxs files & regenerate the GUIDs
for you. I wrote a little C# app a while back to do this & it was
probably less than 50 lines of code as one of our deployment scenarios
is identical to yours.
Add a LaunchCondition which checks the REINSTALLMODE property is not set
but make sure you test patching/upgrading if you're going to be shipping
MSP's and/or major upgrades in the future as they set it too IIRC.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F:
Set InstallPrivileges="elevated" for your Package Element (may also want
to set InstallScope="perMachine") & use the "Privileged" property in a
LaunchCondition to ensure the user running it has Administrator
privileges.
It should then automatically request elevation when starting the
InstallExecut
1 - WiX is a tool for creating Windows Installer packages. Windows Installer
doesn't have a HTML Control type so WiX can't support it ->
http://msdn.microsoft.com/en-us/library/aa368039.aspx
2 - As far as I know you can't unless you write your own External UI/Embedded
UI.
3 - See #2 or use a bo
Try
NOT
PREVIOUSVERSIONSINSTALLED
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Register
Use v3.5 or v3.6. v3.0 has no VS2010 support as it was released long
before VS2010 was even in beta.
Also v3.5 isn't a beta, it's release candidate now. See
http://robmensching.com/blog/posts/2010/10/29/Trick-or-treat-WiX-v3.5-Re
lease-Candidate & also
http://robmensching.com/blog/posts/2010/11/13
hinde :
> > I tried this InstallScope="perMachine"
> > it work but then the problem occurs when custom action tries to
> > execute
> and
> > cause failure of installer
> > and it also fails when user is admin group member
> >
> > Is there any way t
ing it 1 month bac so am new at all these
things
Thank you
On Thu, Nov 25, 2010 at 6:07 PM, Pally Sandher
wrote:
> sighself reg.
>
> Also
>
> sighchaining MSI's (and still using a bootstrapper to
> elevate!).
>
> Palbinder Sandher
> Softwar
ials
Thank you.
On Thu, Nov 25, 2010 at 6:43 PM, Pally Sandher
wrote:
> Rob M. posted on this *yesterday*
> http://www.mail-archive.com/wix-users@lists.sourceforge.net/msg42532.h
> tm l & there have been dozens of threads on this subject on this list
> over the years as wel
Sagar the first attribute has nothing to do with the question & the
second will do the opposite of what you're intending (unless your
intention is to confuse people).
Antonio your question is a little vague, do you want the MSI to elevate
or the installed application? If it's the MSI see my respon
Use a RegistrySearch to find some well-known key or value installed by
.NET 4.0. That's pretty much all the NetFxExtension properties do.
On the subject of v3.5, Microsoft themselves have been using it to ship
retail products such as Visual Studio 2010 long before it was even
upgraded to release c
I agree with Neil. The welcome page is very useful for informing the
user what they're actually installing before they are faced with things
license agreements or even Install buttons (with possible UAC elevation
shield). It's clean, uncluttered & gets the information across to the
user without con
v8.0.50727.762 of the VC++ 8.0 libraries is ancient (VS2005 SP1). Are
your binaries definitely built against that version of the VC++
libraries as the ATL security fix (which is in essence a stealth SP2 for
VS2005) released in July last year updates them to v8.0.50727.4053.
That'd be the first thi
http://msdn.microsoft.com/en-us/library/aa367748.aspx
Set it yourself if Windows Installer is getting it wrong. I've not seen
it happen for my packages as yet but I think it happens with very large
packages more often & our largest install is <1 GB.
Palbinder Sandher
Software Deployment & IT Adm
http://msdn.microsoft.com/en-us/library/aa384232.aspx
Your MSI is built for x86 platforms. Build it for x64 if you don't want
it to do that on x64 platforms.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design
You posted the usual one yourself. Either that or suppress ICE57.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in S
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] ICE57 with HKMU
Do you mean using HKCU? That results in an incorrect installation with the
shortcut in the All Users menu, and the key Path in HKCU.
2010/12/2 Pally Sandher
> You posted the usual one yourself.
Wouldn't it be simpler to have 1 executable that does all the work for
you rather than this chain of executables ending in MSI's?
dotnetinstaller (http://dotnetinstaller.codeplex.com/) for example could
simplify that whole convoluted process to 1 executable containing both
your MSI's & all your ca
, since that has the backing and expertise of
> Microsoft employees; if Burn is anything like the quality of WiX
> itself I expect it to be top-notch.
>
> -Original Message-
> From: Pally Sandher [mailto:pally.sand...@iesve.com]
> Sent: Friday, December 03, 2010 16:40
> To:
One possible solution is to split your installation into 2 (or more)
parts & use separate MSI's for each part. That way you're only patching
or upgrading a smaller set of the whole. If your installation has files
which very rarely change if at all, you could put those into their own
MSI which insta
You could simply duplicate the RegistrySearch into a second Property & set the
Win64 attribute accordingly on each? E.g.
The 2nd RegistrySearch will give you an ICE80 *warning* for using a 64-bit
RegistrySearch in a 32-bit package which you can suppress (or just ignor
Been asked before (many many times, see nabble or mail-archive.com).
Unless Windows Installer supports it, it's unlikely for WiX to support
it. In this case you're limited by the Cabinet API if you want to ship
purely MSI's. Cabinets are either LZX or MSZIP algorithm compression.
If you want to im
I haven't had to use it myself but have you looked at WiX SQLExtension?
http://wix.sourceforge.net/manual-wix3/sql_xsd_index.htm It appears to have an
SQLScript Element which may or may not be what you're looking for.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8
If you're only updating a couple of files at a time you may want to look
into shipping MSPs to your existing users rather than having them
download the full MSI every time. See the doc pages on creating patches
-> http://wix.sourceforge.net/manual-wix3/patching.htm for the 2 methods
of creating MSP
http://sharpsetup.eu does exactly that for ExternalUI rather than
EmbeddedUI but it should be enough to get you started.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Inte
Not as far as I know. Either use a bootstrapper to uninstall it using
"msiexec /x [ProductCode]" or patch an UpgradeCode into it first.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate w
I assume by "update" you mean major upgrades?
You could simply Condition the calls to InstallDirDlg from
LicenseAgreementDlg & VerifyReadyDlg appropriately so it only shows
during first install.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8
vate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 10 January 201
http://blogs.msdn.com/b/windows_installer_team/archive/2005/09/18/461810
.aspx
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. R
r 2 GB.
____
From: Pally Sandher [pally.sand...@iesve.com]
Sent: Thursday, January 13, 2011 11:37 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] error compiling large MSI
http://blogs.msdn.com/b/windows_installer_team/archiv
http://wix.sourceforge.net/manual-wix3/heat.htm
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151
The core problem here is something you've highlighted already yourself
Rob in your earlier post. Windows Installer is repeatedly & vehemently
inconsistent (consistently inconsistent?). As you state, it quite
happily recognises 4 version fields for File versions but Products are
limited to 3. As per
Try CompressionLevel="high" as it's better than "mszip" in my
experience.
Also your MSI itself will be a significant part of that 4.5 depending on
it's complexity. Build with EmbedCab="no" to see what size it is itself.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945
Files specified in Binary elements are embedded within the MSI. You'd
need to extract it from your MSI first to a known location which is
neither easy nor quick to write.
The usual widely used solution is to install the file & refer to it
using it's File Id (use [#FileId] for the full path) in your
lset.
Subject: Re: [WiX-users] compression
Why isn't there a "best" setting?
Like with NSIS; one which tries each one and gives you the best compression =]
On Mon, Jan 17, 2011 at 9:31 PM, Pally Sandher wrote:
> Try CompressionLevel="high" as it's better than &qu
user the result =]
On Wed, Jan 19, 2011 at 12:01 AM, Pally Sandher wrote:
> Because the Cabinet file format doesn't track compression by each individual
> file. The cabinet file itself has a compression level set & all files
> compiled into the cabinet file are compressed
ICE tests require access to the Windows Installer service (msiexec.exe)
to run their validation of your MSI. Could it be that it's taking much
longer to start up on Windows 7 or isn't available for some other reason
(UAC?) for a few moments after it starts? Try monitoring your running
processes in
InstallUISequence = full UI. ARP runs with basic UI. Hence you should
test both installation & uninstallation using basic and/or no UI (/qb or
/qn parameters supplied to msiexec respectively) as well as full UI so
you don't trip up in situations like this.
Also most remote deployment systems (e.g.
nce.
So this works fine as it happens in full UI mode.
Now during uninstall I am calling same tool via Custom Action but that
doesn't work.
So do u know of how to do uninstall these child MSIs?
Thanks,
AK.
-Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent
Use a Type 51 Custom Action.
[author your plug-in components & directory structure here]
Substitute GITSEARCHPROPERTY for whatever you have named the Property
you populate with the RegistrySearch. That way GITLOCATION will be
dynamically set d
I saw a user with a very similar sounding issue because he'd used the
"Windows Installer Clean Up" tool to remove a build of our software he
believed was a "bad install" (thanks InstallShield et al for
mis-educating users for years) & then re-installed using the same
installer. He knew nothing of C
If you're clever about it you can build your 2 platform specific MSI's & embed
them into a bootstrapper without doubling the size of your download.
See the -cc & -reusecab switches for light.exe.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 94
Features are selected or unselected for install depending on the
INSTALLLEVEL value not whether their Level attribute is even or odd. See
http://msdn.microsoft.com/en-us/library/aa369536.aspx
A verbose log should tell you what's happening with the default states
of your Features.
Palbinder Sandh
This works pretty well for me when shipping internal beta builds
http://blogs.msdn.com/b/johnls/archive/2006/11/13/how-to-upgrade-softwar
e-with-a-windows-installer-package.aspx
No bootstrapper required.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0
Some of the ICE tests are written in VBScript as Blair notes in an
earlier reply (scroll down). They will be the ones which were failing
for you.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate +
I can see it at
http://wix.sourceforge.net/manual-wix3/authoring_first_msbuild_project.h
tm
Are you 100% sure the URL isn't being split across 2 lines? It should
end in .htm.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://ww
You can't attach stuff to list replies.
If you've Customized your UI you need to declare the DefaultUIFont
Property same as the stock WiXUI's do. See the source for any of the
WiXUI's (e.g src\ext\UIExtension\wixlib\WixUI_InstallDir.wxs).
Palbinder Sandher
Software Deployment & IT Administrator
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Rune Moberg [mailto:jjfl...@gmail.com]
Sent: 25 January 2011 14:54
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64 Bit progr
L toolset.
Subject: Re: [WiX-users] Build failed?
So where is this declaration? What should it be? Where do I see the
stock WiXUIs?
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-----
From: Pally Sandher [mailto:p
Easiest way? Install WiX v3.5.2519.0, upgrade all your .wxs files using
WiXCop.exe then create a new .wixproj & add them to it.
Alternatively, upgrade to WiX v3.5.2519.0, open your solution & hope for
the best. If that fails see above.
Votive in WiX v2.0 was very experimental & not ready for produ
What Registry Entry are you referring to? In that entire sample there is
but one RegistryValue which is simply a stub entry used as a KeyPath for
a component.
It appears you're missing the entire point of that How To guide. The
purpose is to create a clickable shortcut which will uninstall your
pr
there documentation on how to create a custom UI? This worked for 2.0
but it must of changed for 3.0.
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: T
The documentation had a registry entry:
Kevin Burton
Senior Software Engineer
BUYSEASONS
262-901-2000 Office
262-901-2312 Fax
kev...@buyseasons.com
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Tuesday, January 25, 2011 11:24 AM
To: Gen
Yes you do have a directory with Id="DesktopFolder".
A cursory search for Id="DesktopFolder" found that in seconds in your
code. That should be Directory not DirectoryRef which is what the error
is telling you. You're trying to reference something which doesn't exist
as far as your code is conc
Have you Published the required Control event to show your Custom Dialog
to the Next button in the LicenseAgreementDlg?
When you click the Next button in the LicenseAgreementDlg the verbose
log should tell you what it's actually doing at that point. I'd wager
that's a good place to look.
Palbind
Custom UI?
I see 'Doing action: WelcomeEulaDlg' but I don't see anything about
LicenseAgreementDlg.
Maybe it is changed names and that is why I don't see the dialog. I have
code like
-Original Message-
From: Pally Sandher [mai
.com
-Original Message-
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: Thursday, January 27, 2011 10:16 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Skipped Custom UI?
So you're using WiXUI_Minimal & also defining the exact same di
You should be able to use "msiexec /fv [original.msi]" to recache the
source although it would also run a repair of the installation.
The root of the problem is the missing cached MSI. You need to fix that
to be able to uninstall as otherwise Windows Installer has no idea what
to actually uninstal
You broke the component rules some how. A less error prone way to deal
with shared files of this type is to use either a wixlib or a merge
module. That way you're guaranteed to install the exact same thing &
much less likely to break the component rules.
Palbinder Sandher
Software Deployment & IT
Would it be possible to release upgrades for both products with the
Event Sources authored? That way you can uninstall both.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
but the patch seems to ignore this.
Any other ideas please?
-Original Message-----
From: Pally Sandher [mailto:pally.sand...@iesve.com]
Sent: 28 January 2011 10:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Problem when Uninstalling a Patch.
You broke
Rune take a look at the -arch parameter for candle as it sounds like
it'll do exactly what you need. Bob A mentions it in on his blog @
http://www.joyofsetup.com/2010/05/14/working-hard-or-hardly-working/
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0)
sion for Windows Installer XML toolset.
Subject: Re: [WiX-users] one .wixproj -- two platforms
On Mon, Jan 31, 2011 at 3:45 PM, Pally Sandher
wrote:
> Rune take a look at the -arch parameter for candle as it sounds like
> it'll do exactly what you need. Bob A mentions it in on his bl
When you build your 1.0.3 patch have you defined target images for both
the 1.0.0 & 1.0.2 version under the 1.0.3 Upgrade Element in the Family
Group or just one of them?
If you put both in you should be able to create a 1.0.3 patch which
updates either 1.0.0 or 1.0.2 versions to 1.0.3 & thus skip
Or dotnetinstaller -> http://dotnetinstaller.codeplex.com/
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland
And how would using dotnetinstaller do that?
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
There is a 'hacky' way to do it but bear in mind that once you follow
the 'hacky' method, all future patches will be required to be built the
same way. Also because you've 4 Products, your patches are going to be
around 4 times as big as each Product will have it's own CAB (since it
has it's own tr
The recommended method to create shortcuts is almost as per your code. See
http://wix.sourceforge.net/manual-wix3/create_start_menu_shortcut.htm
I don't particularly like putting HKCU keys in a per-machine package either but
that seems to be the accepted method so I've learned to live with it.
Probably a stupid question but is your Fragment actually getting
included in your MSI? Do you have a ComponentRef for that Component in
your Features? Open the MSI in InstEd! or Orca & see if any of your
Class Id's or TypeLibs from the Fragment below are listed in the
Registry table. If they aren't
Check a verbose log.
Palbinder Sandher
Software Deployment & IT Administrator
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Hel
The FileName column in the File Table isn't of Formatted type so that's
not likely to work -> http://msdn.microsoft.com/library/aa368596.aspx
No harm in trying though.
If that doesn't work I think the only way to do it properly would be to
externalise your UI from Windows Installer & then modify
http://wix.sourceforge.net/manual-wix3/WixUI_customizations.htm
&
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the
2 things could potentially cause an issue of that ilk come to mind.
1 - If you've authored a per-user package & are trying to install
per-machine registry entries as below & the account you're testing your
installs with doesn't have administrator permissions. I would however
expect that to throw w
Check
A
Verbose
Log.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Buildin
Have you looked at the help output from heat.exe?
The -suid flag is what you're looking for.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limite
Directory ID's can be anything you like as long as they're valid
identifiers (see http://msdn.microsoft.com/en-gb/library/aa369212.aspx)
since they go directly into the Directory table. They don't need to
reflect the actual name of the directory.
Just rename it after harvesting.
Palbinder Sandher
Take them out of the InstallUISequence unless there's some UI that
depends upon them.
Palbinder Sandher
Software Deployment Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Regis
Try http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No.
SC151456
Registered Office - Helix Building, West Of Scotland Science Park,
Glasgow G20 0SP
Email Disclaimer
-Original Message-
From: Andrew Jones [ma
You're trying to search WoW6432Node from a 32-bit process. It doesn't exist in
that context. Remove it from your Key & it'll magically* work.
*Note: no actual magic is involved as it's a fictional concept which doesn't
exist. The Windows-on-Windows subsystem does all the clever stuff redirecting
and also Win64 element. I just want to know at the
end if ISPRESENT is empty ot not. HOw do I check that? If ISPRESENT is
empty, I want to enable a control.
On Mon, Jan 30, 2012 at 2:29 PM, Pally Sandher wrote:
> You're trying to search WoW6432Node from a 32-bit process. It doesn'
ProgramFilesFolder = "Program Files (x86)" ->
http://msdn.microsoft.com/en-us/library/aa370881.aspx
ProgramFiles64Folder = "Program Files" ->
http://msdn.microsoft.com/en-us/library/aa370880.aspx
You can't write to 64-bit locations from 32-bit processes such as msiexec
running your x86 package.
omers
"if you have 32-bit app, run this setup, if you have the 64-bit app run the
other". I want to make it simple for customers, and so I want a single
setup to be able to handle all these.
On Thu, Feb 9, 2012 at 7:52 PM, Pally Sandher wrote:
> ProgramFilesFolder = "Program Fi
Paste your Product Element too as all that code depends on the Product being
set up correctly.
Palbinder Sandher
Software Platform Engineer
T: +44 (0) 141 945 8500
F: +44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limite
On Fri, Feb 10, 2012 at 3:01 PM, Pa
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland
AFAIK smoke.exe can be used to run MSI validation outside of light.exe as of
WiX v3.0 -> http://installing.blogspot.com/2006/04/msi-validation-in-wix.html
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Inno
Doesn't heat.exe harvest the registration information from the OCX? I've never
had any problems with this in WiX 2.0 using tallow.exe & in WiX 3.x using its
replacement heat.exe. As long as DLLRegisterServer is an exported function in
your OCX it should be all fine.
If not the other way I use t
Sounds suspiciously like Concurrent Installations ->
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368010.aspx which
even Microsoft warn against doing ->
http://msdn.microsoft.com/en-us/library/windows/desktop/bb204770.aspx#concurrent_installs
As Jon says, use a bootstrapper to chai
http://wix.tramontana.co.hu/
Palbinder Sandher
Software Platform Engineer
T:+44 (0) 141 945 8500
F:+44 (0) 141 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Buil
Sounds suspiciously like Concurrent Installations ->
http://msdn.microsoft.com/en-us/library/windows/desktop/aa368010.aspx which
even Microsoft warn against doing ->
http://msdn.microsoft.com/enus/library/windows/desktop/bb204770.aspx#concurrent_installs
(yes I did just copy & paste the above f
Relevant parts of my code:
http://removed/VESharedContent.msi";
ForcePerMachine="yes"
Visible="yes"
Vital="yes"
InstallCondition="SharedContentVersion < v2.0.0.0" />
http://removed/VESharedContent.msp"
I upgraded to WiX v3.6 from v3.5 earlier this week and started trying to
implement Burn as a replacement for dotnetinstaller.
So far it's pretty easy to get a chain of packages configured & I really like
how well done it is (great job everyone involved =) ).
A few of the issues I've noticed wit
1 945 8501
http://www.iesve.com
**Design, Simulate + Innovate with the **
Integrated Environmental Solutions Limited. Registered in Scotland No. SC151456
Registered Office - Helix Building, West Of Scotland Science Park, Glasgow G20
0SP
Email Disclaimer
-Original Message-----
From
2012 21:04
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] Burn feedback
On 19-Apr-12 12:34, Pally Sandher wrote:
> The bal:WixStandardBootstrapperApplication/@LicenseUrl attribute's value
> cannot be an empty string. If you want the value to be null or empty, simply
been having, I am planing to blog about what
I have found to help others. Thanks for the LicenceUrl tip, I had missed that
and ended up writing my own theme based on the HyperlinkLecense one.
Neil
Neil Sleightholm
n...@x2systems.com<mailto:n...@x2systems.com>
On 19 Apr 2012, at 17:34, Pa
ng the tasks that are defined in wix2010.targets. This didn't work for
me as my certificate is not in the certificate store.
Neil
Neil Sleightholm
n...@x2systems.com<mailto:n...@x2systems.com>
On 23 Apr 2012, at 12:48, Pally Sandher wrote:
Rob M. & others explain how to do it c
601 - 700 of 1015 matches
Mail list logo
