Visual Studio 2019 Release Candidate (RC) now available

John Montgomery

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 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 ( and Visual Studio 2019 Preview 4 is available in the preview channel ( 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, 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!


Discussion is closed. Login to edit/delete existing comments.

  • Dean Jackson 0

    Is the new start window mandatory, or can it be turned off?
    I’m thankful there are some SSDT fixes in 2019, but it’s strange that the SSDT team doesn’t engage with the community at all, when Microsoft is all about engaging with the developer community.  Why don’t they interact at all…like have an active blog that tells what’s going on?
    Since the classic blue theme is still liked by many, will you make it available as a choice when using the Color Theme Editor…the optional themes can be downloaded here:

    • Petr Onderka 0

      You can turn the Start Window off in Tools → Options → Evironment → Startup.

  • Wil Wilder Apaza Bustamante 0

    Arrow navigation are broken now
    See video When I press arrow up/arrow button cursor disappears and focus jumps out of the window to random places top/bottom

    • Rajen Kishna Microsoft employee 0

      Hi Sergey, Could you use the Report a Problem tool in Visual Studio to file an issue for this so we can take a look? Thanks!

  • J. Daniel Smith 0

    Any chance of relaxing the Community license slightly so that enterprise developers can use Visual Studio instead of VSCode+WSL+GCC?

  • King David Consulting LLC 0

    I downloaded and installed Visual Studio 2019 RC version and had to enable the preview sdks usage by Tools–>Options –> Projects and Solutions –>.NET Core –> check Use preview of the .NET Core SDK. I guess the assumption was it would be enabled by default.

  • Felipe Pessoto 0

    I’m a big fan of TTD and looking forward to see it in Visual Studio.

  • 书架 朱 0

    Can Visual Studio 2017 be upgraded directly to Visual Studio 2019 RC?

    • Rajen Kishna Microsoft employee 0

      Hi, Visual Studio 2017 can not be upgraded to Visual Studio 2019 and will install side-by-side.

  • Lynd Trang 0

    How about the Visual Studio 2017, can we upgraded to 2019 or need to uninstall it after install VS2019 ?

    • Ravi UppaluruMicrosoft employee 0

      Hi Lynd,
          VS 2017 and VS 2019 can exist Side by Side (SxS) and you do not have to uninstall VS 2017 to install VS 2019. You can upgrade solutions/projects from VS 2017 to VS 2019. VS version itself can not be upgraded from 2017 to 2019. 

  • Kexy Biscuit 0

    So what’s the feature difference between Community and Professional edition now?

    • Rajen Kishna Microsoft employee 0

      Hi, the main difference between the two has always been the EULA and being able to use Community only when certain conditions are met (as detailed in the Visual Studio Community license terms) Visual Studio Professional 2019 will have the TFVC/Git and Code History CodeLens capabilities available, which are not available in Visual Studio Community 2019. Furthermore, Visual Studio Professional 2019 can be acquired as the Visual Studio Professional Subscription, which comes with a bunch of benefits like monthly Azure credits, access to Microsoft software for dev/test usage, training and support, and partner offers.

  • Rand Random 0

    Annoying scrolling behaviour here on this webpage, when enlarging the posted image. Here a video showing the issue: The issue happens with Edge.   Another issue, when I hit the submit button for this post the scrolling wen to the very top of the webpage. To Reproduce: 1. click on image 2. move mouse outside the image (to the bottom) 3. click to close the image 4. move the mouse = it will scroll to the end of the webpage   Another issue, when I hit the submit button for this comment the webpage scrolled to the very top. One more, while writing/editing this comment I used line breaks to format the message, after refreshing the page those line breaks are gone, is that as designed? In my opinion a WYSIWYG would be better, and not this. And once more, the font and line spaces changes when you press edit and cancel or save. So, yeah.. 

    • Nicole BruckMicrosoft employee 0

      Hi Rand, thank you for the screen recording and reporting these. I apologize for the unexpected behaviors and promise that we’re looking into it straightaway. If you see any other issues or have suggestions for where we can improve, please continue to share feedback.

  • Mike Diack 0

    Request for more information:Can the Visual Studio 2019 Preview / RC release notes, give details of what’s changed between Preview 3 and Preview 4 (aka RC) please?At the moment, there’s no detail at all as to what has changed since Preview 3?Just saying that Preview 4 is a “cumulative update” is hopeless.

  • Mike Diack 0

    There are significant graphical glitches (clipped text, warning icons with no explanatory text) in the upgrade window (e.g. upgrading a VS 2013 c++ code base to the v142 build toolset and SDK).Text is clipped/written on top of buttons. A ! exclamation icon on yellow with no explanatory text. I have raised feedback on this. Similarly, my long standing bug bear about the C++ background analysis failing to show up even the simplest memory leak via malloc or new, raised as a feedback item (with steps on how to reproduce it – basically do malloc and then forget a free), is bounced back as not enough info from the team. Sorry all, but:This release looks rushed and lacking polish at the moment.Most of the comments about the title bar have been ignored, yet it’s marked as done, and likewise the new blue theme which is purple (and the old shade of blue is not included as an “old blue” type theme).Looking at the volume of blog posts and comments about it, you could be forgiven that it was the only thing changed in this version!

    • Marian LuparuMicrosoft employee 0

      Thank you for submitting a ticket for the Upgrade dialog layout issue. For reference, we are currently tracking the issue here: 
      Regarding the C++ background analysis not showing a warning you expected – not all checks are on-by-default. You can change the ruleset being used for your project from Project Properties > Code Analysis (e.g. by switching from “Recommended Rules” to “All Rules” in the Ruleset dropdown)

    • Jamie YoungMicrosoft employee 0

      Hey Mike, sorry to hear you’re feeling that way, we’re not ignoring the comments on the title bar or theme. It’s been great to see the passion for these pieces from you and the community in general and we’ve been making measured steps each preview to fix the functional issues that have been flagged to us. There is more to do on both and we’re actively engaged in addressing all the feedback we hear. Please keep filing bugs and feedback!

  • Mike Diack 0

    Question re: MSDN documentation: When will the VS2019 specific documentation be online on MSDN?I tried looking at documentation relating to changes in VS 2019:(example: ) to look at the evolving state of compiler warnings. I then decided to try a VS2019 version by changing the last character to 9i.e. to find that page doesn’t exist.Likewise there are many other pages missing (e.g. Breaking changes etc.) If RC is now “go-live”, I’d expect there to be some MSDN documentation online to support it (even if it’s incomplete/tagged WIP). Similar example, try to find the MSDN list of C++ compiler options for VS2019. The same list as VS 2017 appears (dated 2016!) ….

  • Peter Hinz 0

    When trying to create a winforms app. You get this:
    No template could be found with the group identity ‘Microsoft.Common.WinForms’

    • Beth MassiMicrosoft employee 0

      Hi Peter, are you trying to create a .NET Framework-based WinForms app or .NET Core-based?

      • Digital Dog 0

        Same here. Same message. It’s a .NET Core WinForms project.
        .NET Core WPF project also doesn’t create – the message contains ‘Microsoft.Common.WPF’
        .NET Framework projects create successfully.

          • Huzaif superzaif 0

            I am getting the same error as above while creating WPF dotnet core apps. This worked fine with the Preview 3 build.
            The following version of dotnet core is installed:
            .NET Core SDK (3.0.100-preview-010184)

          • Anand C 0

            I have the same problem, though I have the latest .NET Core 3.0 preview installed…I think the Release Candidate (RC) is not ready for release…?

          • cine cone 0

            try this:
            dotnet new globaljson –sdk-version 3.0.100-preview-010184

          • Johann Nell 0

            Apart from using the latest SDK and doing above if neccesary, make sure “Use previews of .NET Core SDK” is enabled.
            Tools > Options > Projects and Solutions > .NET Core
            Note, the GUI designers for .NET Core Winforms are not available yet.

      • Ranjith K R 0

        Same here too. Wpf application in .net core is not creating the project. Error is “no template could be found with the group identity Microsoft.commom.WPF”

    • Wil Wilder Apaza Bustamante 0

      This comment has been deleted.

  • TBRMDEV --- 0

    No Express editions ? Then pls make Community totally free (including enterprise)

    • Pavel UstinovMicrosoft employee 0

      Community and Enterprise are 2 different editions. Community is free. You can check feature comparison between editions here:

  • Marcel Ratnam 0

    Are there any plans to release a x64 version of the IDE? The existing IDE has severe memory constraints for large solutions (over 150 projects).

    • Pavel UstinovMicrosoft employee 0

      Hi Marcel, how many projects in your solution? And what problem do you have opening it?

    • Pavel UstinovMicrosoft employee 0

      If you have problems opening more than 150 projects, please, feel free to send a feedback: “Help” –> “Send Feedback” –> “Report a Problem…”.

    • Jamie YoungMicrosoft employee 0

      Hey SuperCocoLoco, thanks for the comment on this! We met on the title bar and theme work yesterday and we’ve a plan in place to solve some the feedback we’re hearing around these items. We are actively working on both areas looking at all the changes that have been suggested from everyone here and on Developer Community. We’ll get these changes to you soon and (of course) please drop us a comment, feedback item or suggestion once you’ve seen them to let us know what you think. 

  • SuperCocoLoco . 0

    It is very curious to see how Microsoft abandons its own technologies in favor of others from third parties. Microsoft now develops Windows applications in Electron instead of using his own technologies in Visual Studio. And example is the unusable and disaster of Skype 8 that nobody wants to upgrage or use and Microsoft inhability to fix for years. Blogs are designed in WordPress instead of Microsoft technologies. Web engine in Edge/Windows 10 are now change by the Google Chrome due to Microsoft’s inability to develop or maintain a decent engine. Now Cortana is no more a Virtual Assistant (due to Microsoft’s inability to develop it) and is now a skill or a tool to use Amazon Alexa and Google Assistant (maybe Samsung Bixby in the future).   A lot of new Microsoft apps are developed by third party companies. Since 2012 all new features in applications they are of the style “new icons”, “emoticons added”, “cloud support”, “touch support”, “more cloud support”, “more touch support”, “new theme”, “combined title bar with menu bar”, “all caps menu” and many really necessary and widely used features have been removed, specially those not related to cloud, or related with all those who work locally or do not want to use the cloud. Microsoft is adding Skype 7 features to Skype 8 for more than a year and there are only two or three new features added in more than a year. What are Microsoft teams doing everyday at job hours? Testing Visual Studio 2019 Release Candidate, it seems to be more in alpha phase than in beta. Its also seems that Microsoft not use or develop in Visual Studio no more. Is it time to leave Microsoft’s ship? Microsoft is the first to do it.

    • Denis Trunin 0

      Thats a way how big corporation are working. They have a lot of money and very ineffective. But they can buy other startups 

    • Evgeny Vrublevsky 0

      It’s a good thing that Microsoft was cured from the “Not Invented Here” syndrome.

    • Yann Duran 0

      I’ve also noticed these two disheartening trends:
      1) Microsoft using pretty much anything OTHER than Microsoft products these days. Just today I was astounded to find that the VS installer is actually an electron “application”.
      2) So much time and effort seems to go into adding “new features” into new versions of VS that:
          a) pander to the lowest common denominator (ie the attempt to dumb everything down)
          b) are just visual elements that seem to be changed for the sake of changing them, so they can be added to the list of “new features”
      How are customers supposed to have confidence in Microsoft products/technologies when more and more we see Microsoft not using them?

  • R wing 0

    Nice news, but how to upgrade from prview 3 to rc ?

    • Rajen Kishna Microsoft employee 0

      Hi, as mentioned in the blog post, the previews are available in the preview channel and the RC is available in the release channel. These install side-by-side, so you can’t upgrade Preview 3 (or 4) to RC. You will be able to upgrade RC to the generally available version we will release at our launch event on April 2. Hope that helps clarify it!

      • Selma IkizMicrosoft employee 0

        Most straightforward way  is install a RC version, then uninstall the Preview 3.  

  • Nguyễn Liêm 0

    Will VS2019 Public Release support UWP when create new CrossPlatform project?

    • Daniel JacobsonMicrosoft employee 0

      Hi Nguyen. I’m not sure I fully understand your question. What kiind of CrossPlatform project are you referring to? 

  • Mike Diack 0

    Serious question – is anyone following up on the comments on this page?A number of people have made comments, both opinions and bugs and the silence has been mostly deafening…1) I raised some bugs (and have raised them as feedback items).2) People have commented on x64, themes, title bars etc.3) People have hinted (I’m not the only one), that the release of VS 2019 feels rushed to meet a time deadline rather than a quality standard/baseline.Case in point – you’d announced a release date before you’d even released the RC…4) I’ve raised issues about non existant documentation (release notes for Preview 4 are minimal), and lack of supporting MSDN docs now that the code is “go live”.And all there’s been is silence….. Anyone from Microsoft listening? If not, this suggests exactly why we’ve had the blue theme and title bar debacle – with MS marking the job as done, in spite of continued protestation from users.

    • Jamie YoungMicrosoft employee 0

      Hi Mike, we are listening 🙂 We are also definitely working on solutions to the feedback we’re hearing. On the title bar and theme work, we have been making measured improvements with each preview release (sorry to hear you think it’s a debacle) But we continue to listen and respond so thanks for opening up new tickets and issues, please keep at it.

      • Anthony CangialosiMicrosoft employee 0

        Hi Mike. When we release Visual Studio 2019 in April we are going to give you back the option to restore the title bar. You’ll find this in the ‘Preview features’ node under Tools->Options. Options under the Preview features node give users a way to restore the old experience for a period of time while we polish the new compact menu experience and learn from the experiences of a broader set of users.
        We continually work on improving startup and solution load time. The best way to for us to diagnose perf issues is to start with a feedback ticket where we can look at specific traces from your instance to help us improve VS.
        We’d like to hear more of your perspective on the UI and other changes. If you reach out to vsidefeedback_at_microsoft_dot_com we can setup a call to dig into your feedback and the  updates we’re thinking. You can also share a link to your feedback ticket at that email address and I’ll be able to loop in engineers from the team. 

  • Ferdinando Cavaliere 0

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

    • SuperCocoLoco . 0

      Yo need to go to the English Microsoft web page instead of other language Microsoft page, to see the all RC downloads.

      • Anatol Faller 0

        Thank you. So i’ll do that

      • Ferdinando Cavaliere 0

        Thank you. It is necessary to change the language of window 10 and use Edge because Chrome and Firefox are automatically redirected to the local Microsoft site 🙂

        • SuperCocoLoco . 0

          At bottom of the Microsoft web page there is an option to change the language in any browser and not redirect more to your local language or ask you before change.

        • SuperCocoLoco . 0

          At the bottom of the Microsoft web page you can change the web language without redirecting to your local Microsoft web page.

    • Anatol Faller 0

      The same as me…Only VS2017 and 2019 Preview appear.

    • Wil Wilder Apaza Bustamante 0

      This comment has been deleted.

  • Luis F. Mendoza Wittke 0

    Is there a RC 2019 Community version?

  • Reinielle Matt Erece 0

    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 0

      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 0

    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 0

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

    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 0

    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 0

      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 0

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

  • Lukas Fellechner 0

    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.

    • Daniel JacobsonMicrosoft employee 0

      Hi Lukas. When opening projects targeting older SDKs, you should see a dialog pointing you to install them from the web. Do you not see this dialog?
      For reference, you can install them here:

      • Lukas Fellechner 0

        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 0

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

  • Goetz Heller 0

    Actually, I’d like to download the RC for VS. Unfortulaty, being based in Germany, I’m redirected to the German download page which does not have a corresponing download link. Trying to use ‘en-us’ in the bowser usually helps – but not in this case. Do you have an advice how I could get to the correct link anyway?

  • McMonigle, David 0

    I’ve just updated my VS19 to the most recent release (RC2 from 3/12/2019). Getting this error when I’m trying to debug my app:
    “Error while trying to run project: Unable to start program ‘[myProgramPath]’
    A compnonent dll could not be found. If failures continue, try disabling any installed add-ins or repairing your installation”
    I’ve repaired twice, and do not have any extensions installed yet. This worked before my update.

    • Stan Blakey 0

      I am seeing a similar thing. Preview still works fine and I am not going to upgrade that until I hear this is fixed for the RC. It tells me the debugger is not installed. Repairing just uses up time with no effect. 

  • X Lin 0

    now it have chinese language?

  • Mike Diack 0

    Hi Just a question really. With Visual Studio 2019 (presumably version 16.0.0) now approaching RTM state (2 April 2019),and the recent release of version 15.9.9 of Visual Studio 2017….Is 15.9.9 the final update for Visual Studio 2017, or will updates for VS 2017 continue for a while after the release of VS 2019?Mike

  • Marcus Johnsson 0

    A shame I can’t try it (RC.2) – “license has expired” even though it’s the community edition and I am signed in with my Bizspark account (Enterprise-level). Trying to refresh it only states “We could not download a license…”. Odd, since both license and the “update license” works in my 2017-edition.

    • Marcus Johnsson 0

      RC.3 fixed this issue. Thumbs up!

  • Andrew Fisher 0

    Im currently trying to download the WDK that is compatible with VS2019. however the link in the wdk docs to the insider wdk seems to be a dead link
    what is the correct link? will the wdk be released on the same day as VS?

  • Mike Diack 0

    The release notes for VS 2019 RC3 / Preview 4.3 are very light on detail – which is the same issue I raised with RC2.
    In particular, RC3 features further C++ compiler and runtime library updates (_MSC_FULL_VER moved from 192027404 to 192027508), but this is not even mentioned in the RC3 release notes which only mentions about 6 changes!
    See: a wider list of changes than the “Top Issues” be published on each update please?

  • King Rince 0

    I downloaded and installed Visual Studio 2019 RC version. But there is something worng with this version.

  • B W 0

    Will VS2019 support Cordova projects?

  • B W 0

    Will Visual Studio 2019 support Cordova projects?
    I was using VS2015 with Ionic and tried to upgrade to VS2017.  It said that I needed to install task runner, which I did, but still could not get it to work.  Some of the forums said that perhaps my node.js was out of date.  I updated it and it still didn’t work and it also appeared to kill the ripple simulator so I can no longer utilize VS2013.  VS2015 gave me an error with something that it was using different versions of node.  They were both in essentially the same location, but one of them was in a sub-folder in the same path that was 64-bit.  I again studied the forums and took the advice of moving paths around to pre-append, post-append, and trying to trim paths, etc. without any luck.
    I installed VS2019 and there isn’t any support for Cordova with which I have a lot of time and effort into.  Somebody said that maybe Microsoft would be pushing Xamarin instead so I thought I would try that, but after doing a complete install of VS2019 along with anything that seemed remotely involved with mobile development or Xamarin, the example project will not compile and run while saying something about the namespace App not being found although I have not performed any edits to the sample project.  With VS2019 so close to being released, I wanted to at least check if Cordova will be supported before moving on to try another platform.  Thank you.

  • Honghui Ling 0

    How can I completely uninstall my VS2017 in my windows?

Feedback usabilla icon