[Post Event] Visual Studio 2019 Launch Event

On April 2nd, 2019 Microsoft launched the new version of Visual Studio - VS 2019. In Cluj-Napoca, we organised a special event party where we broadcasted the event. Additional to this, we had 3 sessions where we presented the new features of VS 2019.
The sessions were focused on code review, remote debugging and writing code with the support of AI - Intelli Code.
I had the opportunity to talk about Visual Studio IntelliCode, a smart way how the IDE can learn about your code and the way how you write code. Using this information, the IDE can provide you with better recommendations related to what method you shall use taking into account the context.

Event summary:
What we'll do! Visual Studio 2019 Launch Party!
April 2nd, 2019 https://launch.visualstudio.com/
Visual Studio 2019 is here! On April 2nd we will broadcast a full day of awesome Visual Studio 2019 technical content to celebrate the launch and get you up to speed with all the new features.
Local agenda:

18:00 - 18:50 - Keynote (broadcasting, Scott Hanselman)
18:50 - 19:00 - Coffee and Snack Break
19:00 - 19:30 - Session 1: Mihai Tibrea | Upgrade your code reviews with VS2019
19:30 - 20:00 - Session 2: Radu Vunvulea | Power up your coding skills with AI inside VS2019
20:00 - 20:10 - Coffee and Snack Break
20:10 - 20:40 - Session 3: Daniel Costea | Visual Studio 2019 Remotely Debugging on Raspberry Pi 3 running Linux
20:40 - 21:00 - Networking

Don't miss this opportunity to find out more on what Visual Studio 2019 brings, and an awesome networking opportunity.

The event is hosted by Steelcase.

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(

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

Cloud as a Story - Vunvulea Radu

Search This Blog