Applying S.O.L.I.D. Principles in Microsoft .NET/C#

Play Applying S.O.L.I.D. Principles in Microsoft .NET/C#
Sign in to queue


Have you heard of the S.O.L.I.D. principles? You have? Good! Can you explain them all? And make your colleague understand them, and why they are useful? Okay, in that case, you should stay away from this session. If not, you should definitely go to this session, as it goes through each one of the principles, explaining what it means and why it is useful. You will also be shown C# code examples explaining how they help you, and what problems you solve by adhering to them.



Session Type:





Hall 8.0 Room B2



Right click to download this episode

The Discussion

  • User profile image

    I'm not very sure if I have understood you (a) ... but not totally agree with you that you should apply each principle from the previous one although it would be a good idea... ;).

    1) If you are doing TDD/BDD/... when you are starting to code you aren't following those principles/good practices/patterns (although you should)... and at the end of the day when you are refactoring it is posible that the way to get your SOLID code is LIDSO...

    2) S.O.L.I.D are a series of principles/good practices/patterns you may follow and the order you follow doesn't matter.

    I believe that SOLID sounds better than LIDSO or DISLO and so on... and I don't think that you should follow the order SRP, OCP, LSP, ISP and DIP in order to code. The order doesn't matter because while you are writing the code come to your mind (or at least it what happens to me). Is when I'm refactoring my code when I think about better ways to implement it and at this time is when I start to apply SOLID principles.

    Congrats because of your great explanation!! It has been very funny! [H]

  • User profile image


    Thanks for this video,
    Where is source files?

    Thanks in advance.

Add Your 2 Cents