Skip to content
This repository has been archived by the owner on Jan 23, 2023. It is now read-only.

Remove cross appdomains cultures checks #9328

Merged

Conversation

tarekgh
Copy link
Member

@tarekgh tarekgh commented Feb 4, 2017

In the ful framework, CultureInfo and other globalization objects are marked as agile which means it can cross the appdomains. In coreclr we don't have multiple appdomains anymore so these checks are not really needed.
removing these checks will make coreclr consistent when running on Windows and other OS's

Fixes #9250

In the ful framework, CultureInfo and other globalization objects are marked as agile which means it can cross the appdomains. In coreclr we don't have multiple appdomains anymore so these checks are not really needed.
removing these checks will make coreclr consistent when running on Windows and other OS's
@tarekgh
Copy link
Member Author

tarekgh commented Feb 4, 2017

@jkotas could you please have a look?

@tarekgh
Copy link
Member Author

tarekgh commented Feb 4, 2017

test OSX x64 Checked Build and Test please
test Ubuntu x64 Checked Build and Test please

@tarekgh tarekgh merged commit 748d467 into dotnet:master Feb 4, 2017
jorive pushed a commit to guhuro/coreclr that referenced this pull request May 4, 2017
* Remove cross appdomains cultures checks

In the ful framework, CultureInfo and other globalization objects are marked as agile which means it can cross the appdomains. In coreclr we don't have multiple appdomains anymore so these checks are not really needed.
removing these checks will make coreclr consistent when running on Windows and other OS's

* Remove un-needed resource entry
@karelz karelz modified the milestone: 2.0.0 Aug 28, 2017
@tarekgh tarekgh deleted the RemoveCrossDomainsChecksInGloablization branch March 25, 2019 15:30
picenka21 pushed a commit to picenka21/runtime that referenced this pull request Feb 18, 2022
* Remove cross appdomains cultures checks

In the ful framework, CultureInfo and other globalization objects are marked as agile which means it can cross the appdomains. In coreclr we don't have multiple appdomains anymore so these checks are not really needed.
removing these checks will make coreclr consistent when running on Windows and other OS's

* Remove un-needed resource entry


Commit migrated from dotnet/coreclr@748d467
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants