1. Don't do it - in the long run it will bite you.
2. Take a look at Inno Setup.
3. If you stay with WiX try using the Heat tool to create the XML, on
simple installs it does a pretty good job.
Neil
-Original Message-
From: Martin Sustrik [mailto:sust...@fastmq.com]
Sent: 03 February 200
I documented the approach I use here:
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html.
Neil
-Original Message-
From: Stefan Kuhr [mailto:kustt...@gmx.li]
Sent: 03 February 2009 18:23
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Is there a better way fo
For the desktop you can use a standard Windows Installer directory reference
(see the SDK). For quick launch the only way I have found is to use this:
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailt
I think that is only true for the MSI version, all parts of file
versions are used.
Neil
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: 29 January 2009 22:52
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Need some hel
Because I support both named and unnamed instances I have a custom
action to
copy the property from TMEDATABASESERVER and TMEDATABASEINSTANCE to
TmeDatabase correctly depending on whether TMEDATABASEINSTANCE is
specified.
That looks like:
-----Or
Do you have a simple example that you could share? I have seen this a
few times but cannot reproduce it reliably.
Neil
-Original Message-
From: jnewton [mailto:jonathan.new...@ni.com]
Sent: 28 January 2009 21:40
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Installer hanging w
hot tip, know a secret or read a really good thread that deserves
attention? E-Mail Me
--- On Wed, 1/28/09, Neil Sleightholm wrote:
> From: Neil Sleightholm
> Subject: Re: [WiX-users] extracting WiX compiled version from msi file
> To: "General discussion for Windows Installer XML
It is in the summary information but the only tool I know that displays
it is InstEd (http://www.instedit.com/). A rough way of find it is to
open the MSI in a text editor and search for "Windows Installer XML" you
should find a string like "Windows Installer XML (3.0.4923.0)". I am
sure there is a
That isn't possible, you have to add each file you want from your
project. I would do this by setting Directory/@FileSource or
DirectoryRef/@FileSource to "var.ProjectName.TargetDir" then include
each file by just setting File/@Name.
Neil
-Original Message-
From: Marais van Zyl [mailto:li
Probably not the case but SQL won't install to compressed drives and IIFC gives
a weird error.
Neil
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: 27 January 2009 15:51
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users]
You can't log if the action is based off a button click, otherwise it
should work.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, January 27, 2009 07:13
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] DTF Logging
I have at custom action written using DTF and the session.Log() method
doesn't write to the MSI log file if the custom action is called in the
UI sequence. Is this a bug or is it not possible to log in the UI
sequence?
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <
Try using NetworkService (i.e. without the space) and I
think the replaces it with the well known SID which means it is
localised. E.g.:
You may also be able to do something with OSInfo and
WIX_ACCOUNT_NETWORKSERVICE - see help file.
Neil
-Original Message-
If you need properties at uninstall time you need to persist them
somewhere and read them on uninstall, the registry is a common location
for these.
Neil
-Original Message-
From: Peter Oehlert [mailto:poehl...@securityinnovation.com]
Sent: 24 January 2009 19:58
To: 'General discussion fo
I don't think this is possible, I would suggest that the right place to do this
is in your application on first run not in the installation.
Neil
-Original Message-
From: Chuck [mailto:electroch...@att.net]
Sent: 24 January 2009 00:09
To: wix-users@lists.sourceforge.net
Subject: [WiX-us
-----
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, January 21, 2009 09:30
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a service wich is also a COM server
1. Looking at the fairly standard set of .Net and VB COM files I would
I believe products like Microsoft Office extract the MSI to a folder and leave
it on your system to allow for changes.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Andrew Lee [mailto:a...@solarfla
There is some information on customising the standard dialogs here:
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html.
I use WiXEdit to create the dialogs: http://wixedit.sourceforge.net/. It
is a bit clunky but quicker than doing it by hand.
Neil
-Original Message-
09 06:53
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Installing a service wich is also a COM server
1. there is already support for the two most common Implemented
Categories. Do you know others that need support?
2. What is "InprocServer32\1.2.3.4"?
>> Like which ones?
Implemented Categories:
HKCR\CLSID\{guid1}\Implemented Categories\{guid2}
Any entries for assemblies:
CLSID\{guid}\InprocServer32\1.2.3.4
These are generated from Heat I have to admit I don't know what they
are!
HKCR\Component Categories\{guid1}
mmended
over assemblyFileVersion. If you have issues with that (and I won't
argue against them because I probably agree with you) then don't suggest
that developers should ignore the recommendations. Work to get the
recommendations changed. That's my outlook.
-Original Mess
hing has to process it).
2. Microsoft teams doing the wrong thing.
Using the argument, "But Microsoft does it" will not always make you
right.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, January 19, 2009 23:36
To: General discussion fo
: [WiX-users] Installing a service wich is also a COM server
Why not use the specific Class, ProgId, TypeLib and Interface elements?
That's a much easier way to represent all the same registry keys.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Tuesday, Ja
I would install the service using the elements and then do the
COM bit by writing the relevant registry entries using .
The hard bit is generating the registry values as I don't think heat can
harvest COM servers, if the code is written in C++ you should be able to
get the values from the source r
Just a thought, you might was to consider a simple bootstrapper that
wraps up the msi. You could then keep the msi filename the same but
change the name of the bootstrapper exe, that way you don't break the
msi rule.
Neil
-Original Message-
From: Colin Fox [mailto:greenene...@gmail.com]
ut rarely
practical, in reality you often need to upgrade in place and policy
redirects don't help - they are only really useful for redirection
between major versions. If you take a look in the GAC I think you will
find that 90% of what Microsoft ships has different file and assembly
versions
mation. Assembly version information is mapped to file
version for your convenience and if you were so inclined you could
replace it with a completely different version. I would use
"!(bind.fileVersion.xxx)" if I were you.
Neil
Neil Sleightholm
X2 Systems Limited
n.
Add additional elements referencing the old upgrade codes.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Natarajan, Thangaraj (MLITS) [mailto:thangaraj_natara...@ml.com]
Sent: Mon 19/01/2009 07:21
T
You probably know this stuff but Bob posted some interest information
here: http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
Neil
-Original Message-
From: vexilar [mailto:s...@sorna.com]
Sent: 16 January 2009 23:56
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Conflic
I think there were a whole lot of translations provide by someone
(possible Microsoft) in the early days of the UI but they haven't been
update to include the custom actions or additions to the UI.
Neil
-Original Message-
From: Vidya Kukke [mailto:vku...@windows.microsoft.com]
Sent: 16 J
If you give it a fallback option to English it should work e.g.
cultures=ja-jp;en-us.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Vidya Kukke [mailto:vku...@windows.microsoft.com]
Sent: Thu 15/01/2
Haven't you requested to install an instance:
"/instancename=MSSQLSERVER".
Neil
-Original Message-
From: Arun Perregatturv [mailto:aperregatt...@napcosecurity.com]
Sent: 15 January 2009 17:28
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] SQL Server 20
This sounds like this problem:
http://n2.nabble.com/Installer-hanging-while-doing-FileCost,-not-frequently-though.-td2116872.html#none
Neil
-Original Message-
From: Kjartan Þór Kjartansson [mailto:kjar...@eskill.is]
Sent: 13 January 2009 12:50
To: General discussion for Windows Installe
What error do you get in the MSI log files?
Have you read this: http://www.tramontana.co.hu/wix/lesson5.php#5.12
What version of WiX are you using?
Neil
-Original Message-
From: Kalvagadda, SivaKrishna (MLX Technology)
[mailto:sivakrishna_kalvaga...@ml.com]
Sent: 12 January 2009 15:00
olset.
Subject: Re: [WiX-users] Building signed WiX Source
Yep. This need has never come up in the 4.5 years WiX has existed
externally.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, January 08, 2009 22:14
To: General discussion for Windows Installe
I think it may be co-incidence that it is installing to D:\ because
ROOTDRIVE is set by default to the drive with the most free space and
hence TARGETDIR is the same.
I do something similar like this:
I think you could also use instead of bu
I don't think you can do this in v2 but in v3 you can use
Neil
-Original Message-
From: Little Forest [mailto:little.for...@ymail.com]
Sent: 08 January 2009 22:16
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] How to detect program running and display a message
box
I'd like t
Take a look at mallow (there is v3 version here:
http://neilsleightholm.blogspot.com/2008/08/mallow-for-wix-v3.html) it
might do what you want.
Neil
-Original Message-
From: Colin Fox [mailto:greenene...@gmail.com]
Sent: 08 January 2009 23:45
To: General discussion for Windows Installer
But if you don't do official builds you can't run them on any machine
but ones that trust the public key - not something that I think is a
good idea. So, for example, if you needed a fix and it hasn't made it in
to the build you would need to build an official build.
I assume I must be alone in n
o make your own "official build" of Votive.
Thanks for the reminder Simon.
-Original Message-----
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, January 08, 2009 09:51
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building si
one
that is used is also used in an InternalsVisibleToAttribute and the
code takes advantage of this
On Thu, Jan 8, 2009 at 9:48 AM, Neil Sleightholm
wrote:
> Is it possible it only works because you are using an official
Microsoft key and that gives permissions to load something else? The
Do you mean copy the hint paths from the 2008 project? The 2005 project doesn't
have any hint paths in it.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Bob Arnson [mailto:b...@joyofsetup.com]
S
Is it possible it only works because you are using an official Microsoft key
and that gives permissions to load something else? They key I generated was
simply done with "sn -k mykey.snk" is that appropriate?
I'll raise a bug so this isn't lost.
Neil
Neil Sleightholm
005 official build. Votive is mainly handled by Justin.
-----Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, January 07, 2009 14:32
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
If I build with
09 22:18
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Building signed WiX Source
Do you have the VSIP SDK? I *think* that's what is required. There is
a fair bit of software that has to be installed when doing an official
build.
-Original Message---
ve any idea why this is happening?
Is this the correct way to generate signed code?
Thanks
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com
--
Check out the new SourceForge.net Marketplace.
It is the best
1. Take a look here:
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html
this outlines how to do it.
Neil
-Original Message-
From: Colin Fox [mailto:greenene...@gmail.com]
Sent: 07 January 2009 19:43
To: wix-users
Subject: [WiX-users] Skipping License Page and Zipping
Why not just make your msi 64 bit, that will only allow installation on 64 bit
platforms.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Andy2k8 [mailto:appr...@gmail.com]
Sent: Wed 07/01/2009 13:03
T
In general the advice is one file per component. I think Rob Mensching has some
information on this on his blog.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Maheswaran Selvaraj [mailto:maheswaran
This is a good starting point:
http://msdn.microsoft.com/en-us/library/aa370579(VS.85).aspx
Plus this: http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
Neil
-Original Message-
From: Pankaj Agrawal (Infosys Technologies Ltd)
[mailto:v-pa...@microsoft.com]
Sent: 06 January 2009 2
No answer but I have been seeing this too. I find that if you cancel the
dialog it sometimes continues but other times it just comes back. If I
cancel the install altogether it usually works ok. I am using the MSI
v4.5 and have seen it on Windows XP and Vista.
Neil
-Original Message-
From
Possibly but there people actually do installs, the people on .Net
forums still think you can xcopy deploy :-)
Neil
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: 05 January 2009 17:16
To: General discussion for Windows Installer XML toolset.
Subject: R
dered what anyone else thought.
Also, is there a way to detect that a file is an Interop file. One
possibility is that Interop files contain
TypeLb\{guid}\ver\Name="PrimaryInteropAssemblyName" - is this a reliable
method of detecting them?
Neil
Neil Sleightholm
X2 Sy
\{guid}\ver\Name="PrimaryInteropAssemblyName" - is this a reliable method
of detecting them?
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@
There is some useful information here:
http://www.joyofsetup.com/2008/12/30/paying-for-upgrades/
Neil
-Original Message-
From: Ryan Parlee [mailto:list...@jesca.com]
Sent: 04 January 2009 06:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Questions a
ng file names.
1 Short file names.
-Original Message-----
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Wednesday, December 31, 2008 00:33
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] Package/@Shortnames
Could someone let me know wha
Could someone let me know what the Package/@Shortnames attribute does or
how it maps to an MSI property. The documentation says "Set to 'yes' to
have short filenames in the source" but that doesn't really mean
anything to me.
Thanks
Neil
Neil Sleight
Take a look here:
http://www.nabble.com/Re:-Failed-to-read-IISWebSite-table.-(-2147024774-
-)-p15487354.html.
I think the bits you need are the and all
the bits (this assumes you are using WiX
v3).
Neil
-Original Message-
From: phillip_sid...@dellteam.com [mailto:phillip_sid...@delltea
I don't have a WiX solution to this but there is some information here:
http://neilsleightholm.blogspot.com/2008/08/report-loader-for-sql-server
-reporting.html. I wrote this because I don't believe the "rs" utility
does everything you need to do.
Neil
-Original Message-
From: Ajay Bhanda
t.
Subject: Re: [WiX-users] Documentation
Neil Sleightholm wrote:
> There is a bit more you need to know. First you need to compile the
> DocCompiler,
Not strictly necessary: It ships in the WiX binaries in the SDK
directory.
--
sig://boB
http:
>> I'm still trying to get the IIS team to recognize they have no
reasonable deployment story for MSI.
And I would guess you won't be able to now that they seem to be focusing
on "MS Deploy".
Neil
--
___
It looks like this is a reported bug:
http://sourceforge.net/tracker2/index.php?func=detail&aid=2318790&group_
id=105970&atid=642714
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 29 December 2008 11:00
To: wix-users@lists.sourceforge.net
S
y the output.
Note: you will probably need to install the "Microsoft HTML Help 1.4
SDK" unless you already have it, check " "C:\Program Files\HTML Help
Workshop".
Neil
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: 30 December 2008
See "Adding to the WiX Documentation" in the WiX help file. That is what
I used to work out how to add to it, I think you then need to submit a
CVS diff file to get it added to the WiX source.
Hope that helps.
Neil
-Original Message-
From: Frank Cohen [mailto:frankensp...@gmail.com]
Sen
Just to clarify, is that only true for minor upgrades? I thought major upgrades
would remove files if they are no longer in the msi.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: Bob Arnson [ma
I have seen that option before and obviously didn't read it properly as I
assumed it meant heat generated the guid (but that is the -gg option). That
will save me some work.
May be heat needs some documentation :-)
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <
2. I would suggest that the most reliable solution would be to have a
solution that set the component guid to "*". This isn't very well
documented but I believe it sets the guid to an MD5 hash of the folder
name and component name (see here:
http://installing.blogspot.com/2006/09/automatically-gene
Could someone tell be if the following is by design?
If the build doesn't find the VC8 x64 components it doesn't include any
of the Visual Studio 2005 component, i.e. BuildVC8="".
Thanks
Neil
Neil Sleightholm
X2 Systems Limite
ution file from the command line."
I have discovered that the msbuild variable "BuildingInsideVisualStudio" is not
being set. Does anyone know why this is happening? I am using 3.0.4827.0.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.
The only way I have found to set a directory to a fixed folder is to use
a custom action:
(You can ignore the condition 'INSTALLDIR=""' if you want but it allows
you to specify the value of INSTALLDIR on the command line if you need
to.)
In WiX v3 you can
only after completion of first solution build.
If I build both the solutions in separate TFS build projects or from VS
all goes well.
Thanks
Sachin
-Original Message-----
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Monday, December 22, 2008 1:45 PM
To: General discussion for Windows Ins
Are you using relative paths to your source files? IIRC TFS builds
output to a different location than a simple msbuild would and that
might be causing the problem.
Neil
-Original Message-
From: Sachin Dubey (Tata Consultancy Services)
[mailto:v-sad...@microsoft.com]
Sent: 22 December 20
5552.
-Original Message-
From: Neil Sleightholm [mailto:n...@x2systems.com]
Sent: Thursday, December 18, 2008 3:01 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] WebSite is getting deleted when msi
uninstalled.
Instead of creating the website you
interface.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.com>
From: daft [mailto:daveb...@gmail.com]
Sent: Thu 18/12/2008 15:50
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users] On registering DLLs
S
Instead of creating the website you just need a reference to an existing one.
I think this has to go outside of a element. You can then reference
this in your element.
Neil
Neil Sleightholm
X2 Systems Limited
n...@x2systems.com <mailto:n...@x2systems.
I'm not sure what the problem is but take a look here:
http://neilsleightholm.blogspot.com/2008/10/how-to-create-wix-build-mach
ine.html I have documented some of the problems I had build WiX. If you
spot anything missing please let me know.
Neil
-Original Message-
From: Sean Farrow [mail
Take a look here
http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html I think
I have covered what you want to do.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: Dmitry Berkovich [
I think you click on the +'s to navigate to the zip files.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: Sean Farrow [mailto:[EMAIL PROTECTED]
Sent: Wed 10/12/2008 07:22
To: wix-users@lists.sour
Don't get me wrong I totally understand, I was just trying to understand how
the process worked.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: Fri 05/12
Legal stuff != productivity :-)
Two repositories would explain the delay between code fixes and them appearing
in CVS. It would be nice to get to see changes earlier but I guess you have
enough to do without adding to it.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mai
next release or sometimes after the release.
I assume this is because the CVS source is not the main repository but a
clone of it. Would it be possible to either update CVS as changes are
made or make CVS the master?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROT
In my experience most tools (Orca, InstEd) don't show the CAB file when it is
embedded.
Neil
-Original Message-
From: siri a [mailto:[EMAIL PROTECTED]
Sent: 03 December 2008 21:50
To: WIX USERS
Subject: Re: [WiX-users] Urgent!! Cab files not getting embedded into MSI file
Thankyou for
I have finally figure out how to fix this, the condition should be as
follows:
This seems to work for me YMMV.
Neil
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: 14 November 2008 09:40
To: General discussion for Windows Installer XML
be bad, I think they forgot
about the case where torch is used standalone. I'll follow up this
week.
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 23:13
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-
n for Windows Installer XML toolset.
Subject: Re: [WiX-users] Install Localisation
Neil Sleightholm wrote:
> 2. Every time I run light it will create a new product code but I
don't
> want that, I want one product code and simply install with a different
> UI language. From what I have
users] Install Localisation
Most people that are attempting to do what you are doing, care about
their ProductCodes so they can tightly manage upgrades in the future.
-Original Message-
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 14:33
To: General discussio
ating transforms
is complete supported. You'll need something to apply the transforms at
run time, presumably.
The bugs in the WiX toolset are being fixed, BTW.
-Original Message-----
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, December 01, 2008 13:59
To: General disc
ou.
Also, Peter was talking about issues with torch and .wixouts but I don't
remember them right now.
It's been a long while since I did all the above so YMMV and please feel
free to correct me where I'm wrong. It might be a bug.
-Original Message-
From: Neil Sleightholm
it is always binding the files into
wixout not just when -bf is used. Does this sound like a bug?
Thanks for your help
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
-Original Message-
From: Rob Mensching [mailto:[EMAIL PROTECTED]
Sent: 06 November 2008 22:31
To: Ge
I did reply before but may be it got lost:
"It was working from msbuild and the command line but failing in VS. Now
the problem has gone away! The only difference was that I had changed
the source rather than rebuilding existing source. I can't reproduce it
again."
Neil
Neil
That is a bit odd environment variables are not case sensitive, cd
"%wix%" is the same as cd "%WIX%". Is it possible you already had the
command prompt open then ran the WiX install, if so the environment
variable wouldn't have been set until you reopened the command prompt.
Neil
-Original Me
>> Be careful when using cd , if you are on drive X:\bin, and
you do
>> cd c:\Temp, the current folder for C: will be Temp, but your current
folder
>> will be still X:\bin - in other words, cd does not change drives :^)
Use cd /d "folder" change drives.
Neil
Neil Sl
ndows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch: remove #
In article <[EMAIL PROTECTED]>,
"Neil Sleightholm" <[EMAIL PROTECTED]> writes:
> Actually it is much simpler than that, I want to read the SQL port
> number from the registry and then
discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] RegistrySearch: remove #
In article <[EMAIL PROTECTED]>,
"Neil Sleightholm" <[EMAIL PROTECTED]> writes:
> It there anyway to remove the hash (#) from the start of a
> RegistrySearch if the val
It there anyway to remove the hash (#) from the start of a
RegistrySearch if the value is a DWORD?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED]
-
This SF.Net email is sponsored by the Moblin Your Move
Using the start group is probably failing on Vista because your problem is
requesting to be run elevated. I think you will have the same problem even if
you use the Run key.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTEC
This is probably not relevant but if you don't have access to SQL how do you
expect any solution to work?
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: Eitan Behar [mailto:[EMAIL PROTECTED]
Sent
There is an alternative approach here
http://neilsleightholm.blogspot.com/2008/08/executing-sqlcmd-from-wix.html that
might be useful.
Neil
Neil Sleightholm
X2 Systems Limited
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
From: Eitan Behar [mailto:
this is a regression from trying to get all those
other .wxl bugs fixed in .wixlibs that we addressed a couple months ago.
-Original Message-----
From: Neil Sleightholm [mailto:[EMAIL PROTECTED]
Sent: Monday, November 17, 2008 23:36
To: General discussion for Windows Installer XML toolset.
Subject
Not directly, but if you use v2 tallow to generate the wxs you can then
use v3 wixcop to update it.
Neil
-Original Message-
From: Yu, Brian [mailto:[EMAIL PROTECTED]
Sent: 18 November 2008 09:45
To: General discussion for Windows Installer XML toolset.
Subject: [WiX-users] how to convert
901 - 1000 of 1316 matches
Mail list logo
