Skip to main content

[PostEvent] ITCamp 2014, Cluj-Napoca

Last week, Cluj-Napoca hosted the 4th edition of ITCamp. More than 400 people participate to this premium conference. During the two days of the event, more than 30 speakers talked about Microsoft Stack, Architecture, Cloud, Development methodology and many more. For this two days we could say that Cluj-Napoca was the center of IT from Romania.
This was the first year when we had 4 tracks in parallel and there were moments where it was pretty hard to decide at which session to attend. Session like “Management of Fear”, “30 Tools for Modern .NET Web Development in 60 minutes”, “Code Quality through Application Software Infrastructure” or “The Battle for Success” made waves between attendees.
Special thanks to the core organization team (Mihai Tataran and Tudy-Tudor Damian). You made a great job this year. There were a lot of sponsors that sustained this event. I’m proud that iQuest was one of the Platinum sponsors.
This year I had the opportunity to do a workshop dedicate to Agile, oriented to practice. The main purpose of it was to see how we can resolve different issues that can appear in a team or company using Agile methodology (if is possible). Also, in the first day of the event I had a session related to redundancy over Microsoft Azure - Database and Public Endpoints redundancy on Azure. Even if we are on a cloud platform, we need to think on different solutions that would offer us redundancy and failover mechanism. Cloud is not managed by God.
ITCamp 2014 Summary: 400+ people, 34 speakers, 2 days, 4 workshops, 4 tracks, 28 sponsors, 6 media partners and a lot of good sessions.
See you next year!

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