We have a Xamarin app that has been working for years. It communicates with a WebService using https and has its SSL/TLS implementation set to Native TLS 1.2+. Up to this week we had been building the app in Visual Studio 2017. So far no problems.
This week we upgraded to Visual Studio 2022. We rebuilt the app without changing anything in the code and using the Visual Studio debugger ran it on our test device. Immediately we began to get the error 'ConnectFailure (TLS Support not available.)' when we tried to connect to the webService.
I checked the server on which the webService is hosted and it appears to have TLS 1.2 enabled and anyway it worked ok last week when the 2017 built app had the exact same SSL/TLS setting.
What is different about Visual Studio 2022?
Related
Visual Studio 2017 V.15.2 Hangs When Disable Internet Connection.
I used Re-sharper 2017.1.2
Solution ?
Visual Studio 2017 15.2 (26430.12) is now available for download. The latest update brings bug fixes and performance improvements. The new version fixed an issue where Visual Studio freezes without a network connection as well as added support for Service Fabric 5.6 release/2.6 SDK which enables using ServicePackageActivationMode=”ExlusiveProcess”.
I have been using Visual Studio 2013 Professional. Yesterday I decided to also install Visual Studio 2017 (after its release) along side for evaluation.
All went well until I realized that my existing IIS7 hosted website was not accessible via HTTPS.
I tried messing around with certificates in mmc and browsers etc with no luck.
How to fix this?
It turns out all that I needed to do was to delete my existing 443 binding on my website and then simply re-add it again!
I've updated my Visual Studio 2017 to latest version (RC.4+26206.0) this morning since then my asp.net core api stopped working.
In chrome I see error: net::ERR_CONNECTION_RESET or if I run it on Kestrel instead of IIS Express I see net::ERR_INCOMPLETE_CHUNKED_ENCODING.
I didn't change anything else.
Did anyone encounter this issue?
I have been facing a problem of freezing Visual Studio 2015 frequently during building a Xamarin Android project and each time I have to kill Visual Studio process and start the building process again then it will work. I'm facing this issue with two machines both of them are Windows 10 Pro .
I'm using:
Visual Studio 2015 Community update 3.
Xamarin 4.2.0
Xamarin.Android 7.0.1.6
I have the same problem and can't find the source of why visual studio hangs while developing Xamarin android project.
Specs:
Visual Studio Professional 2015 with latest update
Windows 10 64-bit
Dev Express Included
ReSharper Installed
Visual Studio 2013 also installed on machine
16 GB Ram
Intel i7 6700 CPU 3.40 GHx
Git for source control
jdk1.7.0_55
Xamarin latest version
The designer also hangs crazy time
In event viewer I can see that vs studio hangs
The program devenv.exe version 14.0.25420.1 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Security and Maintenance control panel
I tried the following attempts and did not helped me:
1.Reinstall (windows + visual studio).
2.Reinstall vs with Xamarin.
3.Update to latest version of Xamarin and vs
4.I also deleted the C:\Users\ ...\AppData\Local\Microsoft\VisualStudio\14.0 directory and i just
lost my settings and some configuration with no effect. Also VS extensions have been removed
5.Deleted my anti virus did not helped
6.No firewall anymore disabled it
7.Disabled windows defender
8.Removed Resharper
The only solution i have is :
Kill vs and restart... but this in annoying since to many times it hangs
Before you go re-installing everything...
I've also experienced Visual Studio (2015 Update 3) hanging while starting a debug session into my Xamarin Android project.
It appears that Visual Studio is having some timing issue between the deployment and connecting to the debugger. What is working for me...
1) Open Task Manager and Kill Visual Studio (because it's hung, and this is the only way I know how to get it out of this state), then...
2) Keeping the Android Hyper-V instance running from my last debug attempt, re-open my project and start a new debug session.
Perhaps Visual Studio is failing to connect to the ADB (Android Debug Bridge)?
I've been developing a Web Forms ASP.net web application in Visual Studio 2013 without any incident for some time now, but recently I attempted to upgrade to Visual Studio 2015 and now every time I launch the project I get stuck waiting for a request. This isn't a server response (like 500 or 404) it just never responds. To try and isolate this I've uninstalled every copy of Visual Studio (I had 2012, 2013 and 2015 installed), deleted the %userprofile%\DocumentsIISExpress folder, reinstalled just VS 2015, and created a completely empty web project (with just the default Web Forms boilerplate). Here is a screen shot of what I am experiencing:
I have had the same problem after installing Visual Studio 2015 Update 1. As it turns out, VS 2015 removes IIS Express 8.0, which was included with Visual Studio 2013, and installs IIS Express 10.0. For some reason, this version of IIS Express does not work for some developers.
visual studio iis express not working
iisexpress hangs when starting MVC project
Visual Studio 2015 Update 1 - No IIS Express Response While Debuging
As a workaround, I ended up uninstalling IIS Express 10.0 from the Programs and Features control panel, and re-installed IIS Express 8.0. It is available as a separate download from Microsoft.
This appears to have resolved the issues I was experiencing, however I do not know if there are features in iis express 10.0 which vs2015 relies on for debugging and app execution. In the extremely limited testing that I've done with VS 2015 and IIS Express 8.0 everything appears to be working fine YMMV.
UPDATE:
While refreshing my OS I noticed that IIS Express 10 was working properly. But when I installed IIS from the Windows Programs and Features dialog, express stopped working and behaved as described above. Others have noticed this coincidence as well.
Uninstalling IIS and reinstalling IIS Express 10, in my case, allowed me to debug my web application with IIS Express 10. As always YMMV.