Impossible to use IReadOnlyList<T>
See original GitHub issueAfter adding TaskScheduler Nuget package I can’t use IReadOnlyList<T> from standard .NET library and see the next error in my code:
The type 'IReadOnlyList<T>' exists in both 'Microsoft.Win32.TaskScheduler, Version=2.8.1.0, Culture=neutral, PublicKeyToken=c416bc1b32d97233' and 'mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
.Net Framework 4.5, version of TaskScheduler Nuget package 2.8.1.
Issue Analytics
- State:
- Created 5 years ago
- Comments:14 (7 by maintainers)
Top Results From Across the Web
Why doesn't List<T> explicitly implement IReadOnlyList<T>?
I think the tool you're using is causing the confusion. The indexer in the list is not implemented explicitly as IList implementation.
Read more >Example of why IReadOnlyList<T> is better than public List ...
Early today, I gave an answer to someone where I recommended using IReadOnlyList<T> . Then I was asked why not just use a...
Read more >IEnumerable vs IReadOnlyList
Today, I'd like to talk about IEnumerable and IReadOnlyList collection interfaces. ... Use IReadOnlyList when possible.
Read more >IEnumerable<T> Vs IReadOnlyList<T>
IEnumerable<T> and IReadOnlyList<T> both returns an immutable collection (in common use case - more on this shortly), which cannot be altered by ...
Read more >XPCollection<T> should implement IReadOnlyList<T> and ...
This is simply impossible by design and means that implementing i.e. IReadOnlyList<T> only guarantees that the reading methods & properties of ...
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 FreeTop 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
Top GitHub Comments
IReadOnlyList is only included in the .NET 2.0, 3.0 and 4.0 builds for backwards compatibility. My guess is that somehow, when Visual Studio unpacked your update, something went wrong and the incorrect build got associated with your project. I would remove the NuGet package from your package and re-reference it to see if the error goes away. I have a .NET 4.7.2 project building against this library without the error and it should be working the same.
vine a decir que ya elimine el troyano, lo borre y elimine por cmd, muchas gracias!! sos un idolo!!