Tag Archives: design

DRY vs Coupling

While reviewing my previous post another great discussion, which may arise from paying attention to your references, came to my mind: Don’t Repeat Yourself (DRY) vs Coupling. Each time you add a new reference it means that you want to … Continue reading

Posted in .NET, Design, Technical | Tagged , , , , , , , | Leave a comment

Using ReSharper for Assembly References Diagrams

A few posts back I talked about how we can use the assembly references to enforce consistency and separation of concerns (here and here are the old posts). I argue there that if we derive from the architecture the assemblies of … Continue reading

Posted in .NET, Design, Technical | Tagged , , , , , , , | Leave a comment

Localization Concern

Localization (also known as internationalization) is one of the concerns that is most of the times overlooked when we design an application. We almost never find it through the requirements, and if we do or if we ask about it, … Continue reading

Posted in .NET, Design, Technical | Tagged , , , , , | Leave a comment

Dependency Inversion and Assemblies References

In my last posts I have talked about using assembly references to preserve critical design aspects. In Enforce Consistency with Assemblies References I talk about how we can use references to outline the allowed dependencies in code and how to … Continue reading

Posted in .NET, Design, Training | Tagged , , , , , | Leave a comment

Repository Implementations

In my previous post I have presented a way to separate your data access from the business logic, when a relational database is used. I have shown another implementation of the well-known Repository pattern. Since Martin Fowler described it in … Continue reading

Posted in .NET, Design, Technical | Tagged , , , , , , , , | Leave a comment

Separating Data Access Concern

In our days most of the applications that have a relational database as storage, use an ORM to access the data. The ORM (Entity Framework, Hibernate, etc.) does most of the data access implementation. Many of them have a modern … Continue reading

Posted in .NET, Design, Technical | Tagged , , , , , , , , , , | Leave a comment

Disposable Instances Series

In the past few weeks I have published a set of four posts that deal with disposable instances. These posts describe in detail a working implementation that automatically disposes all the instances that are no longer needed, in a deterministic … Continue reading

Posted in .NET, Design, Technical | Tagged , , , , | Leave a comment

Disposing Instances when Using Inversion of Control

In the last few posts I have written about how to deal with IDisposable instances when using Dependency Injection. In the Who Disposes Your Repository I talk about the possibilities and challenges of disposing a repository which is injected. Then in the … Continue reading

Posted in .NET, Design, Technical, Training | Tagged , , , , | Leave a comment

Extending Unity Container for IDisposable Instances (2nd approach)

In my previous blog post I detailed an approach of making the Unity Dependency Injection Container to automatically call Dispose() on all the IDisposable instances it builds and injects. The implementation described there, makes use of custom lifetime managers and it … Continue reading

Posted in .NET, Design, Technical, Training | Tagged , , , | Leave a comment

Extending Unity Container for IDisposable Instances (1st approach)

A few weeks ago, in my blog post ‘Who Disposes Your Repository’ I wrote about the challenges of implementing an IDisposable repository, which takes full advantage of the deferred execution of the IQueryable<T> and, which is being injected through Dependency Injection … Continue reading

Posted in .NET, Design, Technical, Training | Tagged , , , | Leave a comment