question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

.NET core 3.x support

See original GitHub issue
Hi All.

Disclaimer: I tried looking through the Wiki and your README file but could not find the answer.

I am tasked to create BOM during CI/CD pipelines using GitHub Actions.

I discovered your wonderful plugin and decided to give it a shot. We have recently moved all of our projects from .NET core 2.X to 3.1. It seems that your tool does not support 3.1 project, is that a correct assumption?

The error I am getting is

Run ./dotnet-CycloneDX ExampleNetCore/ExampleNetCore.csproj -o bom/
It was not possible to find any compatible framework version
The framework 'Microsoft.NETCore.App', version '2.1.0' was not found.
  - The following frameworks were found:
      3.1.0 at [/opt/hostedtoolcache/dncs/3.1.100/x64/shared/Microsoft.NETCore.App]

You can resolve the problem by installing the specified framework and/or SDK.

The specified framework can be found at:
  - https://aka.ms/dotnet-core-applaunch?framework=Microsoft.NETCore.App&framework_version=2.1.0&arch=x64&rid=ubuntu.18.04-x64
##[error]Process completed with exit code 150.

Any clarity on your strategy and/or instructions how to contribute to getting this feature moving would be great. Thanks

Karol

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:6 (6 by maintainers)

github_iconTop GitHub Comments

1reaction
karolswdevcommented, Jan 29, 2020

Absolutely.

    - name: Setup .NET Core 2 🌩️
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: 2.1.803
    - name: Setup .NET Core 3 🌩️
      uses: actions/setup-dotnet@v1
      with:
        dotnet-version: 3.1.100

Did the trick.

1reaction
karolswdevcommented, Jan 29, 2020

@coderpatros You are absolutely right. Thanks so much for helping me out.

Read more comments on GitHub >

github_iconTop Results From Across the Web

.NET and .NET Core official support policy
Long Term Support (LTS). LTS releases are supported for three years after the initial release. · Standard Term Support (STS). STS releases are...
Read more >
Microsoft .NET - endoflife.date
NET Core 3.1, these releases will happen every November and every other release will be LTS. LTS releases are supported for three years ......
Read more >
Microsoft Announces End of Support Date for .NET Core 3.1
Microsoft announced today that .NET Core 3.1, a predecessor to .NET 5 and 6, will reach its end of support on December 13,...
Read more >
Microsoft to End Support for .NET Core 3.1 in December 2022
The long-term-support (LTS) version 3.1 of Microsoft .NET Core Framework is slated to go out of support on December 13th, 2022.
Read more >
Microsoft urges devs to migrate away from .NET Core 3.1 ...
NET Core and .NET Native releases, warned this July, Microsoft will stop providing technical support or servicing updates after EOS.
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found