ideally it would
be in one component that we reuse across installs.
Any help appreciated,
--
Stefan Kuhr
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Using-the-same-exe-file-for-different-services-in-one-MSI-tp6520212p6520212.html
Sent from the
ys set this attribute to "1033" (en-US) and
never received complaints about my MSIs not installing on localized versions
of Windows.
Am I missing something or is this statement of the author just plain wrong?
--
Stefan Kuhr
--
View this message in context:
http://windows-installer-x
Hello Bob,
Bob Arnson-6 wrote:
>
> On 6/19/2010 4:06 AM, Stefan Kuhr wrote:
>> is it possible to use the DefaultVersion attribute for unversioned files?
>
> No. DefaultVersion just sets the File.Version column. See the MSI SDK
> doc for the File table for limitations.
ntain a version info resource in order to achieve version lying?
Any help appreciated,
--
Stefan Kuhr
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/How-can-I-use-DefaultVersion-for-unversioned-files-tp5198138p5198138.html
Sent from the wix-users
ucts after
InstallFinalize? E.g. installs that install services or some other sort of
unusual installs? What can break if I schedule RemoveExistingProducts after
InstallFinalize?
Any advice appreciated,
--
Stefan Kuhr
--
View this message in context:
http://windows-installer-xml-wix-toolset
Yes, sure, my application holds a lock on these files. I would expect that
MSI can deal with such a situation, because having a file open is an everday
scenario, even if this happens only for a short time. It can deal with exe
and dll files that are currently running and the files that are locked
and then scheduled to be removed during reboot from there?
Or maybe I am doing sth entirely wrong? Any help appreciated,
--
Stefan Kuhr
--
View this message in context:
http://windows-installer-xml-wix-toolset.687559.n2.nabble.com/Files-missing-after-major-update-what-am-I-doing-wrong
ario with
progress bars to run in an unattended mode and unfortunately this dialog is
killing the unattended scenario.
--
Stefan Kuhr
--
View this message in context:
http://n2.nabble.com/Prevent-%22files-in-use%22-dialog--tp3115333p3126129.html
Sent f
is
restarted).
Is what I would like to have simply not possible? Or against the design of
the restart manager and its coupling with MSI?
Any help appreciated,
--
Stefan Kuhr
--
View this message in context:
http://n2.nabble.com/Prevent-%22files-in-use%22-dialog--tp31
alogs from appearing? My app is already Vista
restart manager aware so it successfully restarts after an update, therefore
I see no reason why these dialogs should appear at all.
Am I missing something? I am using WiX version 3.0.4805 in case that
matters.
Any help appreciated,
--
Stefan K
Hi Neil,
Neil Sleightholm wrote:
>
> I documented the approach I use here:
> http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html.
>
>
Works like a charm with my projects. Thank you.
--
Stefan Kuhr
--
View this message in context:
http://n2.nabble
Hi Neil
Neil Sleightholm wrote:
>
> I documented the approach I use here:
> http://neilsleightholm.blogspot.com/2008/08/customised-uis-for-wix.html.
>
Thank you, this looks promising. I will give that a try.
--
Stefan
--
View this message in context:
http://n2.nabble.com/Is-there-a-bet
. Also, my builds take a much longer time if I have to create a
wixlib for every setup, so I really would like to get rid of these custom
wixlibs if possible.
Any help appreciated,
--
Stefan Kuhr
--
View this message in context:
http://n2.nabble.com/Is-there-a-better-way-for-custom-UI
Hi Johan,
Johan Appelgren wrote:
>
>
> That is determined by the ALLUSERS property. If it is not set you get
> a per-user installation, so I'm guessing that is what you have.
>
>
OMG, your guess was right. I normally place the ALLUSERS property in every
WiX project I create but this time I
Hi Johan,
Johan Appelgren wrote:
>
> Are you doing a per-user or a per-machine install?
>
>
Oops, please excuse my ignorance, but how do I know that? The command line
is the same as I would install as an interactive user, something like:
msiexec.exe /i path-to-my.msi /qn /l*v path-to-logf
Hi Pierson,
Pierson Lee wrote:
>
> Two questions:
> 1. If you run through interactive does it appear in ARP?
> 2. Do you have the GUIDs setup for Product Code, Upgrade code, Components,
> etc?
>
The answer to both questions is yes.
--
Stefan
--
View this message in context:
http://n2.nab
Hello everyone,
I have an MSI built with WiX. If I install this using msiexec from the
SYSTEM account, the product gets installed (files and registry keys are
there) but it is not visible in ARP. Also if I run this MSI then again from
an interactive user, I do not get the option to repair or remo
Hi Bob,
Bob Arnson-6 wrote:
>
> [...]
> You might want to try running the candle command at a console to get
> more details. CNDL1054 is a deprecation warning so the schema changed
> since the version you authored against. WixCop might convert the
> authoring for you.
>
Thanks, I didn't kn
0)Error CNDL1054: Done
building project "inotesvc.wixproj" -- FAILED.
Build FAILED.
Can anyone tell me what's wrong with my projects? What is the real reason
for my failing builds?
Thanks in advance,
--
Stefan Kuhr
--
View this
Hello everyone, I hope this question doesn't sound outright stupid:
I have a soon-to-be-released product whose binaries are all x86. But I slo
have a version of the product that is all native x64 binaries, all with the
exact same file names as the x86 build. We do not have plans for an
immediate
list with such a question?
Thanks,
--
Stefan Kuhr
--
View this message in context:
http://www.nabble.com/Next-official-v3-build--tf4696094.html#a13423576
Sent from the wix-users mailing list archive at Nabble.com.
-
T
Hello everyone,
I am currently developing our company's first install with WiX, everything
before was homegrown installers or InstallShield. My WiX-based install
distributes files that may also come with other installers for our product
and it is very, very important that the WiX-based install wi
am using v2, latest and greatest (IIRC Dec 2006, official latest release
of v2). No warnings and no errors whatsoever during build. Back to my
problem: How would you go about solving it?
Any help appreciated,
--
Stefan Kuhr
--
View this message in context:
http://www.nabble.com/Conditiona
appreciated,
--
Stefan Kuhr
--
View this message in context:
http://www.nabble.com/Conditional-start-menu-shortcut-creation-tf3041366.html#a8453976
Sent from the wix-users mailing list archive at Nabble.com.
-
Take Surveys
24 matches
Mail list logo