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:
Do you ever wanted to execute code after your Angular template is completely rendered?
This post is the answer of how you can accomplish that.
This a simple tip, but I believe that can be really useful.
I recently started moving some databases that I have in the old Azure SQL Database Web/Business model. I started it with a good feeling. Let's face it, a guaranteed performance level is excellent. Nobody wants a noisy neighbor boring our database.
The downside, is that this shift brings new challenges and possible big troubles to the ones that already have systems in place. Everything has a price and in this case we call it Performance.
My AngularJS - Smart Float Directive post has been a post with a lot of traction, so I want to share another tip related to numbers in Angular.
This a kind of simple tip, but I believe that it can be really useful.
My smart-float directive works really fine in a desktop or laptop browser, but in a smartphone I want to take advantage of HTML5 number inputs and show to my users when they enter in the input, the "mini calculator keyboard".
How to accomplish it using angular?