ne’
> and ‘Administrators’ may be entered in English and are mapped to
> well-known SIDs.” Or there will be localization problems when
> installed in other languages?
>
> Do you have some recommendations?
>
> Thanks a lot for your time.
>
>
>
> 2013/5/22 BGINFO4X :
>
I agree with John - please avoid setting the arpsystemcomponent. It's
extremely annoying to install something and be unable to uninstall it from
the UI, and is really only meant for system components that make no sense
to uninstall.
I suggest you author a burn bundle to hide all the individual MSI
When you say "another package", I assume you mean another MSI?
Make sure the component GUIDs in your MSI match the component GUIDs in the
other MSI so you don't break the component rules, and then for any of the
files that have file versions (such as .exe or .dll files), make sure your
version num
Chain all the MSI files you want to install with a burn bundle. It will by
default not show each MSI it installs in add/remove programs (ARP), instead
you will still see a single entry in ARP for the bundle itself.
Note if you do want some of your MSI's to show up individually in ARP, you
can make
d version to be uninstalled as part of installing the
new version.
Or you might want to explore "Minor Upgrades" which are slightly lighter
weight:
http://msdn.microsoft.com/en-us/library/windows/desktop/aa370037(v=vs.85).aspx
.
On Tue, May 21, 2013 at 9:34 AM, BGINFO4X wrote:
You should be able to. Create the shortcut in your own authoring file. To
point to the file in the generated authoring, see the "Target" attribute of
the shortcut element in wix.chm.
On Tue, May 21, 2013 at 4:37 AM, BGINFO4X wrote:
> > You should change it to this:
> >
> >
> >
I don't know the direct answer to your question, but taking a step back,
have you considered any alternatives instead of adding a custom action?
Custom actions are notoriously difficult to write correctly, and very, very
easy to get wrong. A custom action that invokes an external process (such
as j
Your problem is that "basedir" isn't a child of "INSTALLDIR", it's a child
of "ProgramFilesFolder". Here is your current code:
You should change it to this:
Also, you should pass in "-srd" on the heat commandline (suggestion #3
above), or e
The problem you're running into is that the generated components are by
default generated under a directory under "TARGETDIR", not "INSTALLDIR". To
override this:
1) Add (for example) "-dr foo" to your heat commandline to generate them
under a directory of ID "foo"
2) In your main authoring file,
xist when something needed
it.
That solution probably doesn't fit your situation, so another solution is if
you don't want the app pool to be removed on uninstall, put it in its own
component and make the component "Permanent".
Thanks,
Mike Carlson
-Original Message
figuration file. The two Web.config files are both for IIS7. I'll check.
--
John M. Cooper
Volt at Microsoft
-Original Message-
From: Mike Carlson (DEV DIV) [mailto:mica...@microsoft.com]
Sent: Thursday, May 06, 2010 2:15 PM
To: General discussion for Windows Installer XML toolse
what error code.
Another possibility - is it possible the permissions on a parent directory of
this file are extremely restrictive?
Thanks,
Mike Carlson
-Original Message-
From: John Cooper (Volt) [mailto:a-jc...@microsoft.com]
Sent: Thursday, May 06, 2010 12:02 PM
To: General discuss
Yes, we still use nant/wix.build, and "make.bat" should work.
I don't have direct experience with the wix CVS repository, but I would think
it's best to begin building from cvs. If there is a problem, certainly it's
something we will want to fix.
-Original Message-
From: Neil Sleighthol
Just saw your later reply with the solution to your own problem; sorry for the
spam everyone.
Threads on this alias aren't well-organized in my mail viewer, and I often
forget to manually check if there is a later reply to a thread, before replying
myself...
Thanks,
Mike Ca
The VerQueryValueW() call has been there since WiX 3.5 forked from WiX 3.0, so
I don't think this problem is necessarily Unicode-related. Perhaps you only
recently started using FileUtil's FileVersion() function (which requires
"version.lib" to be linked in)?
Try adding "version.lib" to the lis
Please file a bug for this, if you haven't already.
Thanks,
Mike Carlson
-Original Message-
From: Navid Azimi-Garakani [mailto:naz...@microsoft.com]
Sent: Monday, April 19, 2010 4:14 PM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] 64-bit WiX
T
ignia, and it will update your MSI
appropriately, according to the way you signed your cabs.
If you use MSBuild, this integrates well with MSBuild as well - see the WiX 3.5
CHM page on "Insignia" for instructions to use insignia with MSBuild.
Thanks,
Mike Carlson
-Orig
tool called "Insignia" to make this
process easier - see wix.chm for more information about Insignia in WiX 3.5.
Thanks,
Mike Carlson
-Original Message-
From: Christof Schmutz [mailto:christof.schm...@cstsoft.de]
Sent: Tuesday, April 13, 2010 11:07 AM
To: General discussion for Win
nd I made it to
be executed after ConfigureIIs (in Wix 3.5 I changed to be after
ConfigureIIs7), but from log file I can see that website was not created
after ConfigureIIs7 action. Can you please specify name after which IIS
action I should execute mine custom action?
-Original Mess
Also, what version of the tools are you running? Have you tried "3.0 RTM" or a
recent 3.5 weekly release?
-Original Message-
From: s...@pacaccess.com [mailto:s...@pacaccess.com]
Sent: Wednesday, March 31, 2010 10:26 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re
s before about the same thing:
http://sourceforge.net/tracker/?func=detail&aid=2961215&group_id=105970&;
atid=642714
Is it the same as yours?
And Mike already fixed it in the latest Wix build which should be
available today.
-Original Message-
From: Mike Carlson (DEV DIV) [mailto:m
I'd file a bug with the authoring you pasted below, and the answers to these
questions, if possible:
What's the exact error message you get (use a verbose logfile to find out)?
Does it work correctly if you install to an IIS6 machine?
Thanks,
Mike Carlson
-Original Message-
It shouldn't be giving this message, but have you tried building the project? I
ask because it could be a secondary file (like the primary output) that heat is
trying to open (and is causing the exception to occur).
-Original Message-
From: Bill McCormick (LIST) [mailto:wpmccorm...@ace-c
The recommended way now is typically to run heat.exe to "harvest" the com
registration information out of your DLL. This way it won't actually run the
code from the DLL at install-time (which is more likely to fail, won't handle
all of MSI's transactionality appropriately, and is generally a non
I just realized this was already replied to. Apologies for the spam, everyone.
-Original Message-
From: Mike Carlson (DEV DIV)
Sent: Monday, March 22, 2010 11:26 AM
To: wix-users@lists.sourceforge.net
Subject: RE: [WiX-users] (no subject)
The problem you're running into is that i
The problem you're running into is that in the MSI world, "[PropertyName]" is
used to dynamically (at install-time) pull in the value of a property. So, you
need to escape your bracket so it isn't looked at in that way.
To escape "[" replace it with "[\[]"
To escape "]" replace it with "[\]]"
T
DirProperties is part of IIS, etc. Then during both compile and link, you
need to reference the right extension too when compiling, like:
Candle -ext wixutilextension file.wxs
Light -ext wixutilextension file.wixobj
Hopefully you get the idea.
Thanks,
Mike Carlson
-Origin
om: Navid Azimi-Garakani
Sent: Monday, March 15, 2010 8:34 PM
To: General discussion for Windows Installer XML toolset.
Cc: Mike Carlson (DEV DIV)
Subject: RE: WIX 2.0 on IIS 7.5 with IIS 6.0 Compatiblity Mode
I should mention that that errors are primarily trivial with the exception of
the followin
't require the IIS6 compatibility layer (but 3.5 is still under
development, so expect some bugs if you try 3.5).
Thanks,
Mike Carlson
-Original Message-
From: Navid Azimi-Garakani [mailto:naz...@microsoft.com]
Sent: Monday, March 15, 2010 2:29 PM
To: wix-users@lists.sourceforge.ne
I can't help with the CVS issues, but to download the latest official build of
3.5, you want the "weekly releases" page, linked from wix.sf.net.
The direct link to weekly releases page is here:
http://wix.sourceforge.net/releases/
Thanks,
Mike Carlson
-Original Message-
You need to use a bootstrapper (an EXE designed for running one or more
installation packages) that will pass the appropriate language property to the
MSI at install-time.
WiX 3.5 will have a bootstrapper called Burn, but it's still under development
right now.
Thanks,
Mike Ca
I believe you want to list these properties as the value of the built-in
"SecureCustomProperties" property, so they will be set in the server context as
well.
Try adding something like this to your authoring:
Thanks,
Mike Carlson
-Original Message-
checks
for the cancel between each file.
- Original Message -
From: Mike Carlson (DEV DIV)
To: General discussion for Windows Installer XML toolset.
Sent: Tue Feb 09 17:23:12 2010
Subject: Re: [WiX-users] Interrupting a WiX build
Do the cancel build (etc.) buttons work?
If you'
Do the cancel build (etc.) buttons work?
If you're sure the regular "cancel build" options that work for C++ / C# builds
aren't working for wix (either the options aren't visible, or the options are
visible but don't function as you feel they should), go ahead and file a bug
against WiX 3.5 / V
ow to reproduce the problem
as you can in the bug, and the log excerpts you've already provided in this
e-mail are perfect; make sure to include those in your bug reports too.
Thanks,
Mike Carlson
-Original Message-
From: Matteo Canessa [mailto:matteo.cane...@microarea.it]
Sent: Frida
as much
repro information as you can.
Thanks,
Mike Carlson
-Original Message-
From: Matteo Canessa [mailto:matteo.cane...@microarea.it]
Sent: Thursday, January 28, 2010 6:53 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Creation of an application pool on IIS7 install
that
solves the problem?
If it doesn't solve the problem, file a bug on sourceforge against v3.5, attach
a repro (make sure to exclude any sensitive things from your authoring, if
there are any), and attach a verbose MSI log of the install which didn't seem
to work.
Thanks,
Mi
esign is that users should only write
declarative authoring to represent the things they want installed, and let the
installation engine (and/or the built-in wix custom actions) handle the actual
installation for you.
Thanks,
Mike Carlson
-Original Message-
From: phillip_sid...@delltea
Look closely; some of the link was cut off and placed in the next line, and
this portion was excluded from the hyperlink. If you include the "ine.html"
from the next line in the part that's hyperlinked, the link works for me.
-Original Message-
From: Jahanzeb Khan [mailto:jk...@commondes
It sounds to me like a bug. Please file one - don't forget to copy all the
helpful information (version information, sample authoring + log failure
messages) from your mail into the bug.
Thanks,
Mike Carlson
-Original Message-
From: Duncan Kelbie [mailto:duncan.kel...@neural
en let it be a cab external to the MSI (set
Media/@EmbedCab to no) instead of embedded in the MSI, and wix shouldn't have
to do anything with it if it hasn't changed.
Thanks,
Mike Carlson
-Original Message-
From: Kim Gybels [mailto:kim.gyb...@metris.com]
Sent: Wednesda
-
Von: Blair [mailto:os...@live.com]
Gesendet: Montag, 2. November 2009 23:00
An: 'General discussion for Windows Installer XML toolset.'
Betreff: Re: [WiX-users] Link error for dutil.lib
Are you building 32-bit, or some flavor of 64-bit?
-Original Message-
From: Mike Carlson (DEV DIV
Did you try a clean build? i.e. Delete your build output directory and build
again.
Thanks,
Mike Carlson
-Original Message-
From: Jiang, Chunyan (GE Healthcare) [mailto:chunyan.ji...@ge.com]
Sent: Monday, November 02, 2009 7:20 AM
To: General discussion for Windows Installer XML
you referring to a
repair scenario, or "uninstall" then "install"? Also, if you have a repro
sample (with logs) using a dummy cert, that will help the investigation.
Thanks,
Mike Carlson
-Original Message-
From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellte
erver.
AddMachineCertificate: Error 0x80092004: Could not locate key pair from
PFX file.
AddMachineCertificate: Error 0x80092004: Failed to install certificate.
AddMachineCertificate: Error 0x80092004: Failed to install per-machine
certificate.
- Phil
-Original Message-
From: Mike Carlson (DE
1) What version of WiX are you using?
2) What error message do you see in a verbose logfile in the event of failure?
3) Have you tried making the associated Component Permanent?
Thanks,
Mike Carlson
-Original Message-
From: phillip_sid...@dellteam.com [mailto:phillip_sid...@dellteam.com
e to do things
like this yourself.
Anyway, to answer your original question, try escaping them like this:
"[\[]" (without quotes) for the open square bracket.
"[\]]" (without quotes) for the ending square bracket.
I believe this is the standard MSI way to e
\wix\compiler.cs and search for
"currentplatform". Once you get past the initial few results (which are just
common infrastructure), you'll see where it actually takes effect.
Thanks,
Mike Carlson
-Original Message-
From: Quinton Tormanen [mailto:quint...@deltacompsys.com]
Se
I am able to reproduce your failure - I haven't investigated in detail yet, but
it could be a bug. Go ahead and file a bug on SF against WiX 3.5, and attach
your repro authoring to the bug.
Thanks,
Mike Carlson
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
apped
in a component.
Please, let me know if the snippet above doesn't contain what you were
asking for.
NOTE: it is reproduced when I'm creating a new site. If a user chooses
to use existent site, everything goes fine.
Thank you!
-- Yan
-Original Message-
From: Mike Carlson (D
locator record,
but the web locator couldn't find what it was looking for on the local machine.
Thanks,
Mike Carlson
-Original Message-
From: Yan Sklyarenko [mailto:y...@sitecore.net]
Sent: Tuesday, September 01, 2009 7:25 AM
To: General discussion for Windows Installer XML toolset.
Su
If you're using the visual studio UI for WiX (called Votive), you'll want to
add a reference to WixIISExtension.dll, similar to the way you add references
to assemblies in your C# projects.
If you want general commandline help for the tools, either see the helpfile
(wix.chm), or try running the
erence,
and sounds like a bug - go ahead and file a bug on SF against 3.5.
Thanks,
Mike Carlson
-Original Message-
From: kevin_mitch...@agilent.com [mailto:kevin_mitch...@agilent.com]
Sent: Tuesday, August 04, 2009 7:54 AM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Using Wi
Did you specify the correct Certificate/@PFXPassword attribute?
Also, what build of WiX are you using? It's highly recommended to use WiX 3.0
RTM, as at least a few cert bugs existed in earlier 3.0 builds that were fixed
in RTM.
Thanks,
Mike Carlson
-Original Message-
From:
It contains some of the WiX custom actions that, at install-time, do the work
for most of the elements of the WixUtilExtension.
Many of the other extensions have their own custom action DLLs.
-Original Message-
From: Sunkesula, Srivardhan [mailto:srivardhan.sunkes...@netapp.com]
Sent: Su
ine.
What version of the toolset are you using? Have you checked if the XML file
it's trying to modify exists, etc.?
Thanks,
Mike Carlson
-Original Message-
From: Castro, Edwin G. (Hillsboro) [mailto:edwin.cas...@fiserv.com]
Sent: Wednesday, July 29, 2009 4:17 PM
To: General discus
According to wix.chm, File isn't a valid parent element for
util:PerformanceCounter. It needs to be under a Util:PerformanceCategory
element, which in turn needs to be under a Component element, not a File.
See the CHM for more information.
Thanks,
Mike Carlson
-Original Message-
I would link the .wixobj into your final output, then use dark and see what you
get.
The formatting will be completely different, but depending on how extensive
your changes were, if you remember what you changed, you should be able to find
the things you added or modified, copy them back to th
mmend it at this point in time.
Thanks,
Mike Carlson
-Original Message-
From: Don Benson [mailto:dbenso...@gmail.com]
Sent: Monday, July 13, 2009 11:53 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] Updating web.config field value depending on if
mac
I think a bug is already filed for this (#2803058):
http://sourceforge.net/tracker/?func=detail&aid=2803058&group_id=105970&atid=642714
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Thursday, July 09, 2009 6:26 PM
To: General discussion for Windows Installer XML
Were you by chance using Visual Studio 2010? Votive2010 was inadvertently
removed for a few builds, but the issue has since been fixed, and votive2010
should be back in the MSI with the latest 3.5 build (3.5.0704.0).
Thanks,
Mike Carlson
-Original Message-
From: Rob Mensching [mailto:r
Make sure the IP, Port and Header all exactly match the website on the machine.
These are the 3 things we use to determine if we've found the right website or
not.
Thanks,
Mike Carlson
-Original Message-
From: troy hostetter [mailto:troy.hostet...@gmail.com]
Sent: Wednesday, Ju
d to fail).
If you want the website to be created if it doesn't exist, the website must be
associated with a component.
Thanks,
Mike Carlson
-Original Message-
From: troy hostetter [mailto:troy.hostet...@gmail.com]
Sent: Wednesday, July 01, 2009 11:54 AM
To: General discussion f
A *lot* has changed in the IIS custom actions since WiX v3.0.4805, including an
error that looks very similar to this. First, I would upgrade to the latest WiX
3.0 build (v3.0.5419) and see if you still have a problem after that.
Thanks,
Mike Carlson
-Original Message-
From: troy
arios through the Wow64 API.
Thanks,
Mike Carlson
-Original Message-
From: John Robbins [mailto:j...@wintellect.com]
Sent: Tuesday, June 30, 2009 10:04 AM
To: General discussion for Windows Installer XML toolset.
Subject: Re: [WiX-users] wix3_x64.msi
Doh! Yes, the CA's have x64 ve
r consistent with it failing to find the
website it should install to.
Try either: A) putting your website element inside of a component (so that the
website will be created if it doesn't exist), or B) making sure the website
it's searching for exists on the target machine before insta
Bob raises a good point. Actually, this is an even better reason to split your
files up close-to-evenly into a few cabs.
-Original Message-
From: Bob Arnson [mailto:b...@joyofsetup.com]
Sent: Monday, May 11, 2009 6:57 PM
To: General discussion for Windows Installer XML toolset.
Subject:
y, then I don't believe there is
an automated way to do (unless you create your own program).
Thanks,
Mike Carlson
-Original Message-
From: Mahmoud Hamad [mailto:m.n.ha...@hotmail.com]
Sent: Monday, May 11, 2009 3:41 PM
To: wix-users@lists.sourceforge.net
Subject: Re: [WiX-users
An XmlFile entry will only get passed to ExecXmlFile if the component
associated with it is being installed or uninstalled.
Is the component associated with it being installed (or uninstalled)?
Thanks,
Mike Carlson
-Original Message-
From: Amy Rosewater [mailto:arosewa
o multiple CABs noticeably quickens your build time, you may
be running into this issue.
Thanks,
Mike Carlson
-Original Message-
From: Mahmoud Hamad [mailto:m.n.ha...@hotmail.com]
Sent: Monday, May 11, 2009 2:31 PM
To: wix-users@lists.sourceforge.net
Subject: [WiX-users] Make light.exe run
r the "voicewarmup" regkey you need to set), and
re-run the install. Writemetabasechanges should display more information in the
log, which will help to diagnose the issue.
3) What OS are you installing the MSI on? This too can help diagnose the issue.
Thanks,
Mike Carlson
-O
file a bug. Try to attach a minimal repro
to the bug (authoring & a logfile), as this will help me to reproduce the exact
problem.
Thanks,
Mike Carlson
-Original Message-
From: Gang Cheng [mailto:gang.cheng...@gmail.com]
Sent: Friday, April 03, 2009 6:04 PM
To: wix-users@lists.s
hould display any warnings / errors specific to
the IIS's deferred custom action.
Finally, what version of WiX are you using? Quite a lot of things have been
fixed in the IIS custom action in just the past couple of months - you may want
to try again with the latest weekly build to see if the pro
e using both IIS and Util
extensions, and you've associated one or more of your IIS elements with a User.
Thanks,
Mike Carlson
-Original Message-
From: Rob Mensching [mailto:rob.mensch...@microsoft.com]
Sent: Wednesday, January 14, 2009 9:18 AM
To: General discussion for Windows Inst
74 matches
Mail list logo
