ValueOf VS eShopOnWeb

As we anticipate advancements in C#, we can still forge ahead with crafting resilient applications by utilizing the "ValueOf" package as a provisional solution. Below, we create a validated EmailAddress class leveraging the package:

Probably better to use something like https://github.com/mcintyre321/ValueOf until we get a better solution (if we ever do). I agree that this is a pitfall.

The problem you’re describing here I think is ‘primitive obsession’, and the solution you’ve described is I think essentially a value object. This library might be useful https://github.com/mcintyre321/ValueOf

It lacks compile-time validation (though an analyzer that at least detects validation errors in the constructor should be fairly easy; more complicated flow control cases are probably hard), but at runtime, https://github.com/mcintyre321/ValueOf would let you do that.

If you want to wrap a small number of properties in a type to avoid primitive obsession, consider using ValueOf.

You might be able to create a wrapper type with something like ValueOf.

I good library I've found for addressing this issue is https://github.com/mcintyre321/ValueOf

- https://github.com/dotnet-architecture/eShopOnWeb (a Microsoft example -- also includes the link to a recent livestream which provides an overview)

https://github.com/dotnet-architecture/eShopOnWeb for studying best practices

dotnet-architecture/eShopOnWeb: Sample ASP.NET Core 7.0 reference application, powered by Microsoft, demonstrating a layered application architecture with monolithic deployment model. Download the eBook PDF from docs folder. (github.com)

There is also https://github.com/dotnet-architecture/eShopOnWeb

A fully featured sample ASP .NET Core Application