As our lives move on, it has been hard to keep up with updates on our side projects so we hope we can explain you what has been happening.

As you may recall, one of our projects we mentioned here was Checklist, a simple checklist for developers of any platform whose main goal was to develop a platform in our behalf, while we would learn new tools and try others.

As time passed, we found other platforms that did the same (or sometimes even more) and the fact that some of us weren’t able to respect the deadlines, it was decided to stop its development.

But as people say ”when one door closes, another opens” and so we started a project called TourGo.

[Project] Checklist

As one of this blog’s main goals, “to promote development of custom projects to improve our skills as developers”, we are going to present you project “Checklist”.

What is it?

A platform that provides the users (developers), a to do’s list of best practices to be applied on the development of their projects.

A lot advanced programmers certainly have heard of this two big words, Dependency Injection (DI) & Inversion of Control (IoC). Mainly known as very desirable pattern for solutions on software projects because they enable a nice and clean architecture and loosely cloupling between the various software components.

But before I start giving a big speech about DI & IoC, first I’ll start with a pratical example, using C# (because Ninject was implemented for .NET), to explain what really are this big two words. Then I’ll talk about the practical application of Ninject, and the importance of these two patterns, and also give a little example on how to use the Ninject Extension MVC, to allow the usage of this two patterns on your ASP.NET MVC application. So let’s start with the example…

Tags , , , , , ,