I am trying to automate a Windows build in AWS Codebuild which require downloading Windows SDK with Debugging Tools for Windows installed.
I am able to install the Windows SDK using Visual Studio with some other files required.
powershell -c "Start-Process -FilePath 'vs_community.exe' -ArgumentList \"--quiet\",
\"--norestart\" , \"--add Microsoft.VisualStudio.Workload.Universal\",
\"--add Microsoft.VisualStudio.Workload.NativeDesktop\",
\"--add Microsoft.VisualStudio.Component.VC.ATLMFC\",
\"--add Microsoft.VisualStudio.Component.Windows10SDK.19041\",
\"--includeRecommended\" -Wait;"
The build requires Debugging Tools for Windows enabled in Windows SDK which is straightforward in UI installation. But since I want to automate this, I am looking for a command line option to install Debugging Tools for Windows in Windows 10 SDK.
I was able to install Debugging Tools for Windows via standalone windows sdk installer through command line as below:
powershell -c "Invoke-WebRequest -Uri 'https://go.microsoft.com/fwlink/?linkid=2120843' -OutFile winsdksetup.exe -UseBasicParsing ;"
winsdksetup.exe /features + /q /norestart
/features + selects all the features available in Windows SDK to install.
Related
I want to install VS Build Tool 2022 with the following components:
.NET Desktop Build Tools
Exclude .Net Framework 4.8 targeting pack
Web development Build Tools
Node.js Build Tools
Include optional
I do not know currently how to exclude the .Net Framework 4.8 targeting pack, but I thought I understood how to do the rest and here is the script I created based on the information in https://community.chocolatey.org/packages/visualstudio2022buildtools-preview:
[System.Net.ServicePointManager]::SecurityProtocol = [System.Net.ServicePointManager]::SecurityProtocol -bor 3072
iex ((New-Object System.Net.WebClient).DownloadString('https://community.chocolatey.org/install.ps1'))
$Components = #(
"Microsoft.VisualStudio.Workload.ManagedDesktopBuildTools",
"Microsoft.VisualStudio.Workload.MSBuildTools",
"Microsoft.VisualStudio.Workload.NodeBuildTools;includeOptional",
"Microsoft.VisualStudio.Workload.WebBuildTools"
)
$InstallerArgs = "--add " + ($Components -join " --add ")
choco install visualstudio2022buildtools -y $InstallerArgs
Unfortunately, it only installs the bare minimum. The rest I have to do manually through the VS Installer.
So my script must be wrong, but where is the problem?
To pass the arguments down to the vs_buildtools.exe installer you need to include the --params option.
choco install visualstudio2022buildtools -y --params $InstallerArgs
I have Windows running in a VMware VM, to which I connect via SSH. I can run a Command Prompt or a PowerShell. I'm trying to follow the instructions to install Visual Studio 2017 Build Tools from a command line. I download the installer from https://aka.ms/vs/15/release/vs_buildtools.exe and name it vsbt2017.exe, the "installation channel" from https://aka.ms/vs/15/release/channel and name it vs2017.chman, and I create an empty directory for the installation at C:\vs2017.
When I try this command in Command Prompt, it does not return immediately, waits a few seconds, then returns. My install path remains empty. No error message is printed to the terminal. %ERRORLEVEL% is 1.
start /wait .\vsbt2017.exe --quiet --wait --norestart --nocache --installPath C:\vs2017 --channelUri C:\vs2017.chman --installChannelUri C:\vs2017.chman --add "Microsoft.VisualStudio.Workload.VCTools;includeRecommended"
When I try this command in PowerShell, I get the same results. The analog of this command works for me for VSBT 2019, so it's really puzzling why it doesn't work for 2017.
Start-Process -FilePath C:\vsbt2017.exe -ArgumentList "--quiet --wait --norestart --nocache --installPath C:\vs2017 --channelUri C:\vs2017.chman --installChannelUri C:\vs2017.chman --add Microsoft.VisualStudio.Workload.VCTools;includeRecommended" -Wait -PassThru
If it makes a difference, I already have VSBT 2019 installed on this VM, but I've read in Microsoft's documentation that multiple versions can be installed simultaneously.
Almost two years ago, I asked a similar question about the 2019 Build Tools installer. This time, I need to install the 2017 Build Tools. The reason is that I need to figure out why someone else's installation of Visual Studio 2017 doesn't work, so I need to test with their version. "Just install Visual Studio 2019" is not an acceptable answer to this question.
Need to install Visual Studio for school, but run into this and one other error.
Visual Studio fails to install "Microsoft.Net.CoreUWP,version=1.1.32" and "Win10SDK_10.0.16299,version=10.0.16299.0".
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log for "Microsoft.Net.CoreUWP,version=1.1.32" :
Package 'Microsoft.Net.CoreUWP,version=1.1.32' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Microsoft.Net.CoreUWP;PackageAction=Install;ReturnCode=1316
Details
MSI: C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.Net.CoreUWP,version=1.1.32\netfx_NETCoreUWP.msi, Properties: REBOOT=ReallySuppress ARPSYSTEMCOMPONENT=1 MSIFASTINSTALL="7"
Return code: 1603
Return code details: Fatal error during installation.
Message Id: 1316
Message Details: The specified account already exists.
Log
C:\Users\Kaleb\AppData\Local\Temp\dd_setup_20180123192925_162_Microsoft.Net.CoreUWP.log
Impacted workloads
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.0.27128.1)
Impacted components
Universal Windows Platform tools (Microsoft.VisualStudio.Component.UWP.Support,version=15.0.26906.1)
Universal Windows Platform tools for Cordova (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.0.27005.2)
Universal Windows Platform tools for Xamarin (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.0.27005.2)
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Log for "Win10SDK_10.0.16299,version=10.0.16299.0" :
Package 'Win10SDK_10.0.16299,version=10.0.16299.0' failed to install.
Search URL
https://aka.ms/VSSetupErrorReports?q=PackageId=Win10SDK_10.0.16299;PackageAction=Install;ReturnCode=1316
Details
Command executed: "c:\windows\syswow64\\windowspowershell\v1.0\powershell.exe" -NonInteractive -NoLogo -NoProfile -ExecutionPolicy Bypass -InputFormat None "$ErrorActionPreference="""Stop"""; $VerbosePreference="""Continue"""; $CeipSetting="""on"""; $ScriptPath="""C:\ProgramData\Microsoft\VisualStudio\Packages\Win10SDK_10.0.16299,version=10.0.16299.0\WinSdkInstall.ps1"""; $SetupExe="""winsdksetup.exe"""; $SetupLogFolder="""windowssdk"""; $PackageId="""Win10SDK_10.0.16299"""; $LogFile="""C:\Users\Kaleb\AppData\Local\Temp\dd_setup_20180123192925_181_Win10SDK_10.0.16299.log"""; $SetupParameters="""/features OptionId.AvrfExternal OptionId.UWPManaged OptionId.WindowsSoftwareLogoToolkit OptionId.SigningTools OptionId.UWPLocalized OptionId.UWPCPP OptionId.DesktopCPPx64 OptionId.DesktopCPPx86 OptionID.DesktopCPPARM OptionID.DesktopCPPARM64 OptionId.MSIInstallTools /quiet /norestart"""; (gc $ScriptPath | out-string) | Invoke-Expression; if (!$?) { exit 1603 } elseif ($LastExitCode) { exit $LastExitCode }"
Return code: 1316
Return code details: The specified account already exists.
Log
C:\Users\Kaleb\AppData\Local\Temp\dd_setup_20180123192925_181_Win10SDK_10.0.16299.log
Impacted workloads
Desktop development with C++ (Microsoft.VisualStudio.Workload.NativeDesktop,version=15.0.27102.0)
Universal Windows Platform development (Microsoft.VisualStudio.Workload.Universal,version=15.0.27128.1)
Impacted components
Universal Windows Platform tools (Microsoft.VisualStudio.Component.UWP.Support,version=15.0.26906.1)
Universal Windows Platform tools for Cordova (Microsoft.VisualStudio.ComponentGroup.UWP.Cordova,version=15.0.27005.2)
Universal Windows Platform tools for Xamarin (Microsoft.VisualStudio.ComponentGroup.UWP.Xamarin,version=15.0.27005.2)
Visual C++ tools for CMake (Microsoft.VisualStudio.Component.VC.CMake.Project,version=15.0.27019.1)
Windows 10 SDK (10.0.16299.0) for Desktop C++ [x86 and x64] (Microsoft.VisualStudio.Component.Windows10SDK.16299.Desktop,version=15.0.27128.1)
Windows 10 SDK (10.0.16299.0) for UWP: C#, VB, JS (Microsoft.VisualStudio.Component.Windows10SDK.16299.UWP,version=15.0.27128.1)
Windows 10 SDK (10.0.16299.0) for UWP: C++ (Microsoft.VisualStudio.Component.Windows10SDK.16299.UWP.Native,version=15.0.27128.1)
Update:
In this page there is some info about Error 1316. the specified account already exists:
Are you installing with full administrative rights? To make certain
that you are, right-click the installer and select Run as
administrator.
The next most likely explanation is some bad registry entries:
Microsoft offers a tool to solve these sorts of install and uninstall
problems; please see Fix problems that block programs from being
installed or removed.
When the fix-it tool asks what you're trying to
install, select "not listed" unless you're installing the exact same
version that was previously installed. For example, both 7.5.0 and
7.5.1 would show up as 7.5 in the list in the fix-it tool, but they are different installers so you would select "not listed" if you're
installing 7.5.1 over 7.5.0.
Older Section:
If above solution dose not work for you, read this part:
Based on your provided log, It seems in this case ยป the Visual Studio Setup program need to uninstall netfx_NETCoreUWP.msi and Win10SDK from your computer but it can not do it, so you can help it with uninstalling them manually (with your risk):
Close Visual Studio Setup program
Go to C:\ProgramData\Microsoft\VisualStudio\Packages\Microsoft.Net.CoreUWP,version=1.1.32
Right click on netfx_NETCoreUWP.msi and select Uninstall.
For the second error I think you should open Programs and Features from Control Panel and uninstall Microsoft Software Development Kit - Windows 10.0.16299 from there.
Run Visual Studio Setup program again and go ahead..
I'd like to install the Visual Studio 2013 Update 4 Remote Tools on a Windows 2012R2 Server running IIS 8.5. This is a pretty simple process outlined here: https://msdn.microsoft.com/en-us/library/bt727f1t.aspx
The problem I have is that the server I'm trying to installing this on is a Server Core, meaning, there is no GUI. The Remote Tools application is an exe that only installs via GUI.
I've tried to install it with PowerShell and it just hangs. I'm also not able to find the Remote Tools in Web Platform Installer to install it that way. Extensive Googling has turned up nothing.
Does anyone know how to install the Visual Studio Remote Tools on a Server Core so that I can debug on my DEV server? Any advice is appreciated.
Create a .bat file and enter the below. (not PowerShell) (Or just at the command line.)
rtools_setup_x64.exe" /install /quiet
word...
You don't have to install remote tools. Just copy msvsmon.exe, from your local Visual Studio installation. Then start it from remote powershell silently:
Start-Process -FilePath .\msvsmon.exe -ArgumentList '/nosecuritywarn /port:4022 /silent' -Verb runAs
Don't forget to open firewall port.
Turns out that you can simply remote into the Core server. When you do so, you'll get a command prompt only. From there, CD to the directory where the remote tools install file is. Execute the file by typing the file name at the command prompt, ie: rtools_setup_x64.exe.
This will run the installer, with a GUI, on the Core server. Its that simple, I didn't think you'd be able to get the install wizard on a Core server, however you do.
I have just started Windows Application Development and have installed Visual Studio 13 and Microsoft sdk 8.I am experiencing problems in Deploying the the app on the emulator.It says that Hyper V is not enabled on my pc. When i searched this error on the internet i found out thAt hyper v is windows 8.1 pro only feature and i have windows 8.1 single language and i don't want to upgrade because of monetary reasons.
So i just to know is there another way through which i can proceed app development on my computer either by using another emulator or any other way possible.
I read about oracle vm also but couldn't figure out to connect it to my visual studio 2013.
You could develop on a VirtualBox virtual machine which has a trial version of Windows 8 installed. You install the trial Windows 8, Visual Studio and SDKs on the VM, and do all development there. It's slower, but it works for us.
To make the creation and maintenance of the virtual machine image easier, there are some things you can do. First, start with a vm image from the IE team. Next you can install Chocolatey and find and install packages for Visual Studio and the SDKs you need. If you use source control and use these technologies, provisioning a new development VM should become very quick.
The recipe I use to make development Windows boxes goes something like this:
On your machine
Install Chocolatey
In elevated Powershell: iex ((new-object net.webclient).DownloadString('https://chocolatey.org/install.ps1'))
Run elevated: choco install virtualbox
Download Win8.1 virtual box image and run it
On the Win8.1 VM
Install Chocolatey (as above)
Run the following in an elevated command to provision:
choco install virtualbox.extensionpack
choco install visualstudio2013professional
choco install windows-sdk-8.1
dism.exe /Online /Enable-Feature:Microsoft-Hyper-V /All