So, currently I’m working on a brand-new project involving variety of services being run on Service Fabric cluster in Azure. I’ve never had anything to do with Service Fabric (except for one, short hackathon) before, nor have any of my team mates. For the last couple of weeks, we’ve been struggling to make good architectural choices for the platform we’re still learning about. For the last few days we were working on a service that on certain triggers will populate Redis cache with certain sets of valu...

Kiedy potrzebujemy użyć jakiegoś ORM’a (Object – Relational Mapping) w naszym projekcie, z reguły pierwsza myśl jaka przychodzi nam do głowy to Entity Framework. Dzięki temu narzędziu w bardzo prosty i szybki sposób jesteśmy w stanie skonfigurować połączenie z naszą bazą danych i odwzorować nasze tabele w projekcie. W najnowsze...

"The code that a computer can understand can be written by anyone. A good programmer writes code that people can understand."

Welcome to the twenty-first episode of my course “Becoming a software developer” in which we will use MongoDB which is a NoSQL database for storing the data of our application.

Parę tygodni temu Microsoft przedstawił wersje robocze „Application Architecture Guidance”, czyli poradników dotyczących architektury aplikacji budowanych przy wykorzystaniu narzędzi Microsoftu. Gratka dla każdego .Netowca.

Welcome to the nineteenth episode of my course “Becoming a software developer” in which we will gracefully handle the exceptions and extend logging services with NLog.

Written by Dawid Sibińskion Today we’re going to see how to manage (keep and restore) state of Activities in Xamarin.Android application in order to keep the app consistent and reactive for configuration/state changes. Why to keep and restore Activity’s state? As I already described in my post about Android Activities, the OS may react to some “constant” state changes by calling lifecycle methods during Activity’s life, which may be overridden by the programmer in order to take some additional a...

Welcome to the eighteenth episode of my course “Becoming a software developer” in which we will finalize the basic CRUD for the Driver type, implement extension methods for the repository and build custom middleware in order to deal with exceptions.

Written by Dawid Sibińskion In the 3rd post from SQLite-Net Extensions series we are covering the last type of relationship – one-to-many (and the opposite – many-to-one). One-to-many, many-to-oneOne-to-many relationships are used in general for parent-children or whole-elements relations. Classic examples are: bus and passengers, document and elements etc. One-to-many relationship means that the one-end entity knows about its children and many-end entity has a reference (foreign key) to its pa...

Written by Dawid Sibińskion In this second short post from SQLite-Net Extensions series, we’re going to see how to create one-to-one relationships using this tiny ORM. One-To-One This is the simplest type of database relationship. An example could be vehicle and registration certificate – each vehicle has one and only one registration certificate, and one registration certificate is associated with one and only one vehicle (excluding some extraordinary law rules in other countries that I don’t k...