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
Was using ReportGenerator without a specified version and got this error this morning:
It was not possible to find any compatible framework version
The specified framework 'Microsoft.NETCore.App', version '3.0.0' was not found.
- Check application dependencies and target a framework version installed at:
C:\Program Files\dotnet
- Installing .NET Core prerequisites might help resolve this problem:
https://go.microsoft.com/fwlink/?LinkID=798306&clcid=0x409
- The .NET Core framework and SDK can be installed from:
https://aka.ms/dotnet-download
- The following versions are installed:
2.0.9 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
2.1.9 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
2.1.11 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
2.1.12 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
2.1.13 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
2.2.4 at [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Fixating the version to the previous release, #tool nuget:?package=ReportGenerator&version=4.2.20, fixes my problem and I suspect the error is related to #205 (although I haven't performed any deeper investigation).
Thanks!
The text was updated successfully, but these errors were encountered:
If you use dotnet $(UserProfile)\.nuget\packages\reportgenerator\4.3.0\tools\netcoreapp2.0\ReportGenerator.dll you should be able to use ReportGenerator without .NET Core 3.0
It would be useful if you share the command that you trying to execute.
I currently don't understand why tools\netcoreapp3.0\ReportGenerator.dll gets executed.
Was using ReportGenerator without a specified version and got this error this morning:
Fixating the version to the previous release,
#tool nuget:?package=ReportGenerator&version=4.2.20
, fixes my problem and I suspect the error is related to #205 (although I haven't performed any deeper investigation).Thanks!
The text was updated successfully, but these errors were encountered: