Cloud as a Story - Vunvulea Radu

Last week we had in Cluj-Napoca last ITCamp event in Cluj-Napoca for this year - Winter Code Camp . For this events we decided to talk about the new version of ASP.NET and MVC. Because it was an afternoon event, we decided to have only two sessions where the following subjects were touched: What new in ASP.NET MVC, 5 Visual Studio 2015 and Web Tooling Setting up a SPA using Aurelia with Typescript in Visual Studio   More information about agenda and original announcement can be found here: http://vunvulearadu.blogspot.ro/2015/11/winter-itcamp-event-in-cluj-napoca.html From the number of participants, we were impressed. There were more than 120 attendees. We had to open another room for overflow . First time in my life when had this situation and to use an overflow room. It was a big WOW from our side and we promise that we will organized another event in first 3 months of 2016. At the end of this post, I shared with you some pictures from events.   Thank you for participat

In this post we will see what we need to do when we want to add a new user on our Visual Studio Online project, but we end up with errors like 401 403 TF400813 Let's start from the assumption that we are the administrator on VS Online. We added a user a few days ago on our project, with the same rights like other users. Even if we added the user, he is not able to access our project. It is well known that sometimes we need to wait a few hours until the rights and changes are propagated, but it never takes more than 12-24h. In this moment we need to ask yourself what is different. There are times when the change propagation freeze and you need to remove and add the user again. We sad that this might be possible and let's remove the user and add him again to VS Online and to our project. After removing the user we observed that we cannot find anymore the given account, even if it was a LIVE account. This was strange and odd. We remembered that a few days ago we had a

Playing with Visual Studio Online is sometime like playing with fire. It works great 99.99% of time, but from time to time you have a problem and you cannot find easily support. In this post we will talk about what you need to do when you want to add a new user and you end up with 401 or 403 error code. This days we wanted to add a new user to our Visual Studio Online project. In the portal, when we wanted to add the new user we ended up with the following error: "AAD guest users are not allowed to search in AAD" This happens when we want to add a new user to a group. Even if we were administrators, we were not able to do any change. This was something new for us, 2 weeks ago everything was fine. What happen in the last period of time. Our company integrated our own AD with Azure AD. To be able to use your administrator's rights on Visual Studio Online you need to be added to Azure AD (even if you have a LIVE account) as Member. By default you will be Guest. Pow

A few days ago Azure team announced that they will retire Azure Managed Cache and In-Role Cache will not be supported anymore. In this post we will take a look on why this is happening and what could this decision affect us. The official announced can be found on the following link:  https://azure.microsoft.com/en-us/blog/azure-managed-cache-and-in-role-cache-services-to-be-retired-on-11-30-2016/ Azure Managed Cache Services is a service that allow us to use a cache solution as a service. From our application, we would only need a 'connection string' to the cache services. Using this information we could store or retrieve any kind of content from cache. In-Role Cache allows us to cache content in the memory of our role (web/worker role). A part of the memory can be configured to be used for cache. The data that is cached in In-Role Cache is synchronized automatically between multiple instances of our role. This two cache solutions offered by Microsoft Azure are used very