Recent changes to examples

#32 WixLocalization/UI element not taking effect when not in first -loc files per culture

2013-06-07T19:47:14Z

Err, Somehow I cross posted intending to raise a bug instead an example, not sure how to fix it.

WixLocalization/UI element not taking effect when not in first -loc files per culture

2013-06-07T19:20:34Z

The WixLocalization/UI element is not being activated if it is not present in the first file linked into a wixlib with -loc for each specific culture.

I haven't tested the same with specifying the -loc more directly in the same project.

As the content for each file is not otherwise allowed to overlap for fragment content,
it is desirable that the UI elements be treated equally to strings to be located in any wxl file, or at least merge or report the value being lost.

It might also help when using 'backup' -culture like de-DE,en-US to provide the Overidable flag similar to String.

Background - why it was noticable

The OptionalCheckBox on the ExitDialog is not transparent, so it looks a bit ugly when you have a different background colour to windows default dialog colour.

Trying to move the Checkbox over the banner bar (our preferred location) rather than copying the dialog and customizing it.

We have seperated our localization files within each culture to split UI from Product/Patch from features.

Feature.wxl
Product.wxl
UI.wxl

We started with having this UI element in the UI.wxl, however it wasn't being used.
tried to drop it into all, and it started working (with no compile complain on the duplication)

Eventually identified that the one in Feature.wxl was being used.
Then found adding a new file earlier in File alphabetic order in Votive project caused it to break again, indicating something to do with file order.

Building with seperate build script where the additional files where just added at the end produced a different build order and so the 2 builds where inconstant.

#8 Automate Version in Project

2013-06-03T08:37:27Z

I miss the definition line (dropped?) in my post ..

<?define ProductVersion ="!(bind.FileVersion.sample.exe)"?>

#8 Automate Version in Project

2013-06-03T08:35:03Z

IF you update the verion in every build you can do this:

Use the UtilExtension and insert

<Product Id="*"
    Name="$(var.ProductName) $(var.ProductVersion)"
    Manufacturer="$(var.CompanyName)"
    Version="$(var.ProductVersion)"
    Language="!(loc.LANG)"
    UpgradeCode="$(var.UpgradeCode)">

etc..

#31 framework version 4.5

2013-05-12T11:30:17Z

I need to know please how to check that framework 4.5 is installed.
There is no documentary in the framework properties for this version

framework version 4.5

2013-05-12T11:26:42Z

How to check the framework version 4.5?

#30 expected values for ManagedRuntimeVersion & ManagedPipelineMode

2013-05-12T11:24:15Z

I'll highly appreciate a sample

expected values for ManagedRuntimeVersion & ManagedPipelineMode

2013-05-12T11:21:23Z

I try to create wix toolset xml files to automate MSI creation.
In the WebAppPool documentry there are two Properties -
ManagedRuntimeVersion
ManagedPipelineMode
What are the expected values for them?
It mentioned that they can be set using formatted Property. What are these properties?

Trying to use WiX to install documentation in new directory structure

2013-02-07T07:46:11Z

Hi,

I'm new at this, to searched the WiX Toolset homepage for a solution on creating new folders, and copying some documentation into the bottom level ones.

The install procedure work fine, but the folders I want to create, isn't created as expected.

I found your WiX Tutorial – Creating directories, and tried implementing this into my wxs file.

Does it matter whether I create this as an X86 or X64 msi file?

Hope you have that small hint, that will make everything fall into place 

Mvh./Rgds.
Allan Lillebæk

TEST

        <DirectoryRef Id="DOCSDIR">
            <Component Id="Docs" Guid="8592d02e-ba89-4c6b-96f4-2786e01765bf">
                <CreateFolder />
                <File Id="HELPTOC" Name="TableOfContents.xml" DiskId="1" Source="TableOfContents.xml" KeyPath="yes" />
            </Component>
        </DirectoryRef>

        <Feature Id="Complete" Title="Test Help Content" Description="Test help description " Display="expand" Level="1" ConfigurableDirectory="DOCSDIR">
            <Feature Id="MainDocumentationSet" Title="Test documentation" Description="The set of test documentation." Level="0">
                <ComponentRef Id="Docs" />
            </Feature>
        </Feature>

I expected this to create the folder “Test folder” below my C:\Program files (x86) folder, and that’s what the installer screen shows.
When I click Install, my product is registered in Windows, but the folder isn’t created, and my TableOfContents.xml document isn't installed either.
This was for testing, because what I actually wanted, was to create several folders below each other like this:

ACTUAL NEED

<=== This folder and above exists prior to running the install program

        <DirectoryRef Id="SOLDIR">
            <Component Id="SOLDIR" Guid="3da51be5-14d0-4d28-9a26-0018dc5499a3" SharedDllRefCount="no" KeyPath="no" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either">
                <CreateFolder/>
            </Component>
        </DirectoryRef>
        <DirectoryRef Id="LANGUAGEDIR">
            <Component Id="LANGUAGEDIR" Guid="71a5913e-5152-44a5-ae87-d067adc9e1db" SharedDllRefCount="no" KeyPath="no" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either">
                <CreateFolder/>
            </Component>
        </DirectoryRef>
        <DirectoryRef Id="ARTDOCSDIR">
            <Component Id="ArtDocs" Guid="dc6a44ae-bc27-4f39-8d0d-3a675a33e9a8" SharedDllRefCount="no" KeyPath="no" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either">
                <CreateFolder/>
                <File Id="ART001"     Name="ContentPane1.jpg"                                                                                      DiskId="1" Source="ContentPane1.jpg" />
                <File Id="ART002"     Name="ContentPane2.jpg"                                                                                      DiskId="1" Source="ContentPane2.jpg" />
                <File Id="ART003"     Name="ContentPane3.jpg"                                                                                      DiskId="1" Source="ContentPane3.jpg" />
            </Component>
        </DirectoryRef>
        <DirectoryRef Id="LOCALDOCSDIR">
            <Component Id="LocalDocs" Guid="c03f44ad-bf26-462b-a565-15985ae3ac27" SharedDllRefCount="no" KeyPath="no" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either">
                <CreateFolder/>
                <File Id="LOCAL001"   Name="footer.gif"                                                                                                    DiskId="1" Source="footer.gif" />
            </Component>
        </DirectoryRef>
        <DirectoryRef Id="DOCSDIR">
            <Component Id="HelpDocs" Guid="8592d02e-ba89-4c6b-96f4-2786e01765bf" SharedDllRefCount="no" KeyPath="no" NeverOverwrite="no" Permanent="no" Transitive="no" Win64="no" Location="either">
                <CreateFolder/>
                <File Id="IWFHELPTOC" Name="TableOfContents.xml"                                                                        DiskId="1" Source="TableOfContents.xml" KeyPath="yes" />
                <File Id="IWFHELP001" Name="MW_IWInvoiceWorkflow.docm"                                                    DiskId="1" Source="MW_IWInvoiceWorkflow.docm" />
                <File Id="IWFHELP002" Name="MW_IWInvoiceWorkflow.htm"                                                       DiskId="1" Source="MW_IWInvoiceWorkflow.htm" />
                <File Id="IWFHELP0039" Name="MW_IWInvoiceWorkflow.mht"                                                     DiskId="1" Source="MW_IWInvoiceWorkflow.mht" />
            </Component>
        </DirectoryRef>

        <Feature Id="Complete" Title="MW-InvoiceWorkflow Help Content" Description="Electronic handling and approval of invoices for Microsoft Dynamics AX" Display="expand" Level="1" ConfigurableDirectory="MWSOLUTIONSDIR">
            <Feature Id="MainDocumentationSet" Title="MW-InvoiceWorkflow Documentation" Description="The set of MW-InvoiceWorkflow documentation." Level="0">
                <ComponentRef Id="SOLDIR" />
                <ComponentRef Id="LANGUAGEDIR" />
                <ComponentRef Id="ArtDocs" />
                <ComponentRef Id="LocalDocs" />
                <ComponentRef Id=" HelpDocs " />
            </Feature>
        </Feature>

Change value in an XML using command line parameters with WIX Installer

2013-01-17T23:45:35Z

I was curious to know the best practice to modify an xml file that is get installed by my WIX installer. I am wanting to do it from command line parameters that get passed when a user runs the installer from command line.

Thank you,

Jeremiah