Software / Programming →Microsoft Visual Studio 2022 v17.6.0 AIO (Enterprise, Professional) (x64)

Published by: freedown on 18-05-2023, 11:46 | 0

Microsoft Visual Studio 2022 v17.6.0 AIO (Enterprise, Professional) (x64) | 31.85 GB

This distribution presents ALL existing editions of the 2022 studio version 17.4.0 "in one bottle"! AIO is "All in One". Singling out the studio's editions separately does not give a noticeable size savings ... that's why it was done in a single distribution.

To reduce the downloaded size, there is also a separate distribution for those who need only C ++ ... it is an order of magnitude smaller!
To save size, this distribution has removed previous versions of the C++ compiler (14.30-14.33), which can be selected for installation only from the second tab of the installer. Only the latest version of the plus compiler is left. So if you only select components from the first tab then you don't have to think about it ... if you select something from the second tab then just be careful ... don't install previous versions of the C++ compiler ... well, either are ready that the installer will get behind it in the Internet. Or, first, take all the components of the old plus compilers from the previous version of the studio installer into the components folder of this distribution (for the specific names of these components, see Installer\RemovedOld.txt) and then calmly install the old versions of the plus compiler

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

KEEP IN MIND
• Do not forget to choose the languages you need when installing the studio (on the last tab)
• Do not download the distribution to a "very deep" folder (the length of the full name of the distribution folder should not exceed 44 characters ) ... if it exceeds, then apparently the installer will not find the necessary him components with too long names and will probably try to download them from the Internet. You can also download as "deeply" as you want, but at the time of installation create a symlink to the distribution folder in the "shallow" folder (unless, of course, you know how to work with symlinks) • Details of what exactly is included
in the studio you can see for yourself simply by downloading from distributions ( Installer\vs_0.exe) and running only the studio installer (launching the installer does not mean the mandatory installation of the studio ... you can run the installer without any problems, familiarize yourself with the composition of the components and close the installer)
• The distribution folder must have write access (because you need to copy the files from your chosen studio edition to the right places inside the distribution folder when you run the installer). In particular, this makes it difficult to form a single iso-image of the studio installer. But if you really need an iso image, then of course you can make it from this distribution, but only for one edition of the studio. In order for the files from the edition you need to be copied to where you need to, run the installation of the desired distribution (Setup_.cmd) before writing the folder to the iso image. If you put the studio under a virtual machine, then pay attention to the permission to write to this folder for the virtual machine (well, or do the "trick" described earlier when writing an iso image)
• If you need to MAXIMUM reduce the volume of the installer for your personal purposes (let's say I just want to write desktop applications in C #), then you can get tired and study the keys for the download and installation program. This can be useful if you want to put the studio installer on a flash drive to install on many computers and at the same time want to save space on the flash drive.
You will then need to download the studio installer from the jerseys yourself (you can choose from this ).
If you are too lazy to deal with these keys, then you can then download this entire distribution, arrange the subfolders inside the Installler folder by size and consider the largest of them in order to delete those that, judging by the name, are clearly about something you do not need ... so you can with minimal effort save the maximum size.
Please do not ask about such a necessity in the discussions of the distribution! No one will make a studio installer for you exactly for your purposes

What's New in Visual Studio 2022 17.6
Brace Pair Colorization
• With brace pair colorization, you can visually distinguish each set of opening and closing braces for your code making it easier to see your code's scope or find any missing braces.
• Brace pair colorization is supported for C#, C++, TypeScript, javascript, Visual Basic, and Razor.
• You can enable or disable colorization by going to Tools > Options > Text Editor and toggling the "Enable brace pair colorization" checkbox.
C++
• Sync with Active Document now works in the CMake Targets View. It finds the first location that matches the file’s full path and syncs with that document.
• We made improvements to the Solution - Close scenario, which makes closing a solution containing C++ projects faster. The overall perf improvements can make closing a solution in some cases from 20% faster for small codebases, to 50% faster in some cases for large solutions (1000+ projects). We expect the wins to be more noticeable in large projects. For Chromium, the improvements are typically 50% faster, saving 20 seconds of time.
• The version of Incredibuild bundled through Visual Studio Installer has been updated to version 10.1.9. You can read the Incredbuild 10 release notes for detailed information on new features and the latest changes.
• C++20 support for C++/CLI
* /std:c++20 can now be used in conjunction with /clr. This allows a wide range of C++20 constructs to be used with ISO C++ types. In particular, all C++20 headers can be #included in a /clr compilation without restrictions.
* Two-phase name lookup (ISO C++ [temp.dep]) is now the default when /std:c++20 or /std:c++17 is specified. Specifying /Zc:twoPhase- is no longer required with /std:c++17. Managed templates and generics are an exception and will be compiled as before, without two-phase lookup semantics.
* Coroutines are always compiled to native code and any calls from managed code will incur a managed->native transition penalty.
* Concepts are supported for native types but use with managed types is forbidden and will result in a diagnostic.
* Module support is not yet implemented. Restricted module import support will be forthcoming in a future release.
• You can use the new CMake Debugger to debug your CMake scripts at configure time. You can set breakpoints based on filenames, line numbers, and when CMake errors are triggered. Additionally, you can view call stacks of filenames and watch defined variables. Currently, this only works with bundled CMake, and projects targeting WSL or remote machines are not supported yet
• You can now use the Create Member Function feature to quickly add constructors and equality operators to your classes
• HLSL (High Level Shading Language) is a DirectX-specific programming language used to create shaders in game development and rendering applications. The popular HLSL Tools extension by Tim Jones is now available as part of Visual Studio providing syntax highlighting, statement completion, go-to-definition, and more! To use HLSL Tools, please enable the component in the "Game development with C++" or "Game development with Unity" workload in the Visual Studio Installer.
• Improved performance for Go To and All In One Search for C++ Symbols.
• You can now view Unreal Engine logs without leaving Visual Studio. To open the log window, click View > Other Windows > Unreal Engine Log. After opening the UE log window, logs will be automatically streamed when you start the Unreal Editor with F5. You can also press the red Record button if attaching the debugger to your UE process is not feasible. To filter your logs, click on the "Categories" or "Verbosity" dropdowns.
• You can now import STM32CubeIDE projects for embedded development within Visual Studio with File > Open > Import STM32CubeIDE project. This generates a CMake project with device flashing and debugging settings for STLink. You must have the STM32CubeIDE installed with the board support package for your device. More details available here.
• With the new Remote File Explorer, you can browse, upload, and download files to your remote machine listed in the Connection Manager.
Debugging, Diagnostics and Profiling
• Visual Studio debugger now supports Breakpoint Groups,which can allow you to quickly and easily manage numerous breakpoints in organized groups.
• You can create a new breakpoint group using the "New" dropdown in breakpoints window. To add a breakpoint to an existing group, right-click the breakpoint and choose "Add to Breakpoint Group". You can also drag and drop the breakpoint into the desired group. These breakpoint groups can be enabled, disabled, and deleted. The breakpoints can be toggled individually or in combination as needed.
• The breakpoint groups also support Undo for Delete. You can use “Ctrl-z” to undo you breakpoint groups delete operation.
• Along with this, breakpoint groups now support dependent breakpoint groups. you can make your breakpoint groups dependent on other breakpoints, so that the group only activates when the prerequisite breakpoint is hit.
• Visual Studio Memory Analysis tool now has the ability to identify and display sparse arrays. You can see the list objects with sparse array under the Insights tab.
• A Sparse Array is an array that is mostly filled with zero elements, which can be inefficient in terms of performance and memory usage. The memory analysis tool will automatically detect these arrays and show you how much memory is being wasted due to these zero values.
• The debugger now supports the inclusion of .natstepfilter and .natjmc files within individual solutions, rather than the previous global location. This alteration allows for more efficient collaboration within teams, as these files can now be treated as any other file within a repository and shared accordingly.
• The Visual Studio Instrumentation tool now supports C++ code, providing improved performance analysis. To access the instrumentation tool, go to Debug > Performance Profiler and select "Instrumentation" from the Profiler window that appears.
• The Instrumentation Data View presents a list of functions ordered by longest-running, making it easier to identify potential bottlenecks. Additionally, the Hot Path section displays the call stack for the functions that are consuming the most CPU, providing further insight into performance issues.
• The Visual Studio profiling tools now also support live graphs while collecting from dotnet-monitor for WSL. The WSL live metrics are available for .NET object allocation, CPU usage, and the .NET counter tool.
• While the tool is initially collecting data from dotnet-monitor for WSL you can see the real-time graphing for live counter information, then you can stop collecting and see detailed breakdown views of memory allocation, call trees, functions, collections, and other related data.
• The .NET Object Allocation tool now features the ability to import allocations from a .NET data provider using ETL file formats. For example, if you have an ETL file obtained from a .NET provider that contains allocation tick events, the tool can execute and display the allocations made within that data.
• You can now use the IEnumerable and DataSet Visualizer to inspect your variables/objects when debugging .NET on Unix via SSH, Docker, or WSL.
• The HTML and XML debugger visualizer is now fully themed and supports Visual Studio's blue, light, and dark themes.
• The call stack window now supports search functionality. You can add desired search keywords in the search box, and the matching call stack frames will get highlighted. The window also had a new entry point for the parallel stacks providing quick access to the window while debugging.
• The parallel stack window now has new copy functionality. You can double-click on a frame to copy the stack/ shift & select frames of interest / select particular by clicking on the line and copy and then paste into your local notepad/excel to evaluate further.
• The reattach to debugger process is now persistent to the solution/project across sessions. So you can reattach to processes that you were previously attached to, even after you open a new VS session.
F#
• Introduced native "Go To Definition" functionality for navigating from C# to F#.
• Go To Definition: C# to F#
• Improved parameter name hints by hiding them when they match argument names
• Improved parameter name hints
• Enabled collapsible block comments for better readability
• Collapsible comments in F#
• Refined attribute completions by incorporating settable properties
• Resolved a "Find All References" bug that caused results to be divided into identically labeled groups
• Upgraded the "Go To All" feature experience by intelligently ordering results. See more details here: #14882
SQL
• The database ledger incrementally captures the state of a database as the database evolves over time, while updates occur on ledger tables. It logically uses a blockchain and Merkle tree data structures.
• We are adding Ledger functionality in Sql Server Data Tools similar to Azure Data Studio. SQL Ledger is an added feature in SQL 2022 that brings forth new table types, including the following:
* Append-only Ledger Tables
* Updateable Ledger Tables
* Ledger History Tables
* Dropped Ledger Tables
* Ledger Views
* Dropped Ledger Views
• We are providing the following use cases for Ledger:
* Viewing Ledger Tables, Views in SSOX.
* Creating Ledger Tables, Views from SSOX
* Creating a sqlproj with Ledger Tables. Right Click on Project-> Add Item -> Table Ledger (Updateable) or Table Ledger (Append-Only)
* Publishing th ledger to a SQL database
Git Tooling
• We made several updates in response to customer feedback including - Git: Can't undo changes while debugging and Visual Studio 2022 hangs when pasting in files, adding new files or deleting files.
Git Tooling Enhancements
• You can now stage your changes and commit your staged items during a build. Committing directly is a risky operation since your files may change, but now you can stage them, verify your files are correct, and commit them - all while a build is running.
• Improving on our Issues and Work Items integration in the commit message, you now get better search results when querying for items that you haven't updated recently or that aren't related to you but are part of your project or repo. The search works by matching complete strings in your items' names. This can help minimize copy-pasting item ids between the browser and Visual Studio.
• Updates to our Merge Dialog make it easier to understand how many files are being affected and warn you if there might be conflicts.
• Drastic improvements to our Git History window now load previous commits faster, allowing you to dig into your file and folder history quicker than before!
• Improvements to the New Branch and New Tag dialogs automatically replace spaces with dashes to avoid invalid characters in the name.
GitHub Issues
• The GitHub Issues integration allows you to search and reference your issues from the commit message box in VS, in response to this suggestion ticket. You can reference an issue or a pull request by typing # or clicking on the # button in the lower right side of the commit message text box. If you weren't already authenticated to access related issues, you will now be prompted to sign in to take advantage of this feature.
Line Unstaging
• To continue improving our line-staging (aka interactive staging) feature, we've added unstage. You can now use the tool tip option to unstage changes, line by line, as requested here Unstage individual lines and hunks in a file - 4 votes
Arm64
• We continue to build native support for Arm64 on Windows 11 for the most popular developer scenarios. We now support the .NET Multi-platform App UI (MAUI) workload on Arm64 Visual Studio.
• Code Search and Navigation
• Each result has more breathing room by taking up 2 lines of space.
• The window size and location persist from the last session of Visual Studio. The selected preview state (off, right, or bottom) is also saved.
• The default preview layout is set to the bottom.
• You can enable All-In-One Search: Tools > Manage Preview Features > "New Visual Studio Search experience (restart required)".
Sticky Scroll
• Sticky Scroll helps you orient where you are in the file and understand the context of the code you're looking at. As you scroll through your code, the class and method signatures and other headers will stick to the top of your screen. Clicking on a line in the header will navigate you to that code.
• Customize the maximum number of lines with "Maximum sticky lines".
• With “When number of scopes exceeds the maximum”, choose between higher-level scopes “Prefer outer scopes” or lower-level scopes “Prefer inner scopes”.
• Enable in "Options > Text Editor > General > Sticky scroll (experimental)" by toggling the checkbox for "Group the current scopes within a scrollable region of the editor window".
Lightbulb Performane Improvements
• The lightbulb/code actions have been greatly improved through comprehensive redesign of the diagnostics and code analysis architecture. We have focused on optimizing all components involved in bringing up a lightbulb through a combination of low/medium/high level fixes.
• Low level fixes included limiting tree walks, more efficient string handling, improving efficiency in handling source text, extreme reduction in allocations, conversions, enumerations and data structure level optimizations in the diagnostics code paths
• Medium level fixes included cancelling background diagnostics (squiggles) when computing Lightbulb diagnostics, optimizing the background indexing, optimizing the diagnostics engine for queries run on a single document by limiting analyzers that are applicable per document, addressing significant inefficiencies in several 1st party/2nd party analyzers like PublicAPI analyzer and by improving our caching model
• High level fixes included heaving reworking the diagnostics pipeline to answer span oriented questions, infer which analyzers are applicable to run on particular spans, deprioritizing slow analyzers based on historical run info.
Microsoft Teams Development Tools (Teams Toolkit)
• Add the feature flag "Teams App Configuration Improvements". The preview feature of Teams Toolkit enables developers to bring their existing internal and SaaS applications into Teams with Teams-native integration. In the teamsfxapp.yml file defines what Teams Toolkit engine does.
• Add the deep link to open Teams Toolkit directly from Teams developer portal. You can now open Teams projects in developer portal and edit in Teams Toolkit.
• We have introduced a new Teams App templates for you to start with: Workflow Bot. Use the new Workflow Bot template to create sequential workflows where Adaptive Cards can be returned in response to user input.
• We have also made several bug fixes.
Enterprise Management
• IT Administrators will now be able to host and deploy layouts on an intranet website in addition to a file share. Using an intranet location can simplify layout maintenance and improve installation performance, particularly for those organizations that currently use multiple global network file shares. View guidance for how to enable this experience and leave us feedback to let us know if there's anything we can do to improve it.
• We’ve updated the logic that governs which products are offered when you view the Visual Studio installer’s “Available” tab. You should now have easy access to both the current Previews, as well as the latest versions of SKUs you already have installed. IT Administrators also have the ability to restrict exposure to certain products by either disabling specific channels or by using the new HideAvailableTab policy to suppress the visibility of the Available tab.
• We will start shipping the latest installer everywhere, which means that all future updates to all versions of Visual Studio 2017 and higher will include the latest installer. This means that any new functionality or bug fixes that we add to the latest installer (such as the ability to rollback an installation sourced from a layout) will be automatically available to use in those downlevel versions of the product. Using the --useLatestInstaller parameter in your acquisition scripts will no longer be necessary.
• You can now rollback an update if the product sources originated from a layout. Just make sure that the layout contains the packages needed for the rollback to be successful. More details can be found here.
.NET MAUI
• Updates .NET MAUI to 7.0.86 (SR6), see https://aka.ms/dotnet-maui-releases for release notes.
• Updates to .NET for Android 33.0.46
• Updates to .NET for iOS 16.4.7060
Исправления ошибок
• Please add a way to hide the available tab in the Visual Studio Installer
• Ability to downgrade even when VS is installed from a layout 2 votes
• Misoptimization for ARM64 in 17.6 preview 2, symmetrical comparison optimized out
• VS hangs when shutting down solutions that contain C++ code.
• C++ /CLR regression in VS 17.6 Preview 1 when using the new C++20 support 1 vote
• Override editor feature doesn't work 3 votes
• Windows Forms designer since VS 17.5: "Unable to cast object of type 'System.Data.SqlClient.SqlCommand' to type 'Microsoft.Data.SqlClient.SqlCommand' 13 votes
• In certain scenarios break points are only being hit once when debugging a .NET MAUI app 1 vote
• Unable to edit publish profile on VS 2022 1 vote
• Unable to build WiX3 projects with msbuild that comes with 17.6 Preview 3
• git history fails with .vb files 1 vote
• Angular project: break point is not hit and browser is not launched when debugging on VS 2022
• Search eventually starts returning no results 11 votes
• Sync with Active Document is not working in CMake Targets View 32 votes
• Edge Developer Tools no longer included in Visual Studio
• Getting build error after selecting automatically deploy the database project before unit tests are run option 21 votes
• Build.Compile (Ctrl-F7) stopped working on some files after upgrading to 17.4 on CMake projects with Open Folder 7 votes
• Using msbuild.exe from the command line for Xamarin.iOS is unable to find AppIcons and hangs on completion 7 votes
• Large text string causes VS 2022 to hang 6 votes
• __sanitizer_annotate_contiguous_container declared inconsistenly in 17.3.0 3 votes
• Visual Studio crashes when opening a file is opened and then branch is changed and the file doesn't exist on that branch - Developer Community 1 vote
• Sqlproj file not building when it has certain master db references provided by VS's inbuilt master.dacpac file - Developer Community (visualstudio.com) 20 votes
• Visual Studio 17.5 broke SqlPackage.exe - Developer Community 19 votes
• SQL Unit Tests fail after 17.5 due to Keyword not supported: 'multiple active result sets' - Developer Community (visualstudio.com) 1 vote
• SSDT Advanced Settings will not persist - Developer Community (visualstudio.com) 15 votes
• Unable to open sql files in database project - Developer Community (visualstudio.com) 3 votes