How we do MVC – View models 👀

The ViewModel is a central aspect of our MVC architecture. 🌞

One of the first dilemmas facing MVC developers is to decide what the “M” in MVC means in ASP.NET MVC. 🤔

In Rails, this is fairly clear, the M is ActiveRecord (by default). 🌍

But in ASP.NET MVC, the “M” is silent❗️

Its out-of-the-box architecture offers no guidelines nor advice on what the M should be. ⚙️

Should it be an entity❓
Data access object❔
DTO❓
Something else❔

https://t.me/pgimg/91

[ Website ] : http://bit.do/mvvm

〰〰〰〰〰〰
#AspMvc #CleanCode #BestPractices
@ProgrammingTip

ASP.NET MVC Best Practices and Guidelines ✅

While most developers were used to WebForms and Microsoft's stock controls, when developers moved to ASP.NET MVC, a number of developers were shocked because there wasn't enough meat for this to be a full-featured release. 🤓

Some of the guidelines list below are based on my own experiences over the years since 2008. 📆

https://t.me/pgimg/93

[ Website ] : http://bit.do/aspbst

〰〰〰〰〰〰
#AspMvc #CleanCode #BestPractices
@ProgrammingTip

Getters/Setters. Evil. Period. 👺

There is an old debate, started in 2003 by Allen Holub in this Why getter and setter methods are evil famous article, about whether getters/setters is an anti-pattern and should be avoided or if it is something we inevitably need in object-oriented programming. 🕸

The gist of the following text is this ✨ : getters and setters is a terrible practice and those who use it can't be excused. ❌

Again, to avoid any misunderstanding, I'm not saying that get/set should be avoided when possible. No. I'm saying that you should never have them near your code. 🚫


https://t.me/pgimg/163


[ Article ] : kutt.it/gset

〰〰〰〰〰〰
#BestPractices
@ProgrammingTip

Framework Design Guidelines: Conventions, Idioms, and Patterns for Reusable .NET Libraries - 2nd Edition 📕

Author 🖊 : Krzysztof Cwalina

〰〰〰〰〰〰
#Book #DotNet #BestPractices
@ProgrammingTip

Objects Should Be Immutable 🤫

In object-oriented programming, an object is immutable if its state can’t be modified after it is created. 🤞🏻

In Java/C#, a good example of an immutable object is String.✅
Once created, we can’t modify its state. We can request that it creates new strings, but its own state will never change. ❌

However, there are not so many immutable classes in JDK. Take, for example, class Date. It is possible to modify its state using setTime(). 🕒

This is an incomplete list of arguments in favor of immutability ⚡️:

• Immutable objects are simpler to construct, test, and use
• Truly immutable objects are always thread-safe
• They help to avoid temporal coupling
• Their usage is side-effect free (no defensive copies)
• Identity mutability problem is avoided
• They always have failure atomicity
• They are much easier to cache
• They prevent NULL references, which are bad

Let’s discuss the most important arguments one by one. 🌀


https://t.me/pgimg/178

[ Article ] : kutt.it/immtb

〰〰〰〰〰〰
#BestPractices #DesignPatterns
@ProgrammingTip