“Visual Studio” and “Visual Studio Code” are not the same thing. I don’t know why Microsoft decided to confuse everyone with the names of those two development tools. With a standard installation, we can reduce the configuration time, and easy to debug the same or similar errors in the installation.The first time I heard about “Visual Studio”, I thought it was the same as “Visual Studio Code”. B-4: Compilers, Build Tools, and Runtimes When we installed Visual Studio associated with Git for Windows, then we might not need to install Git independently as introduced in Source Control (4-1), Git - Configuration, On the other hand, just due to this Visual Studio installation including Git, it introduced the configuration error, introduced in this article: Source Control (4-2), Git - Configured to Connect to DevOps and GitHub, Therefore, if we make the installation with a standard format, then we will get the same error, and we can debug in the same and known way. We can choose the default that is configured by Work Loads, and we also can choose the most in the case we need them (without our of support ones): This part will give us chance to make detailed choices. I prefer to include all of them in case we need to use them, except C++ that I am sure I usually do not use it, Not choosing, except you are the game developer. We might just choose Desktop, but I include mobile, just in case I have chance to do that. A-1: Web & Cloudįor this category, we might skip Python if not use it or even Node.js. This part will give us chance to make a basic development approach without detailed choices, if you are new in the development field you might only choose this part, that should be enough to include major components for your development. B-4: Compilers, Build Tools, and Runtimes. ![]() When we run the Visual Studio installer, we usually have two places to choose:
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |