Skip to main content

[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

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Can User Technical Profile Influence AI Architecture Decisions?

In the last few days, I ran a small experiment on Devin/Windsurf/Cascade, BMAD, and LLM-based architecture decisions. The initial concern was simple: if an AI coding assistant knows something about the user, for example, that the user is a Java developer or a .NET developer, can this information influence the architecture and technology stack that the AI will propose? This question is important because many companies are starting to use AI tools not only for coding but also for product discovery, architecture, documentation, and technical decision-making. If the AI is influenced by the developer's personal profile, the result may not be fully neutral. It may look like a business or architecture decision, but in reality, it may be partially shaped by the context of the person using the tool. The test was done using BMAD with Devin/Windsurf/Cascade. The scenario was a unified field service operations platform. The task was to let BMAD refine the product, define the architecture and s...

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...