$vsOptions = -FilePath $filePath -ArgumentList $vsOptionsįor some reason, Invoke-WebRequest isn't downloading the file it is supposed to be. $optionsIncludeRecommended = "-includeRecommended" $optionsAddLayout = ::Join(" ", $workloadArgument ) #Invoke-WebRequest -URI $url -OutFile $filePath $filePath = "C:\dev\pub\vs\vs_professional.exe" New-Item -Path 'C:\dev\pub\vs' -ItemType Directory -force It is supposed to download visual studio via a powershell script $url = "" If Sticky Scroll is not working, try enabling the following options in Tools > Options > Text Editor > C# > Advanced.I have this code. Sticky Scroll requires Block Structure Guides to be enabled for some languages (e.g., C#). Let us know what you think of Sticky Scroll in Visual Studio on this feedback ticket and report any issues you face so we can improve the experience. Try Sticky Scroll in Visual Studio 2022 17.6Įnable it in Tools > Options > Text Editor > General > Sticky Scroll by toggling the checkbox for “Group the current scopes within a scrollable region of the editor window.” But if you need to quickly turn it off, you can right-click on the Sticky Scroll area and click “Sticky Scroll”.
“Prefer inner scopes” shows lower-level scopes: “Prefer outer scopes” shows top-level scopes: The new option “Prefer inner scopes” shows lower-level scopes by pushing out higher-level scopes as you scroll through deeply nested code. “Prefer outer scopes” is set by default, which shows the higher-level scopes that come from the top of the file. In Options, you can configure whether outer or inner scopes are prioritized with “When number of scopes exceeds the maximum”.
Instead, it’d be more useful if lines that are likely to be different are shown instead. It can feel wasteful to give up two lines of vertical space for info that is often obvious. Oftentimes, the namespace and class name match the file name. We’ve heard feedback about how sticking outer scopes isn’t helpful. New: Choose between outer or inner scopes Let us know what you think of Sticky Scroll in Visual Studio on this feedback ticket.
0 kommentar(er)
