Index

• Apologize
• Intro
• Design patterns

Apologize

I know I know... It's been a while without posting anything here, but it was for a good reason. I change my job more than a month ago and that (plus other things) got me entertained for some time. Apart I'm working on a personal project which takes most of my time but I promise I'll be back again really soon. Promised!

Intro

As I said before, I'm working in a new place and Amazon Web Services is heavy here. My aim is to post more about this wonderful service. A part from AWS, I'm also evaluating other PAAS providers like Heroku so you will find posts about this too.

Design patterns

I want to use this post as an index for some of the most important patterns defined in this book:

Please see here the complete list with some links to the ones I consider more useful:

1. Basic patterns
2. Patterns for high availability
3. Patterns for processing static data
4. Patterns for processing dynamic data
5. Patterns for uploading data
6. Patterns for databases
7. Patterns for data processing
8. Patterns for operation and maintenance
9. Patterns for networking

 

That's all for today, I wish you the best guys and stay tuned!

Introduction to Repository pattern

I found this tutorial from Mosh Hamedani pretty good explained. It will give you a very good understanding on how to create a repository pattern in your C# applications.

Learn when to use it (not in small apps, POC,..) and how to implement it properly. Understand DbSet and UnitOfWork, and which functionalities you have to define on them.

I know some of you are on holidays or coming back from some paradise... ok, that's not my case! Some people like me are keeping the world turning :P

Anyway... I would like to continue with more posts and today I bring you some more theoretical but really interesting if you never face those principles before. Listen closely:

SOLID is an acronym made up by Robert C.Martin to stablish the fundamentals in object-oriented programming. The main purpose is to get "low coupling" and "high cohesion" in our applications.All of this is mainly for the maintenance phase: to keep the code readable, maintainable and be able to create new functionalities.

Here we go again with a new tutorial to show you how to create a customized login using MVC 4 with Microsoft Visual Studio 2010. In this post, I will try to explain you how to develop different views, controllers, models, one database and of course, how all these elements interacts between them.

I have used MVC in older posts but I did not expend too much time explaing you how it works. MVC bornt as a software design pattern for implementing user interfaces. It provides a very useful architecture which splits between: the user interface (View), the logic and bridge between the user and the data (Controller) and finally the data (Model). Although originally developed for desktop computing, Model View Controller has been widely adopted as an architecture for World Wide Web. MVC 5 is the last template version released by Microsoft, but there are not too much differents with version 4. For the views, we are going to use Razor (CSHTML), the Microsoft dynamic view engine released in 2010. It is a new way to create your interfaces easier to use than ASPX, here you can check the differences beteween them.

Here below I show you all the steps to have your own login app:

• Create the solution in Visual Studio: first of all, we need to create our project in VS2010. If you can't find the ASP.NET MVC4 Web Application template as showed in the image below, probably you need to download from Microsoft site. Remeber you need Service Pack 1 of VS2010. Write a name for your project and press OK.

In the following window, select a Basic template, which contains an specific structure of MVC 4. The view engine should be Razor and optionally create a unit test project.