I've been running local Visual Studio using HTTPS for years just fine.
I am using Visual Studio 2022 17.3.4.
As of a couple weeks ago, when I run Visual Studio local debug, I get "security certificate invalid". It thinks certificate expired Aug 29, 2022. Running
dotnet dev-certs https --check
shows valid certificate until 2023-09-14.
Any ideas as to why HTTPS will not run local?
Related
I updated macos to version 13 Ventura. I'm developing apps using Xamarin/MAUI on Visual Studio on Windows. Access to macOS over the network is no longer possible. Error message: Unable to connect to SSH using the SSH keys. I have enabled remote access to macOS.
Please ne noted that macOS 13 (Ventura) ships with OpenSSH_9.0p1.
You can try to edit /etc/ssh/sshd_config and save it.
HostkeyAlgorithms +ssh-rsa
PubkeyAcceptedAlgorithms +ssh-rsa
And then restart the Mac and Visual Studio.
This was an bug on Visual Studio 17.3.4 (see https://developercommunity.visualstudio.com/t/macOS-Ventura-130-Beta---Impossible-to/10163760?q=%5BFixed+In%3A+Visual+Studio+2022+version+17.4%5D) that is fixed on 17.4.0, so update to Visual Studio 17.4.0 and the error is gone.
Installing Votive, an extension for Wix - Windows Installer fails for both Votive 2017 and Votive 2019 Visual Studio extension. The reason is a certificate validation error. How can you update your root certificates and install the Visual Studio extension without getting certificate validation error?
It was possible to install Votive using the following Powershell commands to refresh the root certificates with Windows Update.
mkdir c:\certs #temporary folder where the certificates will be installed/updated
cd c:\certs
certutil.exe -generateSSTFromWU roots.sst
$sstStore = ( Get-ChildItem -Path C:\certs\roots.sst )
$sstStore | Import-Certificate -CertStoreLocation Cert:\LocalMachine\Root
The -generateSSTFromWU option downloads all certificates into a .sst file that can be opened with MMC by double clicking, but I ran the Powershell commands listed above to also get all certificates installed.
After doing this, Votive extension installed and I could open the Visual Studio solution with the .wixproj Wix project inside. This worked for both Votive 2017 and Votive 2019.
It is possible to install WixToolset with Chocolatey, but I needed the Visual Studio Extension - called Votive.
vs_installershell.exe has an invalid certificate. Error when trying to update, open, repair or reinstall; and now I can't open Visual Studio!
I tried the post from the Visual Studio Community but, when I click the asked update button, it loads then it stops working. View article.
Error Messages:
1) vs_installershell.exe has an invalid certificate
2) Visual Studio 2019 has stopped working
3) Visual Studio Installer has stopped working
Probably due to a pending Windows update not being installed. Solution recommended by MSDN:
Please go to windows update and make sure all pending windows update
are installed and reboot the computer, then go to C:\Program Files
(x86)\Microsoft Visual Studio\Installer then run vs_installershell.exe
as administrator.
just delete Vs_installer.exe and Vs_installershell.exe from the address below and then run Visual Studio setup again which subsequently copy the installer to the same folder :
C:\Program Files (x86)\Microsoft Visual Studio\Installer
then run the installer if you want !
I have a problem with installation of Remote Tools for Visual Studio 2015 update 3 on Windows Server 2008 R2 that does not have connection to the Internet.
Installator showed following error: "0x800b010a - A certificate chain could not be built to a trusted root authority."
Log contains following errors:
Error 0x800b010a: Failed authenticode verification of payload: C:\ProgramData\Package Cache\.unverified\rdbg_std_amd64
Error 0x800b010a: Failed to verify signature of payload: rdbg_std_amd64
Failed to verify payload: rdbg_std_amd64 at path: C:\ProgramData\Package Cache\.unverified\rdbg_std_amd64, error: 0x800b010a, delete: Yes
Error 0x800b010a: Failed to cache payload: rdbg_std_amd64
Failed to cache payload: rdbg_std_amd64 from working path: C:\Users\MKEDRZ~1\AppData\Local\Temp\2\{ec7a2821-b103-4c27-ade2-549182ab4d32}\rdbg_std_amd64, error: 0x800b010a.
I've tried to install Remote Tools for Visual Studio 2015 update 1 and I succeed but it gives me nothing because we use VS 2015 update 3 and to do remote debugging, I have to have Remote Tools for Visual Studio 2015 update 3
The issue is due to some root CA certificates missing from the offline box. Same things happen when trying to install recent Visual Studio versions. I solved it by manually installing the certificates as described in https://stackoverflow.com/a/34109313
Copy the whole of
C:\Program Files\Microsoft Visual Studio 14.0\Common7\IDE\Remote Debugger\x86
to the remote machine. Use the x64 subdirectory to debug 64bit executables. And obviously replace the 'C:\Program Files' part with wherever VS2015 is installed.
When I try to use the TFS 2015 Build process to deploy the Test Agent, I am receiving the following error:
‘The running command stopped because the preference variable
“ErrorActionPreference” or common parameter is set to Stop: Cannot
find path ‘C:\Program Files (x86)\Microsoft Visual Studio
14.0\Common7\Ide\DTAExecutionHost.exe.config’ because it does not exist.’
I have Visual Studio Professional 2015 Edition installed on D drive and using TFS 2015 Test agent is getting installed on C drive.
As VS2015 Professional is installed on D driver so “DTAExecutionHost.exe.config” exists in D driver.
Is there any means by which we can configure Test Agent on D driver using TFS 2015 as I cannot uninstall VS2015 Professional on server.
There is no such setting to configure Test Agent on D Driver in step Visual Studio Test Agent Deployment.