Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Use Program.dll instead of Program.exe in illink docs #95752

Merged
merged 1 commit into from
Dec 8, 2023
Merged

Use Program.dll instead of Program.exe in illink docs #95752

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 8 additions & 8 deletions docs/tools/illink/illink-options.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,10 +10,10 @@ can also be passed using `_ExtraTrimmerArgs` property.

The command:

`illink -a Program.exe`
`illink -a Program.dll`

will use the assembly `Program.exe` as root ILLink input. That means that the ILLink will
start with the main entry point method of `Program.exe` (typically the `Main` method) and
will use the assembly `Program.dll` as root ILLink input. That means that the ILLink will
start with the main entry point method of `Program.dll` (typically the `Main` method) and
process all its dependencies to determine what is necessary for this assembly to run.

It's possible to use multiple input files and ILLink will use them all as multiple sources.
Expand All @@ -30,10 +30,10 @@ for multi entry-point libraries bundles.
- `visible` - Keep all members and types visible outside of the assembly. All internals members
are also rooted when assembly contains InternalsVisibleToAttribute.

You can retain all public members of `Program.exe` application even if they are not
You can retain all public members of `Program.dll` application even if they are not
referenced by any dependency by calling ILLink like

`illink -a Program.exe visible`
`illink -a Program.dll visible`

### Trimming from an [XML descriptor](data-formats.md#descriptor-format)

Expand Down Expand Up @@ -97,7 +97,7 @@ for by using `-d PATH` option.

Example:

`illink -d ../../libs -a program.exe`
`illink -d ../../libs -a Program.dll`

### Excluding framework features

Expand Down Expand Up @@ -136,11 +136,11 @@ You can now ask ILLink to add the custom step at the end of the pipeline:

Or you can ask ILLink to add it after a specific step:

`illink --custom-step +MarkStep:Foo.FooStep,D:\Bar\Foo.dll -a program.exe`
`illink --custom-step +MarkStep:Foo.FooStep,D:\Bar\Foo.dll -a Program.dll`

Or before a specific step:

`illink --custom-step -MarkStep:Foo.FooStep,D:\Bar\Foo.dll -a program.exe`
`illink --custom-step -MarkStep:Foo.FooStep,D:\Bar\Foo.dll -a Program.dll`

### Passing data to custom steps

Expand Down