-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Specify that Assembly.Load[File/From] throwing on remote only applies to .NET Framework #9911
Conversation
/cc @gewarren |
Learn Build status updates of commit 7b0a91a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit e267603: ❌ Validation status: errorsPlease follow instructions here which may help to resolve issue.
xml/System.Reflection/Assembly.xml
For more details, please refer to the build report. Note: Your PR may contain errors or warnings or suggestions unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them. For any questions, please:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Learn Build status updates of commit fc9dd2a: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Co-authored-by: Genevieve Warren <24882762+gewarren@users.noreply.github.com>
Learn Build status updates of commit 22c7d1d: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Learn Build status updates of commit 0aec188: ✅ Validation status: passed
For more details, please refer to the build report. For any questions, please:
|
Summary
The
Assembly.Load[File/From]
docs indicate that they throwFileLoadException
on .NET Framework 4 and later for remote assemblies/paths. This is confusing as it can be interpreted as applying to .NET Core/5+, which does not do this.cc @AaronRobinsonMSFT @GrabYourPitchforks