Microsoft Visual Studio 2022 AIO ver. 17.1.0 (Все в одном: Enterprise, Professional, Community, ...)

Прочие ограничения

Administrator rights are required to install Visual Studio.
.NET Framework 4.5.2 or above is required to install Visual Studio. Visual Studio requires .NET Framework 4.8 to run. If .NET Framework 4.8 isn't already installed, it will be installed during setup.
Universal Windows app development, including designing, editing, and debugging, requires Windows 10. Windows Server 2019 and Windows Server 2016 may be used to build Universal Windows apps from the command line.
Team Foundation Server 2019 Office Integration requires Office 2016, Office 2013, or Office 2010.

Полезные цифирьки ;)

Enterprise: VHF9H-NXBBB-638P6-6JHCY-88JWH
Professional: TD244-P4NB7-YQ6XK-Y8MMM-YWV2J

ИМЕЙТЕ ВВИДУ

• Не забывайте выбирать требуемые вам языки при установке студии (на последней закладке)
• Не качайте раздачу в "очень глубокую" папку (длина полного названия папки раздачи не должна превысить 44 символа) ... если превысит то видимо установщик не найдет на диске нужные ему компоненты со слишком длинными именами и вероятно попытается выкачать их из интернета. Можно также скачать так "глубоко" как захотите хотите, но на время установки создать в "неглубокой" папке симлинк на папку с раздачей (если конечно умеете работать с симлинками)
• Детали того что именно входит в состав студии вы можете посмотреть сами просто скачав из раздачи (Installer\vs_0.exe) и запустив только установщик студии (запуск установщика не означает обязательную установку студии ... можете без проблем запустить установщик, ознакомится с составом компонентов и закрыть установщик)
• У папки с раздачей должен быть доступ на запись (потому что нужно копировать файлы от выбранной вами редакции студии в нужные места внутри папки с раздачей при запуске установщика). В частности это затрудняет практику формирования единого iso-образа установщика студии. Но если вам очень нужен iso-образ то у вас конечно получится сделать его из этой раздачи но лишь для одной редакции студии. Для того чтобы файлы от нужной вам редакции оказались скопированы куда надо запустите установку нужной раздачи (Setup_.cmd) перед записью папки в iso-образ. Если ставите студию под виртуальной машиной то обратите внимание на разрешение на запись в эту папку у виртуальной машины (ну либо делайте, описанный ранее, "трюк" при записи iso-образа)
• Если вам надо МАКСИМАЛЬНО уменьшить объем установщика под ваши личные цели (скажем просто хочу писать на С# десктопные приложения) то вы можете запариться и изучить ключи для программы скачки и установки. Это может быть полезно если вы хотите установщик студии сунуть на флэшку чтобы ставить на множестве компов и при этом хотите сэкономить место на флэшке
Вам потребуется тогда скачать установщик студии с майков самостоятельно (выбирать можно из этого).
Если лень разбираться с этими ключами то можете тогда выкачать эту раздачу целиком, упорядочить подпапки внутри папки Installler по размеру и рассмотреть самые крупные из них чтобы удалить те которые судя по названию явно про что-то вам не нужное ... так вы сможете минимальными усилиями сэкономить максимум размера.
Не надо пожалуйста спрашивать про такую свою необходимость в обсуждениях раздачи! Никто не будет за вас делать установщик студии именно под ваши цели

Что нового в Visual Studio 2022 17.1

C++
• A new Configure Preset template has been added to configure and build CMake projects on a remote macOS system with CMakePresets.json. You can also launch CMake targets on a remote macOS system and debug with the front-end of the Visual Studio debugger backed by GDB or LLDB.
• You can now debug core dumps on a remote macOS system from Visual Studio with LLDB or GDB.
• The versions of Clang and LLVM shipped with Visual Studio have been upgraded to v13.
• Visual Studio's CMake integration will only activate when a CMakeLists.txt is identified at the root of the open workspace. If a CMakeLists.txt is identified at another level of the workspace, then you will be prompted to activate Visual Studio's CMake integration with a notification.
• Added a new register visualisation window for embedded targets, available through Debug > Windows > Embedded Registers.
• Added a new thread view for RTOS projects, available through Debug > Windows > RTOS Objects.
Debugging & Diagnostics
• Added a new feature called StickyDataTips i.e., you can now keep your DataTips expanded until you click away
• Added a support for Microsoft Azure App Services Attach to Process.
• When building managed libraries developers can choose to embed their source files with the debug information (PDB file) that is produced by the build, and even embed the PDB file into the assembly itselfpress F12 to navigate to the original source file.
• There is now IntelliSense completion for await within an awaitable expression. Start typing an awaitable expression and notice how await will now show up in the completion list.
• There is now a refactoring to move static members to a new type. Place your cursor on a static member. Press (Ctrl+.) to trigger the Quick Actions and Refactorings menu
• There is now a refactoring to simplify code to use the new C# 10.0 extended property patterns
• There is now a refactoring that detects variable swaps and suggests using a tuple to swap values so instead of using a temporary variable in-order to swap arguments you can use a tuple
• The Code Definition Window now supports C# and Visual Basic. To use the Code Definition Window, either press (Ctrl+W,D) or select View > Code Definition Window. Next, place your cursor on an identifier to navigate and explore code.
• C# and Visual Basic support in the Code Definition Window
• There is now a refactoring to enable nullable reference types across a projectSignature Help has improved its display when a tuple appears many times within a signature. The simplified view includes the Structural Type key to show you what is contained in the tuple.
• You can now understand errors and warnings at a glance without needing to hover your cursor over a line of code with Inline Diagnostics
Editor
• Visual Studio can now automatically save code documents whenever the application loses focus
• The Code Cleanup feature can now be configured to be run whenever a file is explicitly saved
Git Tooling
• Added capability to compare branches in Visual Studio.
• Introduced enhancements to the detached head state including the ability to checkout commits.
• Multi-repo branching enhancements including the ability to create branches across different repositories at the same time (preview feature).
• Added capability to include README file when creatting new Git repositories in Visual Studio.
• Enhanced the ability to pin commonly used branches utilizing hover buttons.
• Built a more discoverable UI for relating Work Items with new commits.
IDE
• Add your Github AE account using the integrated account management experience (Requires enabling GitHub Enterprise Server accounts).
• Added ability to toggle color scheme to color your tabs by File Extension or Project.
• Added capability to customize tab colors when color tabs are enabled. Right-click on a color tab and select Set tab color.
Installation and Updates
• We have reduced the number of reboots required after installation. Required reboots were frequently caused by updating Visual C++ Runtime files in the system directory while they were in use
• When the recommended reboot dialog is displayed, the customer may launch the Visual Studio IDE immediately (without rebooting).
• Added information about LTSC channel expiration dates to the Update Settings dialog.
• Added ability to programmatically change the source location of updates independently of actually performing the update. This enables IT admins to programmatically change the update channel.
• Microsoft Azure App Services Attach to Process
• You can now attach to your .NET (Framework. Core, or 5+) for Windows App Service without a solution or project open
Microsoft Teams developer tools
• Teams Toolkit is a Visual Studio Extension to help developers create experiences for Microsoft Teams and is part of the Microsoft Teams Framework (TeamsFx)
• You may now choose the Microsoft Teams development tools component in the ASP.NET web development workload in the Visual Studio Installer.
• Installing this component adds the Teams Toolkit extension. Use the new Microsoft Teams App project template to get started creating a new Teams tab application.
.NET
• We now surface embedded source and Source Link as part of Go to Definition if a referenced assembly has embedded source or Source Link
• There is now a Stack Trace Explorer Window that displays stack traces from the clipboard allowing you to click and navigate directly to the related code
• In this release we added Naming Styles to the EditorConfig UI
• Go To Definition from source information in PDBs.
• IntelliSense completion for await within an awaitable expression.
• Move static members to a new type refactoring.
• Simplify code to use the new C# 10.0 extended property patterns refactoring.
• Detect variable swaps and suggest using a tuple to swap values refactoring.
• Code definition window support for C# and Visual Basic.
• Enable nullable reference types across a project refactoring.
• Signature help simplified view improvements when a tuple appears many times within a signature.
• Understand errors and warnings at a glance with inline diagnostics.
.NET Hot Reload Fixes
• Blazor developers building WebAssembly (Wasm) apps would sometimes see a rude edit dialog when the changes were actually applied or see the rude edit dialog appear multiple times.
• Blazor developers building WebAssembly (Wasm) apps would get into a permanent rude edit state if they used the rebuild feature of the rude edit dialog and then attempted to make changes to Razor files.
• Blazor developers would sometimes see their Hot Reload session terminate when running their app through the Visual Studio debugger (F5).
• Blazor developers would see the Visual Studio debugger break with “Unable to stop debugging...” message if they tried to edit error.cshtml file and apply changes to it using .NET Hot Reload. More bug fixes will be made in future releases of Visual Studio as we strive to improve this feature's capability and stability. If you encounter any problems, please report them using Visual Studio's Report a Problem feature.
Performance
• Faster solution close performance by optimizing cleanup operations when closing a solution.
• Visual Studio now indexes your files in your codebase to provide a much faster Find in Files search experience
• Razor (ASP.NET Core) Editor
• Razor will now add missing using directives if a quick action requires one.
Solution Filters
• Added an option to load or reload the entire dependency tree for the projects in your Solution Filter. When new projects are added to the dependency tree but haven't been manually added to your Solution Filter, you can easily add all the dependencies at once.
Test tools
• A test animation now appears in the bottom of the Visual Studio shell when a test operation is underway. It's similar to the build animation and lets you know what Visual Studio is working on and gives you an indicator that the process hasn't crashed.
• Code coverage tools can now produce the cobertura code coverage format
• You can also collect with the cobertura format from the cli by either specifying it in the runsettings file or specifying it in a parameter
Web Tools
• When provisioning and selecting Azure resources Visual Studio remembers the selections you previously made for fields "Resource Group" and "Location" instead of always defaulting to the first entry in the list
• Publish profiles are now always listed alphabetically in the drop-down located at the top of the Publish summary page as well as the drop-down in the Visual Studio toolbar called Web One Click Publish.
• Tooling support for Azure Container Apps remains in the Visual Studio preview channel. To continue working with Azure Container apps, install the 17.2 Preview 1 release.
XAML Hot Reload
• XAML Hot Reload now supports more end-to-end scenarios when used together with .NET Hot Reload. We’ve enabled the following scenarios: For WPF and WinUI 3 apps:
• XAML code editor will now properly show newly created control types and properties created by a .NET Hot Reload operation in IntelliSense.
• Binding to a newly created property using .NET Hot Reload will now work as expected. For WinUI you can also now use x:Bind to bind to a new property as well. For WPF apps:
• Adding a newly created method for an event handler created using .NET Hot Reload will now work. Note: While the above scenarios work if the types are first applied using .NET Hot Reload and then XAML Hot Reload is used, there is a known limitation
XAML Live Preview
• We’ve made several improvements to rulers, zoom and element selection behavior.
• XAML Live Preview now supports .NET MAUI apps (WinUI & Android), though still limited to where .NET MAUI is available.
• .NET MAUI Support (WinUI & Android Emulator): .NET MAUI apps running as either a WinUI 3 app or executed in an Android Emulator are now supported. .NET MAUI is not yet supported in every version of Visual Studio, therefore this capability while built-in starting with 17.1 will only be available in those versions where .NET MAUI is available
• Ruler Changes: Rulers now properly display the pixels indicator right-to-left or left-to-right based on your applications configuration
Исправления ошибок
• Fixed an issue where the DataSet Custom Debugger Visualizer would not work for Remote and Azure App Service debugging scenarios.
• Added support to cancel a pending "Hot Reload" operation.
• Fixed incremental deployment issues with Xamarin Hot Restart.
• Fixed and enabled Code Lenses support for TFS.
• Fixed bug that would cause misaligned code colorization in Razor and LiveShare scenarios.
• Visual Studio's C++ intellisense is improved when targeting CMake projects on macOS systems. Visual Studio now processes CMake's CMAKE_OSX_SYSROOT variable when searching for C++ headers.
• Fixed several issues where using omp task when combining the /openmp:llvm and /ZI would cause the compiler to crash or silently generate bad code.
• Fixed an issue when Debugging Android applications when Fast Deployment is disabled.
• Correct an issue causing C2567 when using /experimental:deterministic, /pathmap, and /clr.
• Fix crashes in ARM64X thunks from /RTC flags.
• Don't decorate already decorated ARM64EC symbols while linking.
• We have fixed an issue with the Azure Container Apps workflow generation where the Service principal generation fails if a service principal with the same name is already present.
• Added and == operators to ATL CString.
• Updated the linker flags table to allow the -cgthreads and -pdbthreads to differ between in the GENRROFILE and USEPROFILE phases.
• A problem publishing projects that contain an x86 COM reference with ClickOnce has been fixed.
• Fixes a VS crash bug, when adding multiple launch profiles in Manage Docker Compose Launch Settings dialog.
• Fix packaging of no-write-symbols,nodebug AOT'd assemblies within Xamarin.Android applications.
• The C# compiler would generate incorrect codegen or crash in certain scenarios with interpolated string handlers and from-end indexers in deconstruction assignments. These issues have now been fixed. For more details, see https://github.com/dotnet/roslyn/issues/58514 and https://github.com/dotnet/roslyn/issues/58569.
• Fix for an intermittent VS crash when WinForms .NET designer is open and some operations are performed on the project.
• Add ARM64EC to /MACHINE options for link.exe.
• Fixed an issue where sometimes changes to the CMake Workspace settings file would not take effect.
• Under some circumstances the publish of a worker service to an Azure Container Apps would silently fail.
• Fixed an issue where Visual Studio failed to start on Windows 7 machines.
• I regularly have to force kill devenv.exe to close VS because the environment is locked in edit and continue with nothing running
• Razor Tooling: Disco Colors Persist
• Inline Replace focuses wrong input
• MSB3179: Problem isolating COM reference 'SMTLib': No registered classes were detected for this component
• Unable to use the new "project debug properties" window with a screen reader.
• Hot reload doesn't work with .cshtml file in the .NET website project
• Code generated by Source Generator is marked with red squiggles, but compiles fine
• Needed polish for Bidirectional text control option
• Attempting to add a new Launch profile via the Manage Docker Compose Settings causes Visual Studio 2022 to crash.
• Source Generator Intellisense is not working on client project
• Hot Restart with iOS 15 fails with embedded fonts and some additional components (like Firebase)
• Slow "Go to definition" in Visual Studio using UE5 Early Access (was Make IntelliSense work on large projects)
• Bug in Visual studio 2022 + Xamarin + SignalR (method not found)
• Git Repository window uses wrong date format (regression in VS 2022)
• Visual Studio ran into an unexpected problem
• Visual Studio 2022 Preview 7 stuck at "Waiting for IntelliSense to finish initializing..."
• System.InvalidOperationException: No pending update
• UseMultiToolTask causes change detection in a C++ precompiled header to break if a single cpp is compiled
• Unable to resolve symbol '“WebAssembly”'
• In a blazor page (*.razor) adding semi-colon to c# line of code causes cursor to jump
• PackageId:Microsoft.VisualStudio.TestWindow.SourceBasedTestDiscovery;PackageAction:Install;ReturnCode:-2147024690;
• Modules: std::any breaks in nontrivial code when importing a module
• ARM64: incorrect code gen when compiler decides to pass by value
• Error while compiling on WSL with Max Parallel Compilation Jobs >1
• Using bitwise "|" when logical "||"was probably intended
• "Find All References" feature in Visual Studio 2019 16.10.X version
• A problem publishing projects that contain an x86 COM reference with ClickOnce has been fixed
• Visual Studiof Upgrade broke package compilation
• Linux development with C++ - Internal Dynamic linkage is wrong
• Comments without Doxygen tags is not parsed correctly
• Link error with local declaration inside namespace
• Predefined macros for launch.vs.json
• Solution explorer do not display power shell files icon
• C26440 false positive Function can be declared 'noexcept'
• C++: std::is_empty is incorrect for a template specialization
• VC++ for Linux: Remote Pre-Build Event running before copy sources
• Blazor Server and Css Isolation using .Net 6 + VS Community 2022

Решение проблем

1 Если у вас установщик студии закрывается сам собой без каких либо видимых сообщений об ошибке то возможно вы не установили сертификаты, как описано в шапке. Если вы их установили и установка прошла без сообщений об ошибке (сертификаты можно ставить сколько угодно раз, если забыли ставили или нет и как оно прошло), то проверьте что у вас запущена служба "KeyIso" (или еще она называется "Изоляция ключей CNG"). Если у вас эта служба вообще магическим образом отсутствует в списке служб то попробуйте2 Если у вас установщик студии или она сама закрываются то проверьте свои графические драйвера интел. У людей версия 15.31.7.64.3131 может создавать такие проблемы. Обновите его до более новой версии, скажем до 15.36.13.64.4062
3 Если в текстовом редакторе у вас русские буквы отображаются вопросиками то попробуйте в настройках винды задать русский языком по-умолчанию (Control Panel -> Region -> Administrative -> Language for non-Unicode programs -> Change system locale). Если при этом вместо нормальных букв стали отображаться лишь "кракозяблы" то попробуйте в том же окне настроек включить utf-8-галочку