<p>It seems that there is no other way than creating NuGet packages from those <code>.dll</code> files required for the build, as this <a href="https://stackoverflow.com/questions/65804770/include-local-dll-in-azure-devops-pipeline/65805424#65805424">post on SO</a> points out.</p>

CC BY-SA 4.0
2021-07-30T09:20:46.837Z
2021-07-30T09:20:46.837Z
Sasquatch
<p>I hope I am posting this in the correct forum, but to me at least, it seemed that the focus was more on deployment.</p>
<p>I am currently stuck after having successfully refactored an application by extracting certain responsibilities into
class libraries (language: C#, .NET 4.8).</p>
<p>The application is hooked up to Azure CI builds using Azure DevOps, deploying the application to an IIS on a VM. Pipelines are triggered upon commit.</p>
<p>The pipeline looks roughly like this:</p>
<ul>
<li><code>NuGet restore</code></li>
<li><code>Build Solution</code></li>
<li><code>Test Assemblies (Visual Studio Tests)</code></li>
<li><code>Publish symbols path</code></li>
<li><code>Publish Artifact</code></li>
</ul>
<p>The <code>.dll</code> files are located in a dedicated folder within the application.
I am referencing the <code>.dll</code> files in the application and have already changed their property <code>Copy to Output Directory</code> to <code>Copy if newer</code>.
When building the application on my local machine, the required custom <code>.dll</code> files are being copied to the <code>bin</code> folder as expected.
However, when analysing the deployment logs, I noticed that the custom <code>.dll</code> files are not being updated / copied.</p>
<p>How can I make sure that the custom <code>.dll</code> files are deployed properly (same as the standard <code>.ddl</code> files)?</p>

<continuous-integration><azure-devops><deployment><azure-pipelines>
Deploy an application using dll files to IIS on a VM
Sasquatch
# Deploy an application using dll files to IIS on a VM

(Asked by: username_0 on 2021-07-28)

I hope I am posting this in the correct forum, but to me at least, it seemed that the focus was more on deployment.

I am currently stuck after having successfully refactored an application by extracting certain responsibilities into
class libraries (language: C#, .NET 4.8).

The application is hooked up to Azure CI builds using Azure DevOps, deploying the application to an IIS on a VM. Pipelines are triggered upon commit.

The pipeline looks roughly like this:

* `NuGet restore`
* `Build Solution`
* `Test Assemblies (Visual Studio Tests)`
* `Publish symbols path`
* `Publish Artifact`

The `.dll` files are located in a dedicated folder within the application.
I am referencing the `.dll` files in the application and have already changed their property `Copy to Output Directory` to `Copy if newer`.
When building the application on my local machine, the required custom `.dll` files are being copied to the `bin` folder as expected.
However, when analysing the deployment logs, I noticed that the custom `.dll` files are not being updated / copied.

How can I make sure that the custom `.dll` files are deployed properly (same as the standard `.ddl` files)?

**Tags:** continuous-integration, azure-devops, deployment, azure-pipelines


---

## 1 answers

### Answer by username_0 on 2021-07-30. Score: 1 | Accepted answer

It seems that there is no other way than creating NuGet packages from those `.dll` files required for the build, as this [post on SO](https://stackoverflow.com/questions/65804770/include-local-dll-in-azure-devops-pipeline/65805424#65805424) points out.


---

