Skip to content
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

After deleting a class member from the. net core and hot reloading, it is still possible to obtain this class member through reflection #55486

Closed
1 task done
2535688890 opened this issue May 2, 2024 · 2 comments
Labels
feature-hot-reload This issue is related to the Hot Reload feaature ✔️ Resolution: Duplicate Resolved as a duplicate of another issue needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically Status: Resolved

Comments

@2535688890
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

After deleting a class member from the. net core and hot reloading, it is still possible to obtain this class member through reflection

Expected Behavior

I hope to delete a class member. After hot overloading, it can be completely overloaded, and reflection cannot obtain the deleted class member

Steps To Reproduce

E9$6J(CT1 P`~(K)0@~6G{6
ACTOHFFF(8~CB82B{VE5{{J
O}W Y@HHPQQ{T8)C876T2TH

Modify class, hot overload

1@$G8BMDWTCSR{X_Y75N%RB
D(BX)HS( )G(UL{23R IHY

Exceptions (if any)

No response

.NET Version

8.0.204

Anything else?

.NET SDK:
Version: 8.0.204
Commit: c338c7548c
Workload version: 8.0.200-manifests.7d36c14f

运行时环境:
OS Name: Windows
OS Version: 10.0.22631
OS Platform: Windows
RID: win-x64
Base Path: C:\Program Files\dotnet\sdk\8.0.204\

已安装 .NET 工作负载:
没有要显示的已安装工作负载。

Host:
Version: 8.0.4
Architecture: x64
Commit: 2d7eea2529

.NET SDKs installed:
6.0.421 [C:\Program Files\dotnet\sdk]
8.0.204 [C:\Program Files\dotnet\sdk]

.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 8.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.NETCore.App 8.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
Microsoft.WindowsDesktop.App 5.0.17 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 6.0.29 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]
Microsoft.WindowsDesktop.App 8.0.4 [C:\Program Files\dotnet\shared\Microsoft.WindowsDesktop.App]

Other architectures found:
x86 [C:\Program Files (x86)\dotnet]
registered at [HKLM\SOFTWARE\dotnet\Setup\InstalledVersions\x86\InstallLocation]

Environment variables:
Not set

global.json file:
Not found

Learn more:
https://aka.ms/dotnet/info

Download .NET:
https://aka.ms/dotnet/download

@dotnet-issue-labeler dotnet-issue-labeler bot added the needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically label May 2, 2024
@mkArtakMSFT
Copy link
Member

@tmat can you help with this one?

@mkArtakMSFT mkArtakMSFT added the feature-hot-reload This issue is related to the Hot Reload feaature label May 2, 2024
@tmat
Copy link
Member

tmat commented May 6, 2024

Dup of dotnet/runtime#75154. Please vote on this issue.

@tmat tmat closed this as completed May 6, 2024
@mkArtakMSFT mkArtakMSFT added the ✔️ Resolution: Duplicate Resolved as a duplicate of another issue label May 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-hot-reload This issue is related to the Hot Reload feaature ✔️ Resolution: Duplicate Resolved as a duplicate of another issue needs-area-label Used by the dotnet-issue-labeler to label those issues which couldn't be triaged automatically Status: Resolved
Projects
None yet
Development

No branches or pull requests

3 participants