# Referencing Assemblies

## Class Libraries

When building class libraries that target .NET 6+, the assemblies that are referenced via NuGet will not be copied to the bin folder **unless** the following element is added to the library's **csproj** file:

{% code title="App.csproj" %}

```
<CopyLocalLockFileAssemblies>true</CopyLocalLockFileAssemblies>
```

{% endcode %}

{% hint style="info" %}
All referenced assemblies should be copied automatically in **.NET Framework**.
{% endhint %}

## Dynamic Assemblies

If a project or assembly reference is not used in the main Wisej.NET project, the referenced project's dependencies will not be loaded into the App Domain automatically.

{% hint style="info" %}
In **.NET Framework**, any assembly referenced by the main Wisej.NET project would have it's dependencies loaded into the App Domain.
{% endhint %}

**For example:**

If you create a custom control library that implements a custom **Bubbles** notification that gets dynamically injected into the main Wisej.NET project, you will need to call **Application.LoadAssembly()** on **Wisej.Web.Ext.Bubbles** to load the custom library's dependency into the Wisej.NET project.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.wisej.com/docs/releases/whats-new-in-3.0/referencing-assemblies.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.