fix errors

Author: gewarren

xml/System.Reflection.Emit/AssemblyBuilder.xml

@@ -61,14 +61,11 @@
 
 ## Remarks
 
-A dynamic assembly is an assembly that is created using the Reflection Emit APIs. A dynamic assembly can reference types defined in another dynamic or static assembly. You can use <xref:System.Reflection.Emit.AssemblyBuilder> to generate dynamic assemblies in memory and execute their code during the same application run. In .NET 9 we added a new [PersistedAssemblyBuilder](system-reflection-emit-persistedassemblybuilder.md)  with fully managed implementation of reflection emit that allows you save the assembly into a file. In .NET Framework, you can do both&mdash;run the dynamic assembly and save it to a file. The dynamic assembly created for saving is called a *persisted* assembly, while the regular memory-only assembly is called *transient* or *runnable*. In .NET Framework, a dynamic assembly can consist of one or more dynamic modules. In .NET Core and .NET 5+, a dynamic assembly can only consist of one dynamic module.
-
-The way you create an <xref:System.Reflection.Emit.AssemblyBuilder> instance differs for each implementation, but further steps for defining a module, type, method, or enum, and for writing IL, are quite similar.
+A dynamic assembly is an assembly that is created using the Reflection Emit APIs. A dynamic assembly can reference types defined in another dynamic or static assembly. You can use <xref:System.Reflection.Emit.AssemblyBuilder> to generate dynamic assemblies in memory and execute their code during the same application run. .NET 9 introduced the <xref:System.Reflection.Emit.PersistedAssemblyBuilder> type with a fully managed implementation of reflection emit that allows you to save the assembly to a file. A dynamic assembly can consist of only one dynamic module.
 
 ## Runnable dynamic assemblies in .NET
 
-To get a runnable <xref:System.Reflection.Emit.AssemblyBuilder> object, use the <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicAssembly*?displayProperty=nameWithType> method.
-Dynamic assemblies can be created using one of the following access modes:
+To get a runnable <xref:System.Reflection.Emit.AssemblyBuilder> object, use the <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicAssembly*?displayProperty=nameWithType> method. Dynamic assemblies can be created using one of the following access modes:
 
 - <xref:System.Reflection.Emit.AssemblyBuilderAccess.Run?displayProperty=nameWithType>
 
@@ -103,51 +100,8 @@ public void CreateAndRunAssembly(string assemblyPath)
 }
 ```
 
-## Persisted dynamic assemblies in .NET
-
-In .NET, the <xref:System.Reflection.Emit.PersistedAssemblyBuilder> type, which derives from <xref:System.Reflection.Emit.AssemblyBuilder>, lets you save dynamic assemblies. For more information, see the usage scenarios and examples at [PersistedAssemblyBuilder](system-reflection-emit-persistedassemblybuilder.md).
-
-## Persisted dynamic assemblies in .NET Framework
-
-In .NET Framework, dynamic assemblies and modules can be saved to files. To support this feature, the <xref:System.Reflection.Emit.AssemblyBuilderAccess> enumeration declares two additional fields: <xref:System.Reflection.Emit.AssemblyBuilderAccess.Save> and <xref:System.Reflection.Emit.AssemblyBuilderAccess.RunAndSave>.
-
-The dynamic modules in the persistable dynamic assembly are saved when the dynamic assembly is saved using the <xref:System.Reflection.Emit.AssemblyBuilder.Save*> method. To generate an executable, the <xref:System.Reflection.Emit.AssemblyBuilder.SetEntryPoint*> method must be called to identify the method that is the entry point to the assembly. Assemblies are saved as DLLs by default, unless the <xref:System.Reflection.Emit.AssemblyBuilder.SetEntryPoint*> method requests the generation of a console application or a Windows-based application.
-
-The following example demonstrates how to create, save, and run an assembly using .NET Framework.
-
-```csharp
-public void CreateRunAndSaveAssembly(string assemblyPath)
-{
-    AssemblyBuilder ab = Thread.GetDomain().DefineDynamicAssembly(new AssemblyName("MyAssembly"), AssemblyBuilderAccess.RunAndSave);
-    ModuleBuilder mob = ab.DefineDynamicModule("MyAssembly.dll");
-    TypeBuilder tb = mob.DefineType("MyType", TypeAttributes.Public | TypeAttributes.Class);
-    MethodBuilder meb = tb.DefineMethod("SumMethod", MethodAttributes.Public | MethodAttributes.Static,
-                                                                   typeof(int), new Type[] {typeof(int), typeof(int)});
-    ILGenerator il = meb.GetILGenerator();
-    il.Emit(OpCodes.Ldarg_0);
-    il.Emit(OpCodes.Ldarg_1);
-    il.Emit(OpCodes.Add);
-    il.Emit(OpCodes.Ret);
-
-    Type type = tb.CreateType();
-
-    MethodInfo method = type.GetMethod("SumMethod");
-    Console.WriteLine(method.Invoke(null, new object[] { 5, 10 }));
-    ab.Save("MyAssembly.dll");
-}
-```
-
-Some methods on the base <xref:System.Reflection.Assembly> class, such as `GetModules` and `GetLoadedModules`, won't work correctly when called from <xref:System.Reflection.Emit.AssemblyBuilder> objects. You can load the defined dynamic assembly and call the methods on the loaded assembly. For example, to ensure that resource modules are included in the returned module list, call `GetModules` on the loaded <xref:System.Reflection.Assembly> object. If a dynamic assembly contains more than one dynamic module, the assembly's manifest file name should match the module's name that's specified as the first argument to the <xref:System.Reflection.Emit.AssemblyBuilder.DefineDynamicModule*> method.
-
-The signing of a dynamic assembly using <xref:System.Reflection.AssemblyName.KeyPair> is not effective until the assembly is saved to disk. So, strong names will not work with transient dynamic assemblies.
-
-Dynamic assemblies can reference types defined in another assembly. A transient dynamic assembly can safely reference types defined in another transient dynamic assembly, a persistable dynamic assembly, or a static assembly. However, the common language runtime does not allow a persistable dynamic module to reference a type defined in a transient dynamic module. This is because when the persisted dynamic module is loaded after being saved to disk, the runtime cannot resolve the references to types defined in the transient dynamic module.
-
-### Restrictions on emitting to remote application domains
+The <xref:System.Reflection.Emit.PersistedAssemblyBuilder> type, which derives from <xref:System.Reflection.Emit.AssemblyBuilder>, lets you save dynamic assemblies. For more information, see the usage scenarios and examples at <xref:System.Reflection.Emit.PersistedAssemblyBuilder>.
 
-Some scenarios require a dynamic assembly to be created and executed in a remote application domain. Reflection emit does not allow a dynamic assembly to be emitted directly to a remote application domain. The solution is to emit the dynamic assembly in the current application domain, save the emitted dynamic assembly to disk, and then load the dynamic assembly into the remote application domain. The remoting and application domains are supported only in .NET Framework.
-> [!WARNING]
-> `AssemblyBuilder` APIs require a fully trusted environment with trusted input, similar to other technologies such as compilers. There are no restrictions other than basic validation for generated IL that the `AssemblyBuilder` can contain. That includes validation for member name, count, and associated metadata, such as custom attributes.
 ]]></format>
     </remarks>
     <example>

xml/System.Resources/ResourceManager.xml

@@ -69,7 +69,7 @@
     <remarks>
       <format type="text/markdown"><![CDATA[
 
-[!INCLUDE [untrusted-data-class-note](./includes/untrusted-data-class-note.md)]
+[!INCLUDE [untrusted-data-class-note](~/includes/untrusted-data-class-note.md)]
 
 The <xref:System.Resources.ResourceManager> class retrieves resources from a binary .resources file that is embedded in an assembly or from a standalone .resources file. If an app has been localized and localized resources have been deployed in [satellite assemblies](/dotnet/framework/resources/creating-satellite-assemblies-for-desktop-apps), it looks up culture-specific resources, provides resource fallback when a localized resource does not exist, and supports resource serialization.
 

xml/System.Resources/ResourceReader.xml

@@ -92,7 +92,7 @@
     <remarks>
       <format type="text/markdown"><![CDATA[
 
-[!INCLUDE [untrusted-data-class-note](./includes/untrusted-data-class-note.md)]
+[!INCLUDE [untrusted-data-class-note](~/includes/untrusted-data-class-note.md)]
 
 The <xref:System.Resources.ResourceReader> class provides a standard implementation of the <xref:System.Resources.IResourceReader> interface. A <xref:System.Resources.ResourceReader> instance represents either a standalone .resources file or a .resources file that is embedded in an assembly. It is used to enumerate the resources in a .resources file and retrieve its name/value pairs. It differs from the <xref:System.Resources.ResourceManager> class, which is used to retrieve specified named resources from a .resources file that is embedded in an assembly. The <xref:System.Resources.ResourceManager> class is used to retrieve resources whose names are known in advance, whereas the <xref:System.Resources.ResourceReader> class is useful for retrieving resources whose number or precise names are not known at compile time. For example, an application may use a resources file to store configuration information that is organized into sections and items in a section, where the number of sections or items in a section is not known in advance. Resources can then be named generically (such as `Section1`, `Section1Item1`, `Section1Item2`, and so on) and retrieved by using a <xref:System.Resources.ResourceReader> object.