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

VS Code Planning mode

After the introduction of Plan mode in Visual Studio , it now also found its way into VS Code. Planning mode, or as I like to call it 'Hannibal mode', extends GitHub Copilot's Agent Mode capabilities to handle larger, multi-step coding tasks with a structured approach. Instead of jumping straight into code generation, Planning mode creates a detailed execution plan. If you want more details, have a look at my previous post . Putting plan mode into action VS Code takes a different approach compared to Visual Studio when using plan mode. Instead of a configuration setting that you can activate but have limited control over, planning is available as a separate chat mode/agent: I like this approach better than how Visual Studio does it as you have explicit control when plan mode is activated. Instead of immediately diving into execution, the plan agent creates a plan and asks some follow up questions: You can further edit the plan by clicking on ‘Open in Editor’: ...
Read more