How to install Visual Studio 2022 Build Tools on Windows Server Core 2022 - visual-studio-2022

I am attempting to install Visual Studio 2022 Build tools on a fully updated Windows Server 2022 Core installation as a virtual machine on ESXi. Whenever I start the setup, I see the GUI appear while it's extracting files and then it crashes leaving an event log entry:
Application: vs_setup_bootstrapper.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.NotImplementedException
at MS.Win32.UnsafeNativeMethods+ITfThreadMgr.CreateDocumentMgr(ITfDocumentMgr ByRef)
at System.Windows.Input.TextServicesContext.RegisterTextStore(System.Windows.Input.DefaultTextStore)
at System.Windows.Input.DefaultTextStore.get_Current()
at System.Windows.Input.TextServicesContext.SetFocusOnDefaultTextStore()
at System.Windows.Input.InputMethod.EnableOrDisableInputMethod(Boolean)
at System.Windows.Input.TextServicesManager.Focus(System.Windows.DependencyObject)
at System.Windows.Input.KeyboardDevice.ChangeFocus(System.Windows.DependencyObject, Int32)
at System.Windows.Input.KeyboardDevice.TryChangeFocus(System.Windows.DependencyObject, System.Windows.Input.IKeyboardInputProvider, Boolean, Boolean, Boolean)
at System.Windows.Input.KeyboardDevice.Focus(System.Windows.DependencyObject, Boolean, Boolean, Boolean)
at System.Windows.Input.KeyboardDevice.Focus(System.Windows.IInputElement)
I have also tried manually extracting the files and running but the same thing happens using this guide because the installer itself is crashing:
https://silentinstallhq.com/visual-studio-build-tools-2022-silent-install-how-to-guide/
Can anyone advise why it's failing?

Installation of Visual Studio Build Tools 2022 on Windows Server 2022 Core will always fail as the Visual Studio Build Tools 2022 will only identify the 2016 and 2019 versions of Windows Server Core as installation candidates, even if a silent installation is requested. The installer will attempt to throw a GUI exception (which Core cannot handle).
The only method for running Visual Studio Build Tools 2022 on Windows Server Core is by doing so on versions 2016 or 2019. Microsoft calls this out specifically in their documentation (from: https://learn.microsoft.com/en-us/visualstudio/releases/2022/system-requirements#microsoft-visual-studio-build-tools-2022-system-requirements):

It is better to use vs in linux.
You can use a VM to do that.

Related

command line MSBuild works - remote build produces errors

I am setting up a process to build remotely a suite of COBOL programs. A virtual machine has Visual Studio 2017 installed along with a Micro Focus COBOL Enterprise Developer 4.0 Visual Studio 2017 plugin. The programs use CICS as their UI and work with a Microsoft SQL Server backend. Opening a developer command prompt in Visual Studio and issuing a MSBuild command with the solution as the parameter successfully builds the programs. A remote build does not - the error is
MSBUILD : error MSB4025: The project file could not be loaded. Root element is missing.
any ideas?
You need to install the "Micro Focus Enterprise Developer Build tools" on the CI machine.

visual studio 2017 safemode

After I installed an extension to Visual Studio 2017 Enterprise, VS crashes on startup. In previous versions there was a /safemode switch. I tried it but it seems to be no longer supported. What can I do to suppress loading of extensions in Visual Studio when it crashes (cannot disable extensions via extension manager).
Thanks
There is still a /SafeMode switch. If this does not help you need to do a repair on visual studio 2017
https://learn.microsoft.com/en-us/visualstudio/ide/reference/safemode-devenv-exe

Universal Windows App Visual Studio 2015 Community no designer, no controls in toolbox, no properties

I am using Visual Studio Community 2015 to create Universal Windows App.
I am facing following problems-
1. No designer view.
2. No controls in toolbox.
3. Property window don't show any properties of control.
4. No phone emulators are shown after installing EmulatorSetup.exe
Visual Studio Installed Components are as follows
Microsoft Visual Studio Community 2015
Version 14.0.24720.00 Update 1
Microsoft .NET Framework
Version 4.6.01055
Installed Version: Community
Visual Basic 2015 00322-20000-00000-AA136
Visual C# 2015 00322-20000-00000-AA136
Visual C++ 2015 00322-20000-00000-AA136
Application Insights Tools for Visual Studio Package 4.2.60128.3
ASP.NET and Web Tools 2015.1 (Beta8) 14.1.11106.0
ASP.NET Web Frameworks and Tools 2012.2 4.1.41102.0
ASP.NET Web Frameworks and Tools 2013 5.2.30624.0
Common Azure Tools 1.5
JetBrains ReSharper Ultimate 10.0.2 Build 104.0.20151218.120627
JSLint.NET for Visual Studio 2.2.0
Microsoft Azure Mobile Services Tools 1.4
NuGet Package Manager 3.3.0
PreEmptive Analytics Visualizer 1.2
SQL Server Data Tools 14.0.50616.0
TypeScript 1.7.6.0
Visual Studio Tools for Universal Windows Apps 14.0.24720.00
Web Essentials 2015.1 1.0.209
I have had the same problem and the only way I have got the designer to work is (and this should work if build 10240 is acceptable for your development):
Open your project
Go under "Project" to "Properties"
Select "Application" on the left and change BOTH the target version and the min version to "Windows 10 (10.0; Build 10240)
Once you do that the XAML designer will start working again. I've had to do this on 4 different workstations and it's worked everytime.
As to why build 10568 doesn't work? Got me, agile development, will be fixed in a patch? :p
I had the same problem and could not change BOTH versions to Build 10240 as the Application listbox only showed 10586 in Properties/Application. I thought I could arrange that by editing the .csproj file, which is XML after all, but any change there makes all files in the Solution Explorer immediately unavailable. Then I noticed (running Winver.exe) that my W10 still shows build 10240 despite regularly (but not automatically) running Windows updates. Despite multiple solutions tried, this didn't change. I finally used the MediaCreation Tool to download a new Windows 10 on a USB stick and reinstalled Windows 10, preserving apps and data. And now I am really on 10586 ...and the Design mode shows again when I open my project.
I hope this helps a few!
If you are looking for the SSIS toolbox, click SSIS tab, then SSIS Toolbox.

VS2012 Error on setup on Windows 8 - Visual C++ 2012 x86 Minimum Runtime cannot be found

I am getting a few errors trying to download the new VS2012. Its a fresh install of windows 8 (did the windows update). I have tried not selecting all (no C++, lightswitch, blend, office tools)
I tried different mounting tools for the .ISO but no luck. VS2010 is still working. Running x86. Log file
Errors:
Critical: Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.507 Cannot find the requested object.
Microsoft Visual Studio 2012 Pre-Clean Tool Cannot find the requested object
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.507 Cannot find the requested object.
Microsoft Visual C++ 2012 Core Libraries, Team Foundation Server 2012, Microsoft Framework 4.5 Multi-Targeting pack.... and a few other ones cannot be found. Thanks!
Downloaded the web installer, and that seemed to work. It seems that the iso was corrupted as the MD5 did not match.

Visual Studio 2012 Premium crashes when I use the Solution Configuration Manager

Visual Studio 2012 Premium crashes when I use the Solution Configuration Manager (or drop down on tool bar) to switch from Debug solution config to Release. As soon as I make the selection to the Release config, I get a dialog with a progress bar stating it is looking for a solution to the problem and after a few seconds that dialog closes VS closes and another dialog opens that states it is restarting Visual Studio. I get this same behavior if I try to create a new configuration from within the Solution Configuration Manager; i.e., as soon as I save the new config VS crashes. During the crash I'm not given the option in the dialogs to get detailed info for the crash.
This did not happen with the same code in VS2010 and Win7.
My work-around is to modify the Debug config to be what I need for Release, and then put it back to what I need for Debug.
VS 2012 was installed on a clean (not an update) install of Windows 8. I've installed all the latest updates for both Win8 and VS. Here is the Visual Studio boiler-plate info:
Microsoft Visual Studio Premium 2012
Version 11.0.50727.1 RTMREL
Microsoft .NET Framework
Version 4.5.50709
Installed Version: Premium
LightSwitch for Visual Studio 2012, Team Explorer for Visual Studio 2012, Visual Basic 2012, Visual C# 2012, Visual C++ 2012, Visual F# 2012, Visual Studio 2012 Code Analysis Spell Checker, NuGet Package Manager 2.0.30717.9005, PreEmptive Analytics Visualizer 1.0, SQL Server Data Tools 11.1.20627.00, Web Developer Tools 1.0.30710.0