Skip to main content

Visual Studio: Reference a different DLL depending on your build configuration

For a Windows 8 application we are building, we have to deploy versions that connect to different backends. We could have created different branches  but this would result in lots of merges. Instead we decided to go for a provider model combined with conditional compilation symbols. This allows us to easily switch between providers by changing the build configuration.
This brought us half way there but we had still an issue because we also had to use a different 3th party component depending on the backend. So what we actually want is that when setting the build configuration to QA, the 3thparty.component.QA winmd file was loaded and if we switch to Production the 3thparty.component.Production winmd file was loaded.
This is perfectly possible by changing the project file and editing the underlying MSBuild settings:
  • Unload the project.
  • Choose Edit project and open it using the XML editor.
  • Find the reference to the component you want to change depending on the build configuration.
<Reference Include="3thPartyComponent">
 <HintPath>..\packages\3thPartyComponentQA\lib\winrt45\3thparty.component.QA.winmd</HintPath>
</Reference>

  • Duplicate the reference for each build configuration you want to support. 
<Reference Include="3thPartyComponent">
 <HintPath>..\packages\3thPartyComponentQA\lib\winrt45\3thparty.component.QA.winmd</HintPath>
</Reference>
<Reference Include="3thPartyComponent">
 <HintPath>..\packages\3thPartyComponentProduction\lib\winrt45\3thparty.component.Production.winmd</HintPath>
</Reference>

  • Apply a conditional to the Reference elements.

<Reference Include="3thPartyComponent" Condition="'$(Configuration)'=='QA'">
 <HintPath>..\packages\3thPartyComponentQA\lib\winrt45\3thparty.component.QA.winmd</HintPath>
</Reference>
<Reference Include="3thPartyComponent" Condition="'$(Configuration)'=='Production'">
 <HintPath>..\packages\3thPartyComponentProduction\lib\winrt45\3thparty.component.Production.winmd</HintPath>
</Reference>
Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more