You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/tools/illink/error-codes.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1870,6 +1870,22 @@ void TestMethod()
1870
1870
}
1871
1871
```
1872
1872
1873
+
#### `IL2122`: Type 'typeName' is not assembly qualified. Type name strings used for dynamically accessing a type should be assembly qualified.
1874
+
1875
+
- The type name string passed to a location with `DynamicallyAccessedMembers` requirements was not assembly-qualified, so the trimmer cannot guarantee that the type is preserved. Consider using an assembly-qualified name instead.
1876
+
1877
+
```C#
1878
+
// warning IL2122: Type 'MyClass' is not assembly qualified. Type name strings used for dynamically accessing a type should be assembly qualified.
1879
+
GetTypeWrapper("MyClass");
1880
+
1881
+
classMyClass { }
1882
+
1883
+
// May be defined in another assembly, so at runtime Type.GetType will look in that assembly for "MyClass".
Copy file name to clipboardExpand all lines: docs/workflow/requirements/windows-requirements.md
+30Lines changed: 30 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,3 +108,33 @@ You can also temporarily add a directory to the PATH environment variable with t
108
108
You can make your change to the PATH variable persistent by going to _Control Panel -> System And Security -> System -> Advanced system settings -> Environment Variables_, and select the `Path` variable under `System Variables` (if you want to change it for all users) or `User Variables` (if you only want to change it for the current user).
109
109
110
110
Simply edit the PATH variable's value and add the directory (with a semicolon separator).
111
+
112
+
### Windows on Arm64
113
+
114
+
The Windows on Arm64 development experience has improved substantially over the last few years, however there are still a few steps you should take to improve performance when developing dotnet/runtime on an ARM device.
115
+
116
+
During preview releases, the repo sources its compilers from the [Microsoft.NET.Compilers.Toolset](https://www.nuget.org/packages/Microsoft.Net.Compilers.Toolset/) package whose bits aren't configured for the ARM64 build of .NET framework. This can result in [suboptimal performance](https://github.com/dotnet/runtime/issues/104548) when working on libraries in Visual Studio. The issue can be worked around by [configuring the registry](https://github.com/dotnet/runtime/issues/104548#issuecomment-2214581797) to run the compiler as Arm64 processes. The proper fix that will make this workaround unnecessary is being worked on in [this PR](https://github.com/dotnet/roslyn/pull/74285).
117
+
118
+
Using an Administrator Powershell prompt run the script:
Write-Host" Pass a comma-separated list to build for multiple architectures."
34
-
Write-Host(" [Default: {0} (Depends on your console's architecture.)]"-f [System.Runtime.InteropServices.RuntimeInformation]::ProcessArchitecture.ToString().ToLowerInvariant())
34
+
Write-Host" [Default: Your machine's architecture.]"
35
35
Write-Host" -binaryLog (-bl) Output binary log."
36
36
Write-Host" -configuration (-c) Build configuration: Debug, Release or Checked."
37
37
Write-Host" Checked is exclusive to the CLR subset. It is the same as Debug, except code is"
0 commit comments