Installed Visual C++

[Jessica Wilson]

Welcometo Visual Studio 2019! In this version, it's easy to choose and install just the features you need. And because of its reduced minimum footprint, it installs quickly and with less system impact.

The latest release of Visual Studio 2019 that is hosted on Microsoft servers. To install this version, select the following button and then choose the edition you want. The installer downloads a small bootstrapper to your Downloads folder.

The latest release of Visual Studio 2022 that is hosted on Microsoft servers. To install this version, select the following button and then choose the edition you want. The installer downloads a small bootstrapper to your Downloads folder.

If you downloaded a bootstrapper file, you can use it to install Visual Studio. You need administrator permissions. The bootstrapper installs the latest version of the Visual Studio Installer. The installer is a separate program that provides everything you need to both install and customize Visual Studio.

If you receive a User Account Control notice, choose Yes. The dialog box asks you to acknowledge the Microsoft License Terms and the Microsoft Privacy Statement. Choose Continue.

For example, choose the ASP.NET and web development workload. It comes with the default core editor. That editor includes basic code editing support for over 20 languages, the ability to open and edit code from any folder without requiring a project, and integrated source code control.

At any time after installation, you can install workloads or components that you didn't install initially. If you have Visual Studio open, go to Tools > Get Tools and Features, which opens the Visual Studio Installer. Or, open the Visual Studio Installer from the Start menu. From there, you can choose the workloads or components that you wish to install. Then, choose Modify.

If you don't want to use the Workloads feature to customize your Visual Studio installation, or you want to add more components than a workload installs, you can install or add individual components from the Individual components tab. Choose what you want, and then follow the prompts.

By default, the installer program tries to match the language of the operating system when it runs for the first time. To install Visual Studio in a language of your choosing, choose the Language packs tab from the Visual Studio Installer, and then follow the prompts.

You can select a different drive for Visual Studio IDE or Download cache only when you first install Visual Studio. If you already installed it and want to change drives, you must uninstall Visual Studio and then reinstall it.

If you installed Visual Studio on your computer before, you won't be able to change the Shared components, tools, and SDKs path. It appears greyed out. This location is shared by all installations of Visual Studio.

In the search box, enter the type of app you want to create to see a list of available templates. The list of templates depends on the workloads that you chose during installation. To see different templates, choose different workloads.

You can also filter your search for a specific programming language by using the Language dropdown list. You can filter by using the Platform list and the Project type list, too.

In the template search box, enter the type of app you want to create to see a list of available templates. The list of templates depends on the workloads that you chose during installation. To see different templates, choose different workloads.

I have a large Visual Studio 2010 VB solution, targeting the .NET Framework 4.0 which opens and works just find on numerous Visual Studio 2010 installations - except one. The 'error' (more a message) when opening the solution says:

The VB project is targeting '.NETFramework,Version=v4.0", which is not installed on this machine. You must download this framework in order to open and build this project. In order to proceed, you must select an option below.

What worked temporarily was when I used a .NET Framework removal tool in order to remove all traces of the .NET Framework 4.0 from the machine (including the registry) and then installing the .NET Framework 4.0 again. However the error has returned.

I'm not sure if this is a problem with some .NET Framework 4.0 file corruption, something within Visual Studio or simply that Visual Studio cannot find the .NET Framework 4.0. (I have found several possible 'explanations' but nothing that resolves this issue.

I solved this issue for myself by downloading the appropriate Developer targeting pack. I made the mistake of trying to download the Runtime one, which apparently does not include the Visual Basic plug-in that you need.

update or reinstall the framework in question. run visual studio setup. click restore to defaults. will find all installed frameworks and not modify or remove plugins or liscenses.Even kept my settings.

I went to properties and chose the framework 3.5 and the errors went away. I do have the problem that although the 4.0 problem is installed on my computer, Visual Studio can't find it, but I am not using any 4.0 specific functionality, so this works for now. If I figure out why the 4.0 framework is not detectable, I'll update this post with the fix for it, too.

I had the same issue. My pc has the windows in a small SSD drive and user profiles and both Program Files folders on another disk.I solved it by noticing that even I had changed the registry entries about Program Files folders location, the FW setup had still put some files on the default locstion. I copyed them to the right location and at last I have FW 4.0 again on the target frameworks

I was working on a vbs script which was suppose to refer to %PROGRAMFILES% system variable, and was annoyed that no matter which one used (64bit or the (x86)) I was getting to the Program Files (x86) folder. So I found that the registry entry ProgramFilesDir and ProgramFilesDir (x86) under

have the same value ("Program Files (x86)"), so intuitively change the non x86 value properly.And that is what messed up my VS 2010 instance.Rolled that setting back and now VS is fine, left with the vbs issue though ;)

I managed to resolve the issue by replacing the development machine with a new one. Not quite a resolution to the problem but it saved a lot of time uninstalling/reinstalling/repairing over and over again.

Your VS solution may have a project (or more) in it that reference something in the full .NET 4.0 profile, which you are likely to have on your development machines... except perhaps the one where you are having the problem. The .NET 4.0 Client Profile is definitely different, and doesn't support everything you might be needing.

Elsewhere I've seen: In VS 2010, the tag was changed to , and we no longer support "Full"; that's why you're getting the error. Until we fix this, you can just remove the tag from your project file, and the project should open properly.

In windows 10 by default has a version of .net installed that is built in (I think) so cannot be uninstalled (4.5? 4.7?), at least I think that's what's going on, I certainly cannot remove it via "uninstall" I click that and it just stays in the list (4.5 that is). So my old answer, above, no longer works.

Fix was to uninstall the Windows SDK, then temporarily spoof that version 4.7 was not installed. Then install the SDK. Now VS 2010 express loads my C++ projects again (I presume what it did was install .net 4.0 successfully). Either the offline ISO or web version seem to work with this.

Tip: Setup will add Visual Studio Code to your %PATH%, so from the console you can type 'code .' to open VS Code on that folder. You will need to restart your console after the installation for the change to the %PATH% environmental variable to take effect.

The user setup does not require Administrator privileges to run as the location will be under your user Local AppData (LOCALAPPDATA) folder. Since it requires no elevation, the user setup is able to provide a smoother background update experience. This is the preferred way to install VS Code on Windows.

The system setup requires elevation to Administrator privileges to run and will place the installation under the system's Program Files. The in-product update flow will also require elevation, making it less streamlined than the user setup. On the other hand, installing VS Code using the system setup means that it will be available to all users in the system.

VS Code ships monthly releases and supports auto-update when a new release is available. If you're prompted by VS Code, accept the newest update and it will be installed (you won't need to do anything else to get the latest bits).

Windows is a popular operating system and it can be a great cross-platform development environment. This section describes cross-platform features such as the Windows Subsystem for Linux (WSL) and the new Windows Terminal.

On certain devices, editor scrolling is not smooth but laggy for an unpleasant experience. If you notice this issue, make sure you install the Windows 10 October 2018 update where this issue is fixed.

VS Code uses SVG icons and we have found instances where the .SVG file extension is associated with something other than image/svg+xml. We're considering options to fix it, but for now here's a workaround:

3a8082e126