Hello,
I have a product which I've already delivered. The RTM setup of this
product was built with WIX 3.0.3210.0 and contains some directories
which unfortunatelly have the ID longer than 72 characters (they came
from a MSM and because of the MSM's GUID suffix they got longer than
72 - WIX had
1. Putting the WebSite under a Component causes the WebSite's lifetime
(install/uninstall) to be controlled by that Component.
2. The WebSite needs a Directory attribute provided when it is going to
be installed/uninstalled.
3. A WebSite element cannot be the child of a Directory element. If
More specifically, signing is a build task (think MSBuild or NAnt) not a
build setup task (aka: WiX).
Bob Arnson wrote:
Craig Miller wrote:
Is there an easy way to digitally sign the msi w/ the WIX toolkit or should
I use signtool by hand?
WiX doesn't sign.
One thing I remember the MSI team mentioning was that certain system
dialogs the Windows Installer puts up will show up with boxes because
the Windows Installer does not understand the UTF-8 codepage. Basic UI
maybe... I forget the specific dialogs (if they even said)?
Tony Hoyle wrote:
DEXK
Can you provide more details about these crashes? There should be a
stack dump with lots of information.
Calin Iaru wrote:
Some links are down like the download links. Sometimes the browser
won't even open WiX.sourceforge.net. What is wrong? I could not
download WiX 2 nor could I take any
Try putting the Certificate element in a permanent Component.
Lin wrote:
Hi,
I am new to Wix so I hope this is the correct mailing list for such
questions.
I am using Wix3. I would like to associate a certificate with a IIS
website. The certificate already exists in machine store, so I
That should be a safe set of characters. I haven't pushed it myself.
md5hans wrote:
Hi!
Which chars are allowed (or not allowed) when defining the cabinet name for
the Media element, is it the same as for a DOS file name?
Regards Hans
Thanks for these notes. Moving to CLR v2.0 was an interesting struggle
and I don't think we have all of our build dependencies worked out. The
AssemblyInfo.cs is totally one of those files that I've messed up. I've
been struggling with the freaking keys for a while (keeping the private
What is the value for your PORT property during uninstall?
Meyrignac, Jean-Charles wrote:
I have a weird bug while uninstalling a website on Windows XP, using
the MSI installer: when the application is uninstalled, *IIS is
completely* *broken*.
Here is the part installing my web site:
Groups cannot be created with the existing set of Custom Actions. More
code needs writing.
Krishna Kishore B wrote:
How can I add a User Group in Windows 2003 using WIX
Regards
Krishna
Don't hold your breath. sigh/
Tony Hoyle wrote:
DEXK JAHN, GXbor wrote:
Windows Installer still doesn't handle Unicode--I can't simply
understand how the developers got away with this :-)) So, it's not a
WiX limitation...
Maybe MSI 4 wil fix it.. we can only hope.
Tony
Latest build of WiX v3 has support for Event manifests in Vista.
Bob Arnson wrote:
Jared Hughes wrote:
Currently my product is running a custom action of wevtutil.exe im
[manifest_filename] to install an event manifest and create logging
channels with the Windows event logging system,
Do you have a bug number that explains this in more detail? I'm not
sure what the wiki is referring to.
Quattro IV wrote:
Hello, the wix wiki regarding the SQLExtension mentions There is a
serious bug with how the *SqlExtension* handles the SqlDatabase
Element
Rob Mensching wrote:
One thing I remember the MSI team mentioning was that certain system
dialogs the Windows Installer puts up will show up with boxes because
the Windows Installer does not understand the UTF-8 codepage. Basic UI
maybe... I forget the specific dialogs (if they even said)?
To add to Rob's extremely terse answer ;) the IIS custom actions use the IP
address/port/Host header tuple to discover the internal website ID for the
site. Unfortunately there's no special place to store in the metabase that
the website/virtual directory was installed by WiX - not even a field
Cristian Baiu wrote:
Obivously, I will need to cut shorter this directory ids in order to
be able to build my upgrade setup. The question is : will this affect
the patch (I will have the same components in the RTM and upgrade
setups but with different parents in the Directory tables) ?
Bryan C. Boettcher wrote:
Well, it sort of helped. I got rid of about 7 errors, and I'm now left with
the following 8:
ICE03: Table: MIME Column: ContentType Missing specifications in _Validation
Table (or Old Database)
ICE03: Table: MIME Column: Extension_ Missing specifications in
Hello
I have WiX files that deploys features based on conditions. However I am having
trouble creating a patch (msp) for this WiX file, especially for files that are
deployed by conditional statements.
I am following the recommended process for creating msp.
1. Candle patch.wxs for
Sneha Gharpure wrote:
Is there any way to find out the temporary location?
No, it's done on demand only. Custom actions should have no dependencies
on where they're running from, taking everything they need from the
registry or command-line arguments.
--
sig://boB
http://joyofsetup.com/
Levon Levonian wrote:
Will this require defining in my XML code complete UI of every standard
dialog? Ideally, I just want to reference the needed label and change
its font color. I am using the standard Install_Dir type of UI, with no
actual UI code in my XML.
Using WixUI, you can
Rob Mensching wrote:
That should be a safe set of characters. I haven't pushed it myself.
md5hans wrote:
Hi!
Which chars are allowed (or not allowed) when defining the cabinet name for
the Media element, is it the same as for a DOS file name?
The Cabinet topic in the SDK is
Doug Payne wrote:
My application installs for ALLUSERS (ALLUSERS=1). I want to crate a
start menu shortcut which points to the product's root installation
folder. This implies that I want a non-advertised shortcut, since an
advertised shortcut points to the product feature, and launches the
Marc b wrote:
Error LGHT0204: ICE38: Component Dirs installs to user profile. It must use
a registry key under HKCU as its KeyPath, not a file.
Error LGHT0204: ICE43: Component MainExe has non-advertised shortcuts. It
should use a registry key under HKCU as its KeyPath, not a file.
Error
This is perfect thanks
Bob Arnson-6 wrote:
Marc b wrote:
Error LGHT0204: ICE38: Component Dirs installs to user profile. It must
use
a registry key under HKCU as its KeyPath, not a file.
Error LGHT0204: ICE43: Component MainExe has non-advertised shortcuts. It
should use a registry
Thanks, putting the Certificate element in a permanent Component prevented the
certificate from being uninstalled.
While the above solution works, I am curious to know if Wix allows the ability
to only associate certificates with websites without actually installing the
cert?
Thanks,
Dakun
Hi Bob,
Most probably I will not have to patch the files in those directories
because they are not binaries.
But just in case : could you please detail the problems I might have if I
patch those files ? (if I will ever get a request to patch them it would be
good for me to know what problems
26 matches
Mail list logo
