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
Exceptions from MemberDataShouldReferenceValidMember #1937
Comments
Hi Jonas, I got the very same warning using XUnit on a new .NET Core 2.2, VS 2019 test project, despite the tests running/passing fine. I upgraded all nugets, cleaned & rebuilt. Warning still present. Restarted VS2019, re-ran tests and the warning went away. HTH |
Hi Peter. |
Just for the record, this exact thing happened to me on the same type of project. It also went away after restarting VS2019. |
I hit the exception again. public static IEnumerable<object[]> TestData()
{
yield return new object[] { 1 };
// yield return new object[] { 2 };
}
|
I got similar warnings with VS2017 and all were gone after I restarted Visual Studio. |
I have same issue, sometimes it works sometimes it doesn't. System.Exception : Value cannot be null. ` [JsonProperty("ListOfCifs")]
|
I'm going to close this because everybody seems to think it gets solved by restarting Visual Studio, which would indicate that there is some old DLL being held onto, or something similar...? If someone can provide a repro project that cannot be solved by restarting Visual Studio, please open a new issue. Thanks! |
Same here, had to disable all diagnostics starting with "MemberData..." to void build errors, via
Setting them as anything other than The source is nothing special:
|
@kzu Let me know if you can provide a repro. We have our integration project which doesn't show this issue. |
I haven't been able to construct a completely reproducible case, as I know how to exactly trigger the exceptions, but it did happen when trying to create this minimal example.
The text was updated successfully, but these errors were encountered: