Collin Alpert
Collin Alpert
I have continued working here and there, however adding the operation analysis has been harder than thought. Would it be okay to merge the PR with syntax analysis?
That's interesting. I know this pattern changes behavior, however I never had the problem of an unreadable stack trace due to this. There were always plenty of other async methods...
That's interesting. I know this pattern changes behavior, however I never had the problem of an unreadable attack trace due to this. There were always plenty of other async methods...
@stevenaw Yes, sure! Just let me know what you need me to do to consider this mergable.
I am running into this issue as well. Having two OneWayToSource binding binding to the same object result in an infinite loop when calling `this.RaiseAndSetIfChanged( ref _value, value );`
Available in v2.4.0
How about also targeting netstandard2.0 so applications using .NET Framework can use this.
Exactly. I am talking about *additional* support. Something like `netcoreapp3.1;netstandard2.0` You might as well support .NET Core 3.1
The current version of Moq (4.20.69) does not depend on SponsorLink, which is why the analyzer does not trigger. See https://www.nuget.org/packages/Moq/4.20.69#dependencies-body-tab
Interesting. I wrote a test which installs version 4.20.0 and it passes. But I can't seem to get the build error. Will need to investigate a bit further.