Conditional dependency in nuget

Question

I have a tool which I want to deliver via nuget. I'm not very familiar with it, but what I read so far is that you can define dependencies with conditions. Can the condition also be a environment variable?

I found this here:

<ItemGroup>
    <!-- ... -->
    <PackageReference Include="Newtonsoft.Json" Version="9.0.1" Condition="'$(TargetFramework)' == 'net452'" />
    <!-- ... -->
</ItemGroup>

What are there for other "variables" in like in the example above the TargetFramework?

There are also two dependencies which contains what I need, how can I say that I need one of them and not both? And how can I define which I want if nothing is installed yet?

Peska · Accepted Answer · 2019-04-30 09:59:00Z

1

Yes, you can use Environment Variable in Condition:

Use a Condition attribute on a property to set the value only if the property has no value. For example, the following code sets the ToolsPath property to c:\tools only if the ToolsPath environment variable is not set:

<ToolsPath Condition="'$(TOOLSPATH)' == ''">c:\tools</ToolsPath>

Source: How to: Use environment variables in a build

List of all MSBuild build-in properties can be found here: https://stackoverflow.com/a/1453023/7225096

answered Apr 30, 2019 at 9:59

Peska

4,2203 gold badges28 silver badges43 bronze badges

Sign up to request clarification or add additional context in comments.

Collectives™ on Stack Overflow

Conditional dependency in nuget

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related