As mentioned in the Visual Studio 2015 IDE blog post, the setup experience of the product now provides more control to the user, for what does and doesn’t get installed. That blog post also talks about the rationale for this change and future direction for Visual Studio install experience. C++ is one of the features which is available as an optional install (not on by default). This ensures that non-C++ developers don’t have to pay the setup time and disk-space price for installing C++ bits that they don’t need. At the same time, C++ developers can still get the pieces they need.
A Note from Steve Carroll, VC++ Dev Manager
We’ve gotten a lot of feedback on this change and I wanted to address some common questions and concerns.
The most common question is why is only C++ being made optional. The C++ team made several engineering improvements over the course of the VS2015 release to improve our setup and so we were able to get our packages, compilers, and libs factored out in less time than other parts of Visual Studio. C++ is also very large because of the size of the libraries that we ship across many architectures and their matching PDBs. C++ also requires the installation of a Windows SDK. Many non-C++ developers don’t need any of this very large payload and so the overall VS install experience is significantly improved by this change.
The plan of record as mentioned in the IDE blogpost is to move most of Visual Studio to optional as we move forward. This is the first piece of that ongoing work. I want to reassure C++ developers that there is no de-emphasis of C++ development intended by this change whatsoever. Our telemetry and research tells us that C++ development usage in VS and the industry is accelerating, not shrinking. We continue to invest heavily in C++.
Did I mention we are hiring?
Thanks!
Steve
What’s Different
In Visual Studio 2015, C++ tooling is no longer installed by default. Instead, the C++ compiler, libraries, and project templates have been moved into an optional feature. Upon launching setup, you can choose a “Typical” or “Custom” install:
If you choose “Typical”, then you can’t use Visual Studio to develop in C++, because only managed languages and web development tools will be installed. To install the various components needed for desktop and mobile development in C++, you must choose “Custom” and manually select those items:
Note that the “Visual C++” node under “Programming Languages” is divided into three parts, so that you can opt not to install the tools you don’t need. We recommend that you read all the selectable items carefully before proceeding. Specifically:
- “Common Tools for Visual C++ 2015” includes the C++ compiler/linker toolset, libraries, and desktop (Win32) project templates.
- “Microsoft Foundation Classes for C++” includes the libraries and project templates required for building applications that use MFC. Note that this selection also includes support for MFC’s multi-byte character sets (MBCS), which replaces the separately downloadable installer that was required in Visual Studio 2013.
- “Windows XP Support for C++” includes the Windows 7.1 SDK, which can be used to build applications targeting XP with the v140_xp platform toolset.
A Note about Windows 8.1 and Windows Phone 8.0/8.1 Support
XAML compilation for Windows 8.1 and Windows Phone 8.0/8.1 has a dependency on “Common Tools for Visual C++ 2015” that is not automatically checked when selecting the Windows 8.1 and Windows Phone 8.0/8.1 option. If “Common Tools for Visual C++” is not already selected (we are looking at options to fix this in the short term), please do so when selecting the Windows 8.1 and Windows Phone 8.0/8.1 option.
Selecting Visual C++ Features from the Command Line
In order to support installation of optional features from the command line, the /InstallSelectableItems parameter has been added to the Visual Studio 2015 Community, Professional, and Enterprise SKUs.
/InstallSelectableItems takes a semi-colon separated list of identifiers that correspond to optional features in the setup dialog.
For unattended installation scenarios, such as deployment to a build lab, the following command line will install all options under the “Visual C++” node in the optional features dialog:
vs_enterprise.exe /q /norestart /InstallSelectableItems NativeLanguageSupport_Group
The example uses the Enterprise SKU installer (vs_enterprise.exe). This would, of course, need to be adjusted for Professional or Community.
Here’s the full list of optional features & identifiers in Visual Studio 2015 RTM that can be used to install C++ features.
| Optional Feature in VS Setup (Command Line Identifier) | Description |
|---|---|
| Common Tools for Visual C++ 2015 (NativeLanguageSupport_VC ) |
v140 Compiler Toolset, C++ desktop application project templates, and libraries. |
| Microsoft Foundation Classes for C++ (NativeLanguageSupport_MFC) |
MFC libraries for Visual C++. Requires Common Tools for Visual C++ 2015. |
| XP Targeting for C++ (NativeLanguageSupport_XP ) |
XP Targeting support for Visual C++. Requires Common Tools for Visual C++ 2015. |
| Visual C++ [parent node] (NativeLanguageSupport_Group) |
Selects all three of the above options |
| Windows 8.1 and Windows Phone 8.0/8.1 Tools (ToolsForWin81_WP80_WP81) | Includes Visual C++ compiler toolsets (v120 and v110), libraries, and templates for building & maintaining Windows 8.1 and Windows Phone 8.0/8.1 applications. Note: this option is not specific to Visual C++. |
What If I Did Not Install Visual C++?
We understand that Visual Studio users might not have selected all the tools and libraries that they need during the initial installation, so we have modified the behavior of Visual Studio to accommodate such scenarios. Of course, you can also directly launch setup again using “Add or Remove Programs” in the Windows Control Panel.
Creating New Projects
For convenience, in the New Project window, we have inserted placeholder templates that will launch the installer for the components needed to develop those types of applications:
For example, selecting the above template would launch the installer for the tools needed for developing MFC applications:
Opening Existing Projects
When you attempt to open a project you haven’t opened before and it requires components that are not yet installed, Visual Studio will let you know about the missing components and, if you choose, start setup to install them:
If you skip the installation, Visual Studio will keep those projects unloaded. Attempting to reload will result in the same prompt. You can also directly launch setup through right clicking the unloaded project and selecting “Install Missing Feature(s)”:
Customized Projects
If you have edited the project file and moved identifying information to .props files or .targets files, then automatic setup is not supported for that project. In these situations, pay attention to the output window, which lists the set of packages that you need to install for projects with missing dependencies.
If you have any questions or concerns, please feel free to write directly to Daniel Griffing Daniel.Griffing@microsoft.com.
A better setup soultion could be remove the "typical installation" and force users to choose which tools, languages and environment to install.
Kind of related to this, are you planning for a compiler-only SKU in the near future?
This would've been nice 2 days ago. I installed vs2015 and loaded up my project instead of telling me the components need installed it just spat out 1000 compiler errors about cl.exe being missing, combined with the fact visual studio no longer appears in its Folder in the start menu, and searching for it by name yields no results led me to believe my install was corrupted, countless install cycles and repairs later, including redownloading the iso and editing the registry i realised the visual studio shortcut is loose in the start menu and c++is an optional component now with no warning, thanks.
@Alessio
Thanks, we will consider this feedback.
@donmez
This has been a more frequent request lately and is under consideration.
@Andrew
Email me, ebattali@microsoft.com.
What a pain. Now I must explain this to 20 other devs who don't care or follow this blog and hope they don't hit "typical" as they could in the past and then hand hold them through repairing this mess.
> Upon launching setup, you can choose a “Typical” or “Custom” install
Do people do typical installations?
Can't you just skip this question and move straight to the details of what will be installed?
Alessio and Olaf are right. The idea of a "Typical" Visual Studio installation seems misguided.
It would make more sense to default to installing nothing, or installing everything. As a C++ developer, when I'm offered a "Typical" installation, I'll naturally assume it includes C++. Ditto C# or VB developers, if and when those languages become optional. People's expectations of what "Typical" means vary wildly from one developer to the next.
Either force people to make the choice, or install everything for those that don't choose (making it obvious that that's what happening, by showing the tree with everything checked).
Ultimately, it's impossible to get this right by default for even a majority of people, let alone everyone. Any defaults will always be wrong for a great many people, and rightly or wrongly they're going to blame you for their resulting problems.
What about C++ developers that don't do .NET development, why can't we remove C# and VB.NET?
I've installed VS2015 Community few days ago, and there was no option to remove them. I would like to have more options to select what to install or not, like in the old VS setups.
Actually i don't even use the IDE. Ideally, i would like to install only the C++ toolchain (with the Windows SDK).
Regards.
why not release visual studio c++ version? no .net at all
Since this is criticize Visual Studio 2015 Install day;
1) Why white on black? It's almost impossible to read.
2) Why not explain what more of the choices are?
3) I didn't install Silverlight, but the mac debugging DLL got installed anyway.
4) Why VB? I've never used it and will never use it.
And v130 was skipped because it was unlucky? Give me a break! I see this more often now than ever before.
As others have said, it seems odd to have a "typical installation" option at all, for a product as versatile as this. Is there really a "typical" way to use VS? People use it for widely different things. Some people *only* need the C++ parts, some *only* need C#. Some do web stuff, some target mobile phones, etc. It seems weird to pick any specific combination and call that "typical".
When I see a "typical installation" option in an installer, I assume that "it'll probably have 90% of what i need, all the commonly used stuff that everyone relies on". But with VS, there is no commonly used stuff that everyone relies on.
Perhaps it'd make more sense to just have "Full" and "Custom"? For most people, disk space isn't a huge concern, so just installing everything at least ensures they get the features they need.
Also, yes please to a compiler/toolchain-only installation, similar to what used to be available through the Windows SDK.
Where is all C++ help for Visual Studio?
I can't find it anywhere. Help Viewer does not show any content available.
Let's pray we get separate IDE for managed, web, & native as VStudio, VCode, & VC++. I am impressed by managed applications in the enterprise (I particularly respect such database & networking centric solutions for IT). I also admire brochures and advertising driven by web. Interop is good, but integrating as VS98 did is too much. I'd prefer if the performance critical native part was kept distinct.
Poor, very poor. Microsoft's idea of typical is a flawed and patronizing 'we know best attitude'. Where in the custom installation options does it allow me to not install VB?
And AlexGis correct, where is the help for C++?
Also I installed VS2015 from a path that included a space and guess what? When I launched the IDE for the first time I got a dialog box telling me that the pre-release license had expired. I had not installed a pre-release version! I had to reinstall from a path without a space. Microsoft has known about this bug since RC1 and still not fixed it.
Please do try to get it right next time.
Missing C++,MFC, SDK… or Visual Studio parts is annoying for sure. But as the installer takes forever to launch and install files it's even worse.
I agree with other comments that it would be more sensible to allow the user to choose what languages he/she wants to install rather them to force them to install C#/VB and make C++ optional.
Wouldn't it have been more honest to call it 'Managed Only' or 'New Corporate Internal Development'?
@jalf, 'Perhaps it'd make more sense to just have "Full" and "Custom"? For most people, disk space isn't a huge concern, so just installing everything at least ensures they get the features they need.'
Or they could just have Custom with nothing initially selected. Then expandable check boxes for C#, VB, C++… That way, initially, it's clear what you're getting and what you're NOT getting.
(They could still have C# and VB selected by default if that's the way they want to do it. Then pure C++ devs can just unselect them and select C++. Not much extra work as they will typically be customising the C++ bits anyway.)
Agree with Alessio – Install the VS shell by default an force users to pick the languages they develop in to select the tools.
Ok now go and kill us.
YOu have aimed at our legs and hands now is time
Making Visual C++ optional seems like a half baked idea. Nevertheless, I wasn't bit by this because I already knew MFC would be an optional install and selected custom install and caught this. However, it would be nice if I could just select those Visual C++ and not install all of the other tools that are NOT optional.
One of the things I disliked about the VS pre-releases was the amount of time it took to install and de-install. I hope in the next release I can disable VB and .NET. So it is sad for us C++ devs, but it is the right direction for future releases. Thanks for listening to us users.
And I second the idea by others to get rid of the typical installation.
Since we're mentioning default setup, can we change the default target platform from win32 to x64 ? Everything is 64bit now in PC development, it should be the norm not the exception.
I don't understand why everyone is complaining, I think that's a big step in the right direction, thank you! I installed VS 2015 and VS 2013.5 on the same day and installing VS 2015 was much faster. Would be great if I didn't need to install VB.NET in the next version.
But I agree that a "Full" installation instead of a "Typical" installation would make more sense.
It's shame. Now all inst. process will begin with phrase: Don't forget to choose custom and install C++
msdn.microsoft.com/…/jj851139(v=vs.140).aspx
This document is not updated for Visual Studio C++ 2015 about v140_xp toolset targeting 2014
Please focus on "Uninstaller UI". Just like Installer UI, there are two progress bars, the first one says Acquiring and the second one says Applying. There is "no" indication of the word "uninstalling" …
I guess here is the message: "C++ was back, but now it is gone again!"
Can you explain how C++ is gone from VS2015 RTM ???
After installing Visual Studio Community 2015, I only got File->New->Project->Installed->Templates->Visual C++->Windows->Universal->Blank App (Universal Windows). There are no other templates for C++, no choice for win32, no console app, no anything. How am I supposed to use this! Jesus! I rerun setup multiple times but there is no option to add any of those pretty basic project templates! This is just incredible! It is so frustrating that I am tempted to uninstall this garbage! Sorry for the language!
A better solution is the Visual C++ to have its own install package. Then there is no confusion! The current setup is so broken it is unusable. I also don't understand why every time I run repair, there is always something else to download and apply? Does it mean the installer is always missing something ? I would expect repair to check for only missing or broken packages, not download something and apply something every time.
Checking the box under Language -> C++ Common Tools for Visual C++ 2015 gives you absolutely zero C++ templates, not even the basics. You only get the option to install Universal Windows Platform Tools. That does not include any win32, console app. How the hell can one use this? Jesuzz
I tried to compiler a simple Hello World application targetting x64 but I got Windows Phone IP over USB is not running? What the hell? Who says anything about targetting Windows Phone? I am trying to make a simple application on the desktop. You cannot do the simplest things with VS 2015. Jezuz …
I notice that Eric has stopped responding to these comments. Hanging his head in shame no doubt. To be fair though, it's not as if he was the product manager for the installer was he?
Someone needs to own up and admit that they dropped a massive one.
I have been using visual studio for a while and hence chose "typical" and then found c++ tools missing. Great!!
At least, is there a way to install c++ tools on top of visual studio community 2015?
This almost just caught me out. Luckily I decided to switch to custom to see what addition goodies are included. I can see that a 700kb installer could work for visual studio where just the bare ide is downloaded at first and as you open projects and use various features they are installed on demand. You could then genericise this installer and allow third parties to install their own projects in the same way.
It seems that there is no PGO with the community edition. Is it normal? Should we add something else? Did I made a mistake during the installation (which is really a mess now)?
How can I get pgort140.dll, which is missing if I compile with /LTCG:PGINSTRUMENT?
This is incredibly misleading. Upon launching the installer, it asked to indicate the installation "mode". For any person with a functioning brain TYPICAL means the necessary tools to develop in C++, because if I downloaded Visual Studio for developing in C++, as beautifully advertised in your site, I would naturally expect no surprises. But it turns out that the "TYPICAL" installation will not add any of that!!! So I start a new project after hours of installation and updates to my SO, and oh surprise! I wasted my time downloading everything but the stuff "Typical" supposed to include, in fact, at this point god knows what was actually installed because when I try to update to get the "additional" tools, the installer says it needs 4GB of additional space.
Seriously, what kind of people are in charge of making these desicions? Are they really trying to get costumers and developers to hate your products? You should look for potential saboteurs in your own offices! They are succeding!
I know that Microsoft no longer provides a Visual C++ package and that C++ was ripped from the Windows SDK. That being the case I'm surprised I've not been able to find instructions for installing Visual C++ without Visual Studio. Do you have instructions for creating an installation of Visual C++ (compiler, headers, libraries, linker, msbuild files, etc.) without Visual Studio? If not, why not?
Our build team would like to deploy to Windows Core. Will you run on Windows Core? If not, why not?
Personally, I'm in setup hell.
I installed VS2015 Pro today to find the WP8 templates weren't appearing. Fine, I thought. I'll use my Visual Studio 2013 Ultimate installation to do that. Just one issue…. the templates were missing from my 2013 installation now. I've checked the common directory, they should be appearing. If you ask me, you've got a shared CLSID of some kind somewhere. It definitely looks like my 2013 installation is now looking for its templates in the 2015 common folder.
I cannot install it for some unknown reason. It takes me to setup – usage. For some reason. Please fix it.
How long should I expect 2015 to spend repairing itself. It's been over 8 hours and we haven't moved beyond "Microsoft Build Tools 14.0 (x86)" for the better part of that time. I'll leave it running overnight. In the event that it doesn't complete by the morning, what should I do?
I'm tempted to delete the Visual Studio folder tree, run CCleaner on the registry to at least partially cleanup the mess, and then install from scratch.
This cost me 20min, of which 10 very frustrated ones. How can MS deliver an IDE that after installation does NOT do the minimum required, but only .NET stuff, which THEY want us to use. As soon as I can convince my boss to get rid of this MS dependency, we're switching.
VS2015 Professional:
After 4 frustrating full days of purchasing (That is hard..) Registering (That is harder, almost impossible looping process) the D/L from the now obligatory "Licensing Online Service", using the DVD ISO from the Download Manager at the VLOS produced 2 days of Install fails. There is NO MS SUPPORT for this version at all : (
Eventually tried a D/L of the ISO "iso" from >>http://www.visualstudio.com/…/download-visual-studio-vs.aspx and that worked OK.
Selected "Typical" (Having tried this and every combo on the failed version, for 24th time) and this selection using this particular ISO did install C++ successfully.
Maybe the "Typical" contents have changed now?
When I try to install tools for c++, a window comes up that asks if i want to install the missing features for c++. I click install and then a very large window appears titled Setup-Usage that lists a bunch of commands like:
/? Displays this usage text
/H
/Help
/AdminFile <filename>Specifies the instillation control file
and so on… It is too large for me to see the bottom of it on my screen, and it is the only window that appears when i try to install c++. I tried doing this as well from the web, but all that it asked was if i wanted to uninstall c++ from my computer. Please help.
I miss Microsoft Visual C++ 2010 Express! It's less than 1GB installed. Now I need 8GB for community 2015 to do the same thing?
I am confused, what is XP support for XP? .net works in XP so I am not sure why it takes 3GB of installation to allow C++ software to compile to be compatible with XP?
I'm a programming newbie, still learning.
Lastly, do I need to install the 'common tools for Visual C++ 2015' in order to code in C++ with community 2015? And MFC is optional, yes?
Thanks
if I've already done setup and I've chosen typical and now I've to work on c++ what should I do?
Run the setup again, or select it from the programs and features control panel and select Change (Windows 7), select Modify, and check the VC++ option.
Hello, I am using a laptop and when trying to install the C++ tools for windows. It doesn't work. It loads up something, I click install then nothing downloads. I really need this fixing, it is effecting my study.
When I try to create a new Windows 10 UWP, or open or build existing samples or projects, I get the following error:
The imported project "C:Program Files (x86)MSBuildMicrosoftWindowsXamlv14.08.2Microsoft.Windows.UI.Xaml.CSharp.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk
I am running VS2015 Enterprise on Windows 10 Pro. Windows 10 SDK (10240) and Emulators installed. Have re-installed VS2015 several times without luck. There is no v14.08.2 folder on my machine. Tried to copy the v14.08.1 folder to create v14.08.2 folder but this only allows you to load the project or create new ones, but build fails. This is driving me crazy.
Note: An earlier install of same VS2015 ISO and SDK on Windows 10 Enterprise Evaluation was running successfully until I had to re-format a few days ago when I upgraded my Windows 7 to Windows 10 Pro. I have now also tried to install a clean copy of Windows 10 Enterprise, re-install VS2015 with SDK and emulators, and yet no luck. Same error keeps repeating. Re-installed VS2015 Enterprise installed on dual-boot Windows 10 Pro, and Windows 10 Enterprise. Same results. Have VS2013 running on the Windows 10 Pro. Had used VS2012, and VS2010 on same system with Win 7 without issues. Windows 10 Enterprise is a clean install. Have tried the modify several times. The only options not installed were 3rd-party tools.
Any suggestions on where/how to create the v14.08.2 folder would be appreciated.
This is really a mess. I attempted to install VS2015 on my Windows10 computer two months ago and failed getting past "Microsoft Build Tools 14.0 (x86)". Now it's installed "Great! Good Fun, Time to Study C++ so when I go back to college I'll be prepared" I attempt to start and what do I get??!? More horse dung. This is a real let down, I really wish I could download Visual Basic 2010 Express instead of this garbage least then I could study for a requirement of my Mechanical Engineer degree which I hope to finish.
Thanks for providing false hope Guys. *Thumbs UP* Your truly great. Never met better people
Thats sarcasm if you haven't already figured it out
I installed Visual Studio Community 2015 and coded a simple c++ "Hello world!" and i found over 300 errors. All said that it is missing some header files.
So… how do I deploy the templates I didn't know to install to my environment silently?
Very frustrating experience.
I’ve installed VS2015 Comunity with C++ addons on Windows 10.
Even Template Visual C++ “Win32 Console Application” with default settings does not work, i.e. devenv hangs.
In process explorer, however I see 3 ( three) (!?) ConsoleApplication.exe
I just tried to install VS2015 community edition. I need it for Win10 IoT core and other C++. Customizing installation to bring in C++ caused setup to fail with dozens of errors stating missing team something, azure something, … bla bla. It was installation on Win 10.
Attempt to reinstall offered another 16GB of something and then I realized that there is plenty of “something” already installed.
So I had to clean it first (someone recalls rollback features when VS did know how not to leave junk on my machine if it fails).
2nd time installation with default settings failed again with some other errors that something different is missing.
I do not know where this is going, but I am not sure if I really want to use this (cannot call it product because it is missing basic functionalities of any SW product, installation) for my production. It is to costly to spend all that time doing QA for Microsoft instead of doing business for my customer.
What a disappointment. Terrific.
This is my first time with Visual C++ and to be honest it didn’t leave a good impression. I’ve installed it with German language. After installing the English language pack, either it crashes or I cannot create projects from certain templates. And this is still true after numerous attempt of repair and re-installations!
There is a bug in your Update 1 setup. Even after selecting “Common Tools for Visual C++ 2015” fails to install the C++ compiler. CMake complains as well.
While i try to installing C++ tools on visual studio, always missing or corrupted ?
I don’t understand why it was even a question. C/C++ was part of MS since the 80s. MS millions of 3rd party applications out there built on MS C/C++, as well I am sure with the “newer” languages, .Net, etc. On this issue, I wasted nearly 2 days of re-installing VS2015 because the “default” didn’t give me the basic C/C++ stuff nor the pure “DosBox” command line shell links,. There was one for MSBUILD but not CL.EXE. Huh? That’s Crazy!! I had to reinstall and this time, not to ‘miss out” on anything that might had fell thru the cracks, I selected all. Wow! What a mistake!! Talk about “bloat!” 🙂
What is currently a problem for me right now, having recently renewed to VS2015, is having the tool sets for v100_xp, v110_xpr Runtime libraries. For example, I need V110_XP tool set in order to support PHP 5,.6 Extensions. For PHP 7.0, they are now at V140, but for older, still supported 5.xx models, you need at least V110.
So I think MS should create downloadable setups for installing just the “Platform Toolsets’ for the VS2015 IDE/Shell environment. Why should anyone have to download and install older VS2012 or VS2010 installations just to get their v###_XP toolset? After all, its just c/c++ headers and libraries and maybe some XML files so they can be added to the IDE.
Thanks
Notice that C# disappears from the options when you select custom install. Nice transparency folks. Way to live up to your CEOs stated goals, not.
What a fustercluck of a decision that was MS. Yay.
Question:
I can’t install visual studio 2015 community edition for some reason. Every time I run the installer I get this error message:
“The specified service does not exist as a installed service”
Here is my system setup:
– windows 7 x 64 bit
– windows sdk 7.1
– core i5 4670k
– gtx 760 sli
– 16gb ram
Please help.
this is not working visual studio 2015,how i install optional templates into my pc
I just installed “Visual Studio Community” today under “typical” option. Everything went well. But I cannot find dumpbin.exe within this package. So what else I have to do to get this application? My system is Lenovo IdeaPad Z710 running Windows 8.1 Home. Thanks
Hard drive space is so cheap, why would you even consider NOT installing by default with the option to uncheck for customized installation?
I’ve been debugging an application I’ve written and it would crash when trying to delete a vector with “delete_scalar.cpp” not found.
oddly, the compiled release doesn’t crash on windows 7 environments, only windows 10.
I haven’t tested it yet, but it’s looking like it’s because I did a “Typical” installation assuming it would give me all the basics.
I’m using Win 7 Ent. and VS 2015 community . Where are the C++ templates ( Win 32 , C++, C , without importing .net ) ? I need to try some IoT using only c / c++ ( microcontrollers) , without MFC, .NET , WPF ,Win 8 sdk, win native , UWP ,… Just c/c++ and win 32 . How can I install these templates ?
i cannt find c++ in visual stdio 2015 community which i download recently.why???
Worst update could be imagined. Just now faced it.
WHY do you people make this shit so impossibly complicated? WHY? All I want to do is add C# to my programming languages installation. And I can’t even do that because it’s not listed anywhere in the Features list and all the drivel above is worthless for that endeavor.
I shouldn’t have to spend a week figuring out how to install C#. I just should NOT.