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 Framework compatibility

See original GitHub issue

Hi, I have a question/need for some general knowledge surrounding coverlets compatibility with .NET Framework.

I’m receiving an error when attempting to generate code coverage for a test project that references Microsoft.ReportViewer.WebForms. The error is occurring because coverlet is looking in the .NET Core sdk folder for the necessary dll, and it’s not there. The assembly is present elsewhere. Please see the warning below. This precedes the build failure.

Do you have any recommendations for a graceful way to point coverlet towards non .NET Core referenced assemblies?

C:\Program Files\dotnet\sdk\2.2.107\Microsoft.CSharp.CurrentVersion.targets(134,9): warning MSB3884: Could not find rule set file "AllRules.ruleset". [C:\source\SSDirectoryLibrary44\SSDirectoryLibrary44.csproj] C:\Program Files\dotnet\sdk\2.2.107\Microsoft.Common.CurrentVersion.targets(2110,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.ReportViewer.WebForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.

Working in .NET 4.6.1 Xunit 2.4.1 coverlet 2.6.3

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:24

github_iconTop GitHub Comments

1reaction
eal61commented, Sep 9, 2019

I deleted the bin folder in my test project and re-ran the dotnet test command. All tests were run successfully, but the coverage report is empty. Ran with logging enabled and I’m looking at the binlog now

0reactions
MarcoRossignolicommented, Jan 2, 2020

Close for stale conversation, feel free to re-open if needed.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Version compatibility in .NET Framework
The .NET Framework 4.5 and later versions are backward-compatible with apps that were built with earlier versions of the .NET Framework. In ...
Read more >
NET Framework system requirements
On 64-bit operating systems, .NET Framework supports both WOW64 (32-bit processing on a 64-bit machine) and native 64-bit processing. Supported ...
Read more >
NET Standard
This compatibility mode allows .NET Standard projects to reference .NET Framework libraries as if they were compiled for .NET Standard.
Read more >
NET Framework & Windows OS versions
In addition, if your app targets version 2.0, 3.0, or 3.5, your users may be required to enable .NET Framework 3.5 on a...
Read more >
NET Framework - Runtime and retargeting changes
Compatibility is an important goal of each .NET Framework release. Compatibility ensures that each version is additive, so previous versions ...
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