How do you feel after reading a few articles about CQRS (Command Query Responsibility Segregation)? Confused?!
The good news is that's not your problem.
CQRS is a simple concept, but usually is presented side by side with other patterns creating the perception that CQRS requires a ton of elements to work.
This post pretends to demonstrate that CQRS can be a simple concept that can evolve according to your needs.
When you want to send emails from .net applications how do you do it?
Do you create an instance of StringBuilder and start adding texts?!
And when you want to format the body as HTML? How do you do it?! A bigger string?!
And if you could write your templates as plain text and still be capable to inject values like names, dates or other values?
The good news is that you can and you have a good old friend to help you: T4 Templates.
Let's see how to do it.
Do you have a wine cellar at home?!
Nothing too big, but the sufficient number of bottles to lose control?!
Do you really know what you have in your cellar?
This post wants to help you solve those problems, and manage your home cellar with an amazing and free tool.
We are bringing to Oporto the 7th Meeting of NetPonto Community. The meeting will take place at Instituto Superior de Engenharia do Porto (ISEP) at 26 September 2015.
09:45 - Check-in
10:00 - SOLR in .NET - Super Solid solution for a Super Fast Search - Pedro Neves Rosa
12:00 - The Future of Web Applications - ECMAScript vNext and others - Ricardo Brandão
13:30 - Closing Panel
SPOILER ALERT: This text contains opinions from the author about smartphones.
I'm a huge fan of Windows Phone since the early days and I have been using it since 2011. I followed the growing and I struggled with all the limitations in past years.
Until the last month I'd never used an Android Phone or an iPhone as my personal phones. I've been playing with them in work or with family phones, and I have to honestly say that I never fall in love for them. But I need to refer that I'm not a hater of them, I respect both Operating Systems.
I can see their pros and cons and I try to stay away from those fanboy discussions (usually I'm the guy that they will make fun because for my friends I'm the only person in the country with a Windows Phone).
In the last month, I noticed that the camera button of my Nokia Lumia was a little loose and I decided that was time to send it to repair. I needed a substitution phone and I decided to give a try to Android because I'm a kind of disappointed with the Nokia hardware quality and I was really curious to try a different operating system. I've faced the experience with an open heart and really expecting to be surprised.
I managed to get a Vodafone Prime 6, it's not a flagship product but it's a cool phone and I used it during a month. Here I will explain what I loved in Android and what I missed from my Windows Phone.
*I want to point out that I won't compare hardware features. *
Are you fighting with the path length of your Node.js projects?
If you are using Microsoft Visual Studio to development, I bet you do. If you don't, you will (this isn't any curse that I'm throwing at you)!
Windows has the "Maximum Path Length Limitation" that is terrible for Node.JS projects.
"The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters."
As you know, when you install a package in Node.js, the npm will place the dependencies under the package folder. This process is recursive for each package, so you can easily overcome the path length.
Unfortunately, there's no silver bullet to fix it (I'm not a Node.js guru, so please let me know if I'm wrong), but we can follow some tips to deal with it.
We are bringing to Oporto the 6th Meeting of NetPonto Community. The meeting will take place at Instituto Superior de Engenharia do Porto (ISEP) at 11 July 2015.
09:45 - Check-in
10:00 - ASP.NET VNext, now in Mac! - Bruno Lopes
12:00 - Building applications with Xamarin Forms - Rui Marinho
13:30 - Closing Panel
I had the pleasure of write an article to the Revista PROGRAMAR, a Portuguese collaborative magazine about programming. I’m glad with my first article for a magazine and especially because, I'm side by side with people that I admire like Paulo Morgado or Sara Silva, for instance. This was an amazing experience and I want to share with you the result of it.
In March, Microsoft announced an improvement in his services by introducing the new Azure App Service. This service covers the “oldest” Websites, now named as Web Apps, the Azure Mobile Services, now, Mobile Apps, and introduce new capabilities as Logic Apps and the API Apps. This article talks about the last one. The question is: What’s the reason to create an API App, and not a Web API in a Website? This question can be easily answered, analysing the feature list, for example:
- Access Control using Azure Active Directory or OAuth services, as Facebook or Twitter;
- Fast integration with the Swagger Framework;
- Easy integration with Logic Apps;
- Private gallery of APIs, enabling us to provide APIs to the other members of the organization;
- Automatic generation of an SDK for our API.
In this article we will see, how to create an API, publish in our subscription and create an SDK to consume it.
In the last week I attended to the Agile Portugal 2015, an amazing event that gathers the agile community. I had the opportunity to listen excellent speakers as:
The event was amazing, and I want to share with you the main lessons that I learned.
Recently I was playing with API Apps, from the new Azure App Service when I faced the following error: