# Source: https://raw.githubusercontent.com/unoplatform/uno/refs/heads/master/doc/articles/features/using-il-linker-webassembly.md

---
uid: uno.articles.features.illinker
---

# Using the IL Linker

> [!NOTE]
> This article is about the .NET IL Linker, you can also view information about [XAML and Resources Trimming](xref:Uno.Features.ResourcesTrimming).

## Support for features

In order to improve the size of the application, some platforms are providing the ability to unconditionally disable features if the app is known not to use them.

|Feature|MSBuild property|Description|
|-----|----|---|
|External Drag and Drop|`UnoDragDropExternalSupport`|Enables or disables drag and dropping content from **outside** the app using this property. Drag and Drop **inside** the app is always available when disabled.|

For example, to disable external drag and drop support on WebAssembly, add the following to your csproj:

```xml
<PropertyGroup>
    <UnoDragDropExternalSupport>false</UnoDragDropExternalSupport>
</PropertyGroup>
```

## WebAssembly

The [linker step](https://github.com/dotnet/linker/tree/main/docs) (also known as tree shaking, or IL Trimming) is responsible for the detection and removal of code that may not be used at runtime. This step is particularly important when targeting WebAssembly or native code in general, to reduce significantly the final package size.

The linker is generally efficient at removing code but in some cases it may remove too much code, making some assemblies fail to work properly. In particular, assemblies or features that rely on reflection don't work by default with the linker enabled. `JSON.NET` is a good example of this, as it relies on reflection very heavily.

To handle cases where the default linker behavior removes too much code, the linker can be manually configured using the `LinkerConfig.xml` file in Uno projects.

When parts of an application fail to work, you can:

- Add full assembly names to the `LinkerConfig.xml` file:

```xml
<assembly fullname="MyAssembly" />
```

- Add namespaces for the linker to ignore:

```xml
<assembly fullname="MyAssembly">
  <!-- This is required by Json.NET and any expression.Compile caller -->
  <type fullname="MyNamespace*" />
</assembly>
```

As a troubleshooting step to determine if the linker is causing your code to break, you can also disable the linker completely by adding the following to your `csproj` file:

```xml
<PropertyGroup>
  <WasmShellILLinkerEnabled>false</WasmShellILLinkerEnabled>
</PropertyGroup>
```

Note that disabling the linker is not recommended as it can force the compiler to generate very large WebAssembly modules AOT process, and go over the browser's size limits.

You can find additional information about the linker step in Uno Platform in the [Linker configuration documentation](https://github.com/unoplatform/Uno.Wasm.Bootstrap/blob/main/doc/linker-configuration.md).