-
Notifications
You must be signed in to change notification settings - Fork 387
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Missing method with vstest integration #456
Comments
https://github.com/tonerdo/coverlet/blob/master/README.md#vstest-integration |
@MarcoRossignoli I would assume that the latest nightly of 3.0 preview 6 would have the bits? It's newer than 2.2.300. |
Ah you're right completely missed that line...it's friday time to take a break...cc: @vagisha-nidhi that wrote collector. |
AFAIK the change in 2.2.300 hasn't flowed into 3.x yet |
@ViktorHofer is correct. The 2.2.300 changes haven't flown into 3.x Preview 6.
Should this message be replaced with something more informative (like using the correct sdk version)? cc: @cltshivash |
@vagisha-nidhi yes I agree this error is a bit cryptic. Maybe improve with some advice(catch |
@onovotny I close issue because the question has been anwered by @vagisha-nidhi |
Update for anyone following along -- the 16.1.1 vstest runner has been merged into the latest .NET Core 3 Preview 7 nightlies, so this works now. |
Thanks for info Oren! |
Would fallback's be available to lower the framework version?
or something like:
|
@YulerB which versioin of sdk you want to use?Cannot compile with greather version but lower tfm? |
Our build agents on RHEL 7 only support dotnet core sdk 2.1.400 |
@YulerB can you open new issue? |
Hi,
I'm trying to use the VSTest integration and getting the following:
I'm using the .NET Core 3 SDK Preview 6 3.0.100-preview6-012262.
The test project has the following:
I also tried with
Microsoft.NET.Test.SDK
16.2.0-preview-20190606-02
, which was just published 5 hours ago.The text was updated successfully, but these errors were encountered: