Visual Studio 2019 Release Candidate (RC) now available

John

Today we’re sharing a Visual Studio 2019 Release Candidate (RC) – one of the final steps before general availability on April 2 at the virtual launch event. You can download the RC at visualstudio.com/downloads. As always, check out the release notes for the RC for all the details.

Explaining the Release Candidate

With this release, we’re introducing two product “channels”: the release channel and the preview channel. Starting today, Visual Studio 2019 RC is available in the release channel (visualstudio.com/downloads) and Visual Studio 2019 Preview 4 is available in the preview channel (visualstudio.com/preview). Both versions can be installed and used side-by-side and, right now, both channels contain the same bits.

Starting April 2, the release channel (RC) build can be upgraded to our generally available (GA) release, which will be ready for production use. The preview channel will continue to offer an early look at upcoming features, just as you’ve become accustomed to in Visual Studio 2017.

With today’s releases, we encourage you to install either Visual Studio 2019 RC side-by-side with your existing Preview installation, or start using the RC if you haven’t checked out the Preview releases. Visual Studio 2019 RC, as was the case with RCs of previous versions of Visual Studio, is a supported release and comes with a go-live license, but keep in mind that we’re still finalizing things and some workloads remain in preview until April 2. As mentioned, the RC can be upgraded to (GA) on April 2.

To help explain the two channels between now and GA (and beyond), we’ve put together this chart: Visual Studio 2019 product channels

Visual Studio 2019 Editions

On the download or preview page on visualstudio.com, you’ll find that you can now choose to download the Community, Professional, or Enterprise edition for either channel. Up until now, only the Enterprise edition was available in the Visual Studio 2019 preview channel. If you have an Enterprise license and would like to keep using Visual Studio 2019 Preview, you can simply update to Preview 4 in the Visual Studio Installer. For everyone else, you will have to switch to the edition you’re licensed for, either in the preview (Preview 4) or release (RC) channels. We recommend that you first install your licensed edition, and then uninstall the current Visual Studio 2019 Preview if installed.

Visual Studio Professional and Enterprise have different features. For example, Enterprise has IntelliTrace, Live Unit Testing, Embedded Assemblies for mobile apps, Real Time Architecture Validation, and others – features we continue to hone. A couple of items I’ll call out that are a bit newer in Visual Studio 2019 Enterprise:

  • The Snapshot Debugger, which enables you to debug production applications in Azure with minimal disruption, adds support for Azure Kubernetes Service (AKS) and Virtual Machine Scale Sets (VMSS).
  • In a future release of Visual Studio Enterprise 2019 will add a preview of Time Travel Debugging (TTD) integrated with the Snapshot Debugger. TTD enables you to record a process and then accurately reconstruct and replay the execution path. You can rewind and replay each line of code however many times you want, helping you isolate and identify problems.

For Visual Studio Community 2019, we’re making the References, Application Insights (Requests and Exceptions), and Test (Test Status and Tested By) CodeLens capabilities available, which were only available in Visual Studio Professional and Enterprise previously. This means that any Visual Studio 2019 user can can now get specific insights and information about the code, right within the code editor.

Reaching the home stretch together

We’re incredibly grateful to all the users who have been trying out Visual Studio 2019 since the first preview and have been giving us feedback every step of the way. While our generally available release on April 2 only marks the beginning of Visual Studio 2019 releases, we still encourage everyone to install Visual Studio 2019 RC and help us ship the best of Visual Studio to date. Let us know of any issues you run into by using the Report a Problem tool in Visual Studio or head over to the Visual Studio Developer Community to track your issue or suggest a feature.

I hope you all tune in online on April 2 for the virtual launch of Visual Studio 2019, which will be a fun celebration together with you, the community. You can also attend one of the many local launch events happening between April 2 and June 30. I hope you continue to share your feedback in future releases, so Visual Studio continues to be your development environment of choice. Thank you!

93 comments

Comments are closed. Login to edit/delete your existing comments

  • Ferdinando Cavaliere

    Where is the link for download teh RC ? In the pahe i see only de link for 2017 versions anche 2019 Preview 🙁

  • Reinielle Matt Erece

    We all know that the workloads in Visual Studio are verly large. So I hope that there will be somewhat of a smooth update from 2017 without having to install everything again. Would that be possible?

    • Rajen Kishna Microsoft employee

      Hi, Visual Studio 2019 installs side-by-side with Visual Studio 2017, so you will have to install it separately. However, you can export your current installation configuration from the installer and import it for your Visual Studio 2019 installation, so you automatically get the same components installed.

  • Guk Igor

    Hello all.
    I`m trying Visual Studio 2019.
    Studio installed on Mac OS Mojave. Just create empty Xamarin.Forms project. But I can not build it. There is error with such tracktrace:System.ArgumentNullException: Value cannot be null.
    Parameter name: path1
      at System.IO.Path.Combine (System.String path1, System.String path2) [0x000a0] in /Users/builder/jenkins/workspace/build-package-osx-mono/2018-08/external/bockbuild/builds/mono-x64/mcs/class/corlib/System.IO/Path.cs:126 
      at Xamarin.AndroidTools.AndroidSdk.get_SdkBuildToolsVersion () [0x00000] in /Users/vsts/agent/2.146.0/work/1/s/md-addins/MonoDevelop.MonoDroid/external/androidtools/Xamarin.AndroidTools/AndroidSdk.cs:304 
      at MonoDevelop.MonoDroid.MonoDroidProjectFlavor.OnGetProjectEventMetadata (MonoDevelop.Projects.ConfigurationSelector configurationSelector) [0x0005b] in /Users/vsts/agent/2.146.0/work/1/s/md-addins/MonoDevelop.MonoDroid/MonoDevelop.MonoDroid/MonoDroidProject.cs:1243 
      at MonoDevelop.Projects.SolutionItemExtension.OnGetProjectEventMetadata (MonoDevelop.Projects.ConfigurationSelector configurationSelector) [0x00000] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionItemExtension.cs:93 
      at MonoDevelop.Projects.SolutionItemExtension.OnGetProjectEventMetadata (MonoDevelop.Projects.ConfigurationSelector configurationSelector) [0x00000] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionItemExtension.cs:93 
      at MonoDevelop.Projects.SolutionItemExtension.OnGetProjectEventMetadata (MonoDevelop.Projects.ConfigurationSelector configurationSelector) [0x00000] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionItemExtension.cs:93 
      at MonoDevelop.Projects.SolutionItemExtension.OnGetProjectEventMetadata (MonoDevelop.Projects.ConfigurationSelector configurationSelector) [0x00000] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionItemExtension.cs:93 
      at MonoDevelop.Projects.SolutionItemExtension.OnGetProjectEventMetadata (MonoDevelop.Projects.ConfigurationSelector configurationSelector) [0x00000] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionItemExtension.cs:93 
      at MonoDevelop.Projects.SolutionItem.CreateProjectEventMetadata (MonoDevelop.Projects.ConfigurationSelector configurationSelector) [0x00000] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/SolutionItem.cs:875 
      at MonoDevelop.Projects.Project+<>c__DisplayClass151_0.<RunMSBuildTarget>b__0 () [0x00065] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/Project.cs:1384 
      at MonoDevelop.Projects.Project.RunMSBuildTarget (MonoDevelop.Core.ProgressMonitor monitor, System.String target, MonoDevelop.Projects.ConfigurationSelector configuration, MonoDevelop.Projects.TargetEvaluationContext context) [0x00270] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/Project.cs:1375 
      at MonoDevelop.Projects.Project.DoRunTarget (MonoDevelop.Core.ProgressMonitor monitor, System.String target, MonoDevelop.Projects.ConfigurationSelector configuration, MonoDevelop.Projects.TargetEvaluationContext context) [0x002a2] in /Users/vsts/agent/2.146.0/work/1/s/monodevelop/main/src/core/MonoDevelop.Core/MonoDevelop.Projects/Project.cs:1345 
      at MonoDevelop.MonoDroid.MonoDroidProjectFlavor.OnRunTarget (MonoDevelop.Core.ProgressMonitor monitor, System.String target, MonoDevelop.Projects.ConfigurationSelector configuration, MonoDevelop.Projects.TargetEvaluationContext context) [0x00117] in /Users/vsts/agent/2.146.0/work/1/s/md-addins/MonoDevelop.MonoDroid/MonoDevelop.MonoDroid/MonoDroidProject.cs:1783 
      at Xamarin.AndroidDesigner.MonoDevelop.IdeDesignerProject.DoRunTarget (System.String targetName, System.Threading.CancellationToken token, System.Collections.Generic.Dictionary`2[TKey,TValue] globalProperties, System.Collections.Generic.HashSet`1[T] propertiesToEvaluate, System.Collections.Generic.HashSet`1[T] itemsToEvaluate, System.IProgress`1[T] progress) [0x0018e] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Android/Xamarin.AndroidDesigner.MonoDevelop/IdeDesignerProject.cs:237 
      at Xamarin.AndroidDesigner.IIdeProjectExtensions.RunTarget (Xamarin.AndroidDesigner.IIdeProject ideProject, System.String targetName, System.Threading.CancellationToken token, System.Collections.Generic.Dictionary`2[TKey,TValue] globalProperties, System.Collections.Generic.HashSet`1[T] propertiesToEvaluate, System.Collections.Generic.HashSet`1[T] itemsToEvaluate, System.IProgress`1[T] progress) [0x00095] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Android/Xamarin.AndroidDesigner/IIdeProject.cs:97 
      at Xamarin.AndroidDesigner.DesignerProject.UpdateGeneratedAndroidResources (System.Threading.CancellationToken token, System.IProgress`1[T] progress) [0x00096] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Android/Xamarin.AndroidDesigner/DesignerProject.cs:1690 
      at Xamarin.AndroidDesigner.DesignerProject.InitializeIdeProjectAsync () [0x004bb] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Android/Xamarin.AndroidDesigner/DesignerProject.cs:196 
      at Xamarin.AndroidDesigner.AndroidDesignerService.LoadProjectAsync (Xamarin.AndroidDesigner.IIdeProject ideProject, System.String resourcesDir, System.String projectResourcesDir) [0x0005a] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Android/Xamarin.AndroidDesigner/AndroidDesignerService.cs:501 
      at Xamarin.Designer.Forms.XamarinStudioXamlPreviewerView.InitializeAndroidDesignerProject (MonoDevelop.Projects.DotNetProject androidProject) [0x00122] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Forms/Xamarin.FormsPreviewer.MonoDevelop/Xamarin.Designer.Forms/XamarinStudioXamlPreviewerView.cs:754 
      at Xamarin.Designer.Forms.Preview.AndroidXamlRenderer.EnsureSessionIsReady () [0x00081] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Forms/Xamarin.Designer.Forms.Preview/Android/AndroidXamlRenderer.cs:84 
      at Xamarin.Designer.Forms.Preview.AndroidXamlRenderer.RenderOneXaml (MonoTouch.Design.XamlRenderContext context) [0x0005d] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Forms/Xamarin.Designer.Forms.Preview/Android/AndroidXamlRenderer.cs:122 
      at Xamarin.Designer.Forms.Preview.AndroidXamlRenderer.RenderXamls (MonoTouch.Design.XamlRenderContext context, System.Threading.CancellationToken token) [0x000a5] in /Users/vsts/agent/2.144.2/work/1/s/Xamarin.Designer.Forms/Xamarin.Designer.Forms.Preview/Android/AndroidXamlRenderer.cs:201 

  • Narek Torosyan

    IMPORTANT WARNING FOR NON-AMERICAN VISITORS
    The “Download Visual Studio 2019 RC” button leads to a download page from where you can download VS2019 Preview 4, but not VS2019 RC.
    To download the RC, go to https://visualstudio.microsoft.com/thank-you-downloading-visual-studio/?sku=Community&rel=16. It installs a newer version of the VS Installer. From there it starts downloading the Community version. Close the install window if you want to download another edition (Available > Release)

  • Mike Diack

    Thanks to Jamie Young and others for responding.
    I do appreciate the responses. Personally I feel the title bar is nearly right as of Preview 4 (though it does behave oddly below approx 1080 pixels width).My other comment though about lack of MSDN documentation for an RC that is now tagged “go live” stands…What news is there on some online MSDN documentation specifically about VS 2019 eg breaking changes, commandline options etc.Also, is there any chance of a more detailed changelog for Preview 4 vs Preview 3 rather than the terse “cumulative update”?

  • Byron Adams

    I plan on installing vs2019 when it is finalized and soon after I would like to completely remove vs2017. My question is how does this work with the workloads and components?  I’m not sure what is shared and what belongs to just vs2017.  I don’t want to remove all the parts and break vs2019.I thought I heard once is that all I need to do is remove the vs2017 folder, is that true?

    • David Sterling (VS)Microsoft employee

      Hi Byron,
      If you install VS 2019 and install the same workloads/components, then remove your instance of VS 2017, we won’t remove any shared components that are needed in VS 2019.
      We keep an internal count of shared components so that we don’t accidentally break your VS 2019 environment.

  • Orides Pavaneli

    John, the download page does not show Visual Studio 2019
    RC! So, I can´t dowload the Community Edition.

  • Lukas Fellechner

    How can I install older Window SDK versions in VS2019? I am working on some open source libaray projects which target e.g. UWP SDK version 10.0.15063.0, but I cannot find them in the VS2019 installer. I would expect all SDK versions to be also available for VS2019 as optional components.

      • Lukas Fellechner

        Thank you, I have not tried this. I would have expected to see all SDK versions in the Visual Studio Installer as optioal components, like it was the case with VS2017. I will try the manual installation then, as you proposed.

  • Craig Lyall

    If you are licensed for VS 2017 Professional is this a free upgrade to VS 2019 Pro?