---
title: Things I don’t like/understand/need to investigate
description: "I've always done this with a single solution and only one C# project. I have some doubts about how this will work with many C# projects, models, solutions, etc. For example, if a model has a dependency on the DLL…"
url: "https://ariste.info/dynamics365almguide/things-i-dont-like-understand-need-to-investigate/"
updated: "2024-08-25"
category: Legacy Guide / Add and build .NET projects
---

# Things I don’t like/understand/need to investigate

I've always done this with a single solution and only one C# project. I have some doubts about how this will work with many C# projects, models, solutions, etc.   For example, if a model has a dependency on the DLL but it's built before the DLL the build will fail. I'm sure there's a way to set an order to solve dependencies like there is for FnO projects within a solution.   Or maybe I could try building all the C#/.NET projects before, pack them in a nuget and use the DLLs later in the FnO build, [something similar to what Paul Heisterkamp explained in his blog](https://msdyn365fo.wordpress.com/2020/08/13/integration-of-nuget-packages-from-azure-devops-artifacts-into-the-dynalm-process/).   Anyway, it's your choice how to manage your C# projects and what solution fits your workflow the best, but at least you've got an example here 🙂

#### Subscribe!

Receive an email when a new post is published