Skip to main content

[Post Event] ITCamp 2016, Cluj-Napoca

The 6th edition of ITCamp conference took place in Cluj-Napoca at the end of this week. For 2 days, more than 600 people were connected to the latest software development and devops trends.
More than 40 speakers had offered high quality content to ITCamp attends. Having 5 tracks in parallel is awesome, but sometimes is so hard to decide to what session to attend.

There were a lot of interesting topics that were presented and discussed during this two days. From Security and Development Best Practices, to .NET Core, Cloud and IoT. I really felt that IoT era already started during the sessions where many speakers had with them different smart devices that can improve our life.
The second day of ITCamp brought for the first time in Cluj-Napoca and Romania Microsoft HoloLens. This glasses are like the one from Start Trek that not only creates a virtual reality like other devices on the market, but offers to the user an augmentative reality. I had the opportunity to test them and it was amazing.
You can find pictures from the event at the end of this post.

This year at ITCamp I was invited to speak about Service Fabric and Microservices. More details about my session and slides can be found below. Feel free to contact me if you have any question related to this topic.

Topic: Azure Microservices in Practice
Abstract: In this session we will take a look on Azure Service Fabric and how we can create a web application using ASP.NET Core and microservices. During the presentation we will create a web application that will be hosted in Azure Service Fabric and use the most important capabilities of Azure Service Fabric.
Slides:
  

Comments

Popular posts from this blog

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

Azure AD and AWS Cognito side-by-side

In the last few weeks, I was involved in multiple opportunities on Microsoft Azure and Amazon, where we had to analyse AWS Cognito, Azure AD and other solutions that are available on the market. I decided to consolidate in one post all features and differences that I identified for both of them that we should need to take into account. Take into account that Azure AD is an identity and access management services well integrated with Microsoft stack. In comparison, AWS Cognito is just a user sign-up, sign-in and access control and nothing more. The focus is not on the main features, is more on small things that can make a difference when you want to decide where we want to store and manage our users.  This information might be useful in the future when we need to decide where we want to keep and manage our users.  Feature Azure AD (B2C, B2C) AWS Cognito Access token lifetime Default 1h – the value is configurable 1h – cannot be modified

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine: threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See http://go.microsoft.com/fwlink/?LinkId=260882 for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration: TeamCity .NET 4.51 EF 6.0.2 VS2013 It see