Custom conditional dotnet add package

[TangMonk]

for instance:

$ dotnet add package LigerShark.WebOptimizer.TypeScript  --dev

<ItemGroup Env="Development">
    <PackageReference Include="LigerShark.WebOptimizer.Core" Version="3.0.250" />
    <PackageReference Include="LigerShark.WebOptimizer.Sass" Version="3.0.40-beta" />
    <PackageReference Include="LigerShark.WebOptimizer.TypeScript" Version="2.5.10-beta" />
</ItemGroup>

<ItemGroup Env="Production">
 <PackageReference Include="Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation" Version="3.0.0" />
</ItemGroup>

This will avoid binary size when publish project and will avoid environment condition in Startup.cs

[dominoFire]

You can achieve a similar effect using the Condition attribute for MSBuild ItemGroup elements. For example:

  <PropertyGroup>
    <Env Condition="'$(Env)' == ''">Development</Env>
  </PropertyGroup>

  <ItemGroup Condition="'$(Env)' == 'Production'">
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation" Version="3.0.0" />
  </ItemGroup>

  <ItemGroup Condition="'$(Env)' == 'Development'">
    <PackageReference Include="LigerShark.WebOptimizer.Core" Version="3.0.250" />
    <PackageReference Include="LigerShark.WebOptimizer.Sass" Version="3.0.40-beta" />
    <PackageReference Include="LigerShark.WebOptimizer.TypeScript" Version="2.5.10-beta" />
  </ItemGroup>

When you add packages via dotnet.exe, for example:

dotnet add package NuGet.Protocol

It will add the package to the ItemGroup conditioned for the 'Development' ItemGroup, since it is the default value for the Env property, as defined in the PropertyGroup:

  <PropertyGroup>
    <Env Condition="'$(Env)' == ''">Development</Env>
  </PropertyGroup>

  <ItemGroup Condition="'$(Env)' == 'Production'">
    <PackageReference Include="Microsoft.AspNetCore.Mvc.Razor.RuntimeCompilation" Version="3.0.0" />
  </ItemGroup>

  <ItemGroup Condition="'$(Env)' == 'Development'">
    <PackageReference Include="LigerShark.WebOptimizer.Core" Version="3.0.250" />
    <PackageReference Include="LigerShark.WebOptimizer.Sass" Version="3.0.40-beta" />
    <PackageReference Include="LigerShark.WebOptimizer.TypeScript" Version="2.5.10-beta" />
    <PackageReference Include="NuGet.Protocol" Version="5.3.1" />
  </ItemGroup>

In that case, you will need to manually edit the .csproj file for adding the PackageReference for different ItemGroup's

[Dimigergo]

Hello!

I have the same problem, but the workaround doesn't work when the nuget package is already added, and only need to update the package.

When I try to use an another workaround with choose condition the problem is the same.

    <Choose>
        <When Condition=" '$(Configuration)' == 'Debug'">
            <ItemGroup>
                <ProjectReference Include="..\MLR.Components\MLR.Components.csproj" />
            </ItemGroup>
        </When>
        <Otherwise>
            <ItemGroup>
                <PackageReference Include="MLR.Components" Version="3.0.13655" />
            </ItemGroup>
        </Otherwise>
    </Choose>

The dotnet list command simply ignore the otherwise too.
Of course the dotnet add package returns the original problem: error: Value cannot be null. (Parameter 'path1')

We use internal (company) nuget packages and build with Azure Devops Server and only can use dotnet cli. :(
Will it be a bug fix?