"Conditional Compile" in XAML?

Question

We have a program we use internally to test and validate an industrial control product we sell. We'd like to be able to offer a scaled-down or lightweight version of this to certain customers.

Our program is written in using C# and WPF (thus XAML). Having sections of C# code that only build for use in our factory is easily done using conditional compile features, e.g.,

#if FACTORY
    // our in-house code . . .  
   . . . 
   . . . 
#endif

But how can we accomplish something similar for the XAML portion of our program?

Note: **There's a Stack Overflow question on this topic where someone posted a terse answer with a link but the link doesn't seem to be related to the question. So don't count this as a duplicate based on that because that doesn't answer the question.* XAML Conditional Compilation

Can you add more details about which type of features would you want to disable? since XAML is just to `define the UI` - I fail to imagine what parts of XAML you would want to conditionally compile. — Federico Berasategui, Feb 07 '14 at 21:35
There's [answer](http://stackoverflow.com/a/19940157/259206) to other question which looks promising. — Borislav Ivanov, Feb 07 '14 at 22:04
There are buttons and other UI components we'd like to only have available and visible in the factory. — user316117, Feb 09 '14 at 17:22

score 2 · Accepted Answer · edited May 23 '17 at 11:53

The technique illustrated in the linked question/answer may go some way towards giving conditional processing of XAML elements, but I don't think it is going to give you exactly what you are after.

There are another two options that may be better suited to your needs: programmatic conditional compilation and conditional inclusion at build time.

For the programmatic conditional compilation you can use regular conditional compilation in the code behind of your view (preferable as it's a UI element you're affecting) or in the viewmodel (not so pure, but totally acceptable if you have to include it in multiple layers). This conditional compilation can be used to either change what values are returned from properties (by changing which lines are compiled in and therefore executed) or by eliminating blocks of code (this is clunky but still effective), you can then have a XAML DataTrigger that has an expression dependent on the conditionally compiled code.

The other option is to specify control templates in a XAML resource file and either programmatically select them or use a MSBuild property in an ItemGroup expression in your proj file to control which files are included in the build. Combined with regular programmatic conditional compilation in your models/viewmodels this should give you a nice clean solution for your problem - in fact using this option you possibly don't even need the programmatic conditional compilation.

A TemplateSelector may also help, but IMVHO its a bit of a filthy hack. A TemplateSelector is supposed to swap a template based on type, but you can also exploit this to include extra code to determine the template to use - this could be a good spot to include conditionally compiled code.

+1 for the specifying of templates be they the control templates/user controls etc. — Chris W., Feb 07 '14 at 22:18
An alternate suggestion was [put forward by Tomer Sharman](http://social.msdn.microsoft.com/Forums/wpapps/en-us/baee88bf-52c6-420f-bb71-96bc97e37fe4/any-way-to-get-alternatecontent-choice-tags-working-in-xaml?forum=wpdevelop) involving an attached property. It's not really conditional compilation though as I believe the content is being selected at runtime. Still, it's another option to consider. — Mark Feldman, Feb 07 '14 at 23:30

score 1 · Answer 2 · edited May 23 '17 at 12:17

I'd use an XSTL transformation, this MSDN article explains how to apply them at compile time. It should be possible to set up the transform to strip sections inside pre-processor tags (this SO question appears to show just that), although I'd probably put them in comments myself so that you don't break the Visual Studio designer. There's also this SO question which shows how to include processor directives as regular XML tags that you could again just embed inside your XAML.

score 1 · Answer 3 · answered Dec 13 '17 at 19:13

Define compiler constant FACTORY.

Create markup extension class:

using System;
using System.Windows.Markup;

namespace Conditional 
{
    public class Condition : MarkupExtension 
    {
        public object MyFactory { get; set; }
        public object Other { get; set; }

        public override object ProvideValue(IServiceProvider sp) 
        {
        #if FACTORY
            return this.MyFactory;
        #else
            return this.Other;
        #endif
        }
    }
}

In XAML markup:

Import namespace:

xmlns:conditional="clr-namespace:RootNamespace.Conditional"

Insert this block of code where need conditional XAML markup:

<ViewBox>
    <conditional:Condition>
        <conditional:Condition.MyFactory>
            <TextBlock Text="This is My Factory"/>
        </conditional:Condition.MyFactory>
        <conditional:Condition.Other>
            <TextBlock Text="this is other" />
        </conditional:Condition.Other>
    </conditional:Condition>
</ViewBox>

Thank you! While this solution is working, it requires to insert all possible conditions in xaml (else it throws a null reference exception). Do you know a way to avoid this? Thanks — ʞᴉɯ, Mar 29 '20 at 19:28

"Conditional Compile" in XAML?

3 Answers3

Linked