You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CSharpier.MSBuild uses TargetFramework to choose which CSharpier tool to run which results in odd behavior when building multi-target libraries in Microsoft container images
#1022
Closed
adc-cjewett opened this issue
Nov 16, 2023
· 0 comments
· Fixed by #1034
We use Microsoft's container images to build our code. CSharpier.MSBuild does not seem to play nicely with those images in more recent versions and the reason for that is it uses the TargetFramework to determine which version of the CSharpier tool is run. That seems incorrect because a machine with only .NET 8.0.100 SDK can build and package multi-target libraries. However, it cannot run .NET 6 or .NET 7 tools as the below error describes.
Would it make sense to expose a property that allows the users to override and specify which version of the CSharpier tool to be run?
We use Microsoft's container images to build our code. CSharpier.MSBuild does not seem to play nicely with those images in more recent versions and the reason for that is it uses the TargetFramework to determine which version of the CSharpier tool is run. That seems incorrect because a machine with only .NET 8.0.100 SDK can build and package multi-target libraries. However, it cannot run .NET 6 or .NET 7 tools as the below error describes.
Would it make sense to expose a property that allows the users to override and specify which version of the CSharpier tool to be run?
Reproducible here: https://github.com/adc-cjewett/CSharpierTest
The text was updated successfully, but these errors were encountered: