-
Notifications
You must be signed in to change notification settings - Fork 266
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
Bump System.Threading.Tasks.Extensions #653
Comments
Hi @benoitdion , Which 4.x version did you want the later Happy to try to make things easier with Unity! |
Awesome! In general though, keeping the transitive dependencies up to date is likely to cause fewer issues over time. |
Is it fine to make the change from next NSub release (4.2.x or 4.3.x etc)? Or you need it from an older release? If you add an explicit project reference to |
Off of 4.2.2 would be perfect! Unfortunately, it seems Unity requires a perfect match in some situations :(. |
I see 5.1 is still using System.Threading.Tasks.Extensions 4.3+. But of course, you could use a newer version in your code. @dtchepak I think we don't have plans to change this? Should we close this one? |
Yes I never got around to this. 😞 I'll close, but please re-open if there are continued problems with Unity and we'll re-evaluate. |
To avoid confusing, I'm marking this as not plannend instead of completed :) |
I realize this might be a big ask but would it be possible to release a new 4.x version with a more recent version of
System.Threading.Tasks.Extensions
? This will make consuming NSubstitute with Unity a bit easier when other libraries bring in newer versions of the tasks extensions. Unfortunately, Unity doesn't support assembly binding redirect the same way regular dot net projects do.The text was updated successfully, but these errors were encountered: