Any plans for updating this for latest version of .NET Core?
See original GitHub issueI’m using the current 1.0.1 version of the dotnet cli. And whenI run dotnet test
I get this output
No test is available in /projects/unit-testing-using-dotnet-test/PrimeService.Tests/bin/Debug/netcoreapp1.1/PrimeService.Tests.dll. Make sure that installed test discoverers & executors, platform & framework version settings are appropriate and try again.
All the examples from the docs use project.json / .xproj format for managing dependencies. I tried using dotnet’s updater but it didn’t work.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:1
- Comments:17
Top Results From Across the Web
.NET and .NET Core official support policy
NET Core support lifecycle offers support for each release. ... Customers choosing LTS need the latest patch update installed to qualify for support....
Read more >Command line to install/upgrade .NET Core
Are there command line commands to install or upgrade .NET Core? I checked to see if I had .NET Core was installed on...
Read more >Tools to Upgrade Your Existing .Net App to .NET Core ...
Today, in this article we will discuss the upgrade process of any existing .NET application into .NET Core 6. Last year November, Microsoft ......
Read more >Net Core 3.1 will reach EOL
MS is very clear that any update to newer versions of .NET are a potential security issue in 3.1. That .NET 3.1 will...
Read more >Net 6 runtime and windows updates
You can install any .NET 6 Runtime version. Except for critical bug fixes, breaking changes do not happen on the same major version....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Even better yes Gist updated https://gist.github.com/ylelan/a8af8e1816675d181d959de73822f1a0
@ylelan thanks for pointing that out. Actually yes,
this.GetType()...
does not fit well within astatic
method. You could swap that with the following:typeof(Program)...
. That should fit the bill, what do you think?