[Post Event] Peak IT 006 - Brasov, May 2024

In the middle of May, I had the opportunity to participate in the Peak IT Conference as a speaker and panel moderator. With over 400 attendees, 48 speakers, and 4 streams, the Peak IT Conference offers the attendees 3 amazing days.

The conference was a treasure trove of well-organized sessions, networking opportunities, and, of course, coffee. Andrei Danila delivered one of the standout sessions, titled ' There is light at the end of the tunnel. ' This session, among the best I've seen in recent years, provided invaluable insights for startups and highlighted key areas of awareness.

During the conference, I had the opportunity to deliver a session related to Cloud Repatriation and talk about the future of Microsoft Azure and . NET. You can find more about the content that I delivered below:

Cloud (re)patriation and Hybrid Cloud: The cloud has revolutionized how businesses operate, providing agility, efficiency, and scalability. However, in recent years, cloud repatriation has emerged as a trend in which businesses are moving data or workloads back to on-premises. Join this session to learn more about the pros/cons and concerns of cloud repatriation.

.NET and Cloud Development 2024 Trends: We invite you to a roundtable discussion on .NET and Cloud trends. The panel will explore these trends. Your insights are not only welcomed but essential to the dialogue.

Comments

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(

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

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

Cloud as a Story - Vunvulea Radu

Search This Blog