---
title: "Comment by For sell Mx on \"Step-by-Step Approach to Use Onion Architecture in .NET\" | Hashnode"
description: "I recently refactored a legacy service using this layered approach, and your step-by-step breakdown perfectly captures the initial hurdle of setting up those pr"
url: "https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38/comment/69d6868c870fa71e3d441a5b"
---

[Discussion](https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38)

Comment [Step-by-Step Approach to Use Onion Architecture in .NET](https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38)

[For sell Mx](https://hashnode.com/@mxsell)

[Apr 8](https://hashnode.com/posts/step-by-step-approach-to-use-onion-architecture-in-net/67e98fe33beb1a0497ba6e38/comment/69d6868c870fa71e3d441a5b)

I recently refactored a legacy service using this layered approach, and your step-by-step breakdown perfectly captures the initial hurdle of setting up those project dependencies. The clear separation you demonstrated for the Core and Infrastructure projects is exactly what made testing so much easier later on.