summaryrefslogtreecommitdiff
path: root/src/mscorlib/Resources/Strings.resx
diff options
context:
space:
mode:
Diffstat (limited to 'src/mscorlib/Resources/Strings.resx')
-rw-r--r--src/mscorlib/Resources/Strings.resx12
1 files changed, 0 insertions, 12 deletions
diff --git a/src/mscorlib/Resources/Strings.resx b/src/mscorlib/Resources/Strings.resx
index cb9474fe00..791d1ca04d 100644
--- a/src/mscorlib/Resources/Strings.resx
+++ b/src/mscorlib/Resources/Strings.resx
@@ -2864,9 +2864,6 @@
<data name="NotSupported_AppX" xml:space="preserve">
<value>{0} is not supported in AppX.</value>
</data>
- <data name="NotSupported_AssemblyLoadCodeBase" xml:space="preserve">
- <value>Assembly.Load with a Codebase is not supported.</value>
- </data>
<data name="NotSupported_AssemblyLoadFromHash" xml:space="preserve">
<value>Assembly.LoadFrom with hashValue is not supported.</value>
</data>
@@ -3575,18 +3572,9 @@
<data name="LockRecursionException_RecursiveWriteNotAllowed" xml:space="preserve">
<value>Recursive write lock acquisitions not allowed in this mode.</value>
</data>
- <data name="LockRecursionException_ReadAfterWriteNotAllowed" xml:space="preserve">
- <value>A read lock may not be acquired with the write lock held in this mode.</value>
- </data>
<data name="LockRecursionException_RecursiveUpgradeNotAllowed" xml:space="preserve">
<value>Recursive upgradeable lock acquisitions not allowed in this mode.</value>
</data>
- <data name="LockRecursionException_RecursiveReadNotAllowed" xml:space="preserve">
- <value>Recursive read lock acquisitions not allowed in this mode.</value>
- </data>
- <data name="LockRecursionException_WriteAfterReadNotAllowed" xml:space="preserve">
- <value>Write lock may not be acquired with read lock held. This pattern is prone to deadlocks. Please ensure that read locks are released before taking a write lock. If an upgrade is necessary, use an upgrade lock in place of the read lock.</value>
- </data>
<data name="LockRecursionException_WriteAfterReadNotAllowed" xml:space="preserve">
<value>Write lock may not be acquired with read lock held. This pattern is prone to deadlocks. Please ensure that read locks are released before taking a write lock. If an upgrade is necessary, use an upgrade lock in place of the read lock.</value>
</data>