-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
[release/7.0] Fix Equals in hot reload scenario #78258
Conversation
…nCacheTests.cs Co-authored-by: Steve Harter <steveharter@users.noreply.github.com>
Tagging subscribers to this area: @dotnet/area-system-reflection Issue DetailsBackport of #78249 to release/7.0 /cc @buyaa-n Customer ImpactTestingRiskIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.
|
Approved for servicing by email, updating the label with approved The failure unrelated and related issue is linked |
CI failure is known and unrelated: #77988 |
Backport of #78249 to release/7.0
/cc @buyaa-n
Description
While fixing Hot Reload breaks MethodInfo equality we caused regression in .NET 7 Huge Breaking Issue in Net7 with MemberInfo equality
Customer Impact
The regression causes wrong equality check result for derived members of a Type when hot reload enabled. As hot reload is enabled by default in VS it could cause failures for any customer that uses Reflection and debugging their code. They would need to disable hot reload to be able to debug further
Testing
Added unit tests that reproes the issue
Risk
Low, the fix adds one additional check (of
ReflectedTypes
) but only affects hot reload scenariosIMPORTANT: Is this backport for a servicing release? If so and this change touches code that ships in a NuGet package, please make certain that you have added any necessary package authoring and gotten it explicitly reviewed.