Return to Question

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)?

Update

Found a suggestion on SO. This post suggests transforming the .dll into a NuGet package then publishing the package to the Azure DevOps Nuget feed.

This seems to be a bit of an effort creating a NuGet package for each of the .dll files required for the application. Moreover, I can imagine making a ton of mistakes when setting up the individual pipelines (there are a few class libraries that need to be taken care of).

Is the approach above the only option available?

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)?

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)?

Update

Found a suggestion on SO. This post suggests transforming the .dll into a NuGet package then publishing the package to the Azure DevOps Nuget feed. Is that the only option, since it seems to be a bit of an effort creating a NuGet package for each of the .dll files required for the application.

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)?

Update

Found a suggestion on SO. This post suggests transforming the .dll into a NuGet package then publishing the package to the Azure DevOps Nuget feed.

This seems to be a bit of an effort creating a NuGet package for each of the .dll files required for the application. Moreover, I can imagine making a ton of mistakes when setting up the individual pipelines (there are a few class libraries that need to be taken care of).

Is the approach above the only option available?

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).

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)?

Update

Found a suggestion on SO. This post suggests transforming the .dll into a NuGet package then publishing the package to the Azure DevOps Nuget feed. Is that the only option, since it seems to be a bit of an effort creating a NuGet package for each of the .dll files required for the application.