Can't resolve ip when running inside visualstudio 2022 debugger - visual-studio

As of this morning, when hitting F5 and running any debug app or service inside the debugger I cannot resolve any IP addresses. This includes multiple types of requests, AMQP, Http, etc.
If I run the same apps (even debug builds) directly they work absolutely fine. Has anyone experienced this before and got the solution?
Have tried the obvious cleaning, rebuilding, rebooting, restarting router and modem.

Well in the end it took a complete uninstall of visual studio. I also took the time to clean up my disk, install latest updates, update .NET6 and clear all repos.
I don't know if the issue was the resolution of IPs or whether that was a symptom of something else. I was getting a large number of exceptions and being taken to the screen about missing pdbs constantly.
Either way, the issue has now gone away and I'm debugging again.

Related

Connection timeout issue in Visual Studio Code

I have been facing some weird connection timeout issues in Visual Studio Code.
I am writing a simple web crawler to read a website using the requests and beautifulsoup4 packages in Python. I don't have any problem opening the URL in my web browsers (opens fine in Edge and Chrome), but when I say request.get(url), then the request always times out. Also, when I try to install some additional packages using pip, it always times out. But the corresponding PyPI page opens fine on my web browser.
The funny thing is - I am facing this issue only when I work out of my company's office. I don't have this issue at all when I am working from my home. There shouldn't be a system-wide firewall or a network firewall, because if there is, then the sites shouldn't be opening on my browsers too, right?
I went to VS Code Preferences and checked the settings there. There's no proxy set up. There is nothing specifically that would block network requests from inside VS Code. Here are some screenshots showing what VS Code Settings looks like.
I looked online and couldn't find much, since every question out there is regarding timeouts in SSH connections, which isn't relevant to me here. This official site here gives a bunch of URLs that need to be allowed by the firewall for VS Code to be able to connect to the network, but I don't know where to add them.
Is there something that I am missing? Any leads on how I can debug this issue? Or is it something that I'll have to take up with my company's network administrator?
TIA.

Clickonce App Doesn't start with Windows 1803

I have a Clickonce app from Visual Studio 2015 SP3 that is published to the network server and used in-house only. The program works just fine when launched from Visual Studio. It runs just fine on a Windows machine that does not have the 1803 update. But once a machine updates to 1803, the application no longer starts. I get the "Checking for updates..." window then nothing. On a fresh install, I usually get the Smartscreen telling me the program may be dangerous. It doesn't get that far.
I've created the Clickonce from a computer with the 1803 update and the problem still exists.
I've disconnected the machine from the network. The application starts but then has no database access and it needs the database. It's also written to hide buttons that would use the database to prevent users from trying to do things that require it.
I found a workaround (third paragraph) at https://social.technet.microsoft.com/Forums/en-US/7cbd16f5-526e-4b0b-a186-3ebf41b7b349/smartscreen-prompt-does-not-show-for-clickonce-app-since-windows-10-update-1803?forum=win10itprogeneral. When I start the application from the directory mentioned, I get the Smartscreen and can tell it to run anyway. Every time I click the desktop icon, it works just fine.
If a new release is published, the new release is downloaded and the program updated, but the Smartscreen no longer appears and the application never starts.
So somewhere between installing the latest update and the Smartscreen, this is failing. Anyone else experiencing this and have an idea as to why?
Yes, frustratingly I also experienced this today. Presumably a security update that they'll release another patch for given this is quite a pain for developers and users of small business apps.
Rather than disable Defender or SmartScreen I chose to add my deployment website to the Trusted Sites in Internet Explorer and that then re-instated the warning dialog and my app updated and ran as before.
Really annoying given the nature of the issue and how long it took to figure out, but at the same time I had to use IE today, which is a rare event nowadays.
This works for me...Warn doesnt warn anymore...
After running in the same problem, I just found that my application was going to halt after a stupid uncaught exception.
Despite the fact that the image below is in Portuguese, Event Viewer shows the right error cause.
In my case, was a corrupted settings file!
It appears as though some subsequent Windows Updates have fixed the issue on several of our PC's that were previously experiencing the issue.
Check for the updates listed here.
https://www.catalog.update.microsoft.com/Search.aspx?q=KB4338548
Running winver.exe will show you which build you have.

VS Xamarin Agent losing build host connection

I’m having an issue for the 3rd time now! VS loses connection to the mac build host. Trying to remember how it happened the other times I think it might be related to updates. Yesterday I updated to Parallels 12 and the new OSX version, 10.11.6. Please take a look at my pictures and let me know if you’ve been in this situation and how you solved.
The other times I fixed by try-and-error, so I have no idea about what was the actual fix…
By the way, I can ping, remote login is enabled and mono is set as allowed in the firewall.
Ping mac host:
Remote login:
Firewall:
PuTTY SSH working:
Everything said here is done:
https://developer.xamarin.com/guides/ios/getting_started/installation/windows/#Configuration
Any ideas?
Thanks!
EDIT:
Well, from the moment I posted this question to now it started to work again. But instead of closing this answer I'm gonna leave it open until we can find a solution for this. I'm not the only one facing this issue and it would be cool to document it for the next time it happens.
Here's the connection working now... :
We're including some reliability improvements on the connectivity between Visual Studio and the Mac build host as part of Xamarin for Visual Studio 4.2.0.
If you hit this issue again, please let me know what Xamarin version are you using, and also share the logs after the failing connection. (Help - Xamarin - Zip Logs).
If the issue is DNS related, you can try connecting by IP (adding the Mac manually) as suggested by #valtedero.
Another interesting test to diagnostic the issue is trying to build an iOS project from a developer command line, passing the ServerAddress, ServerUser and ServerPassword. That will try to connect to the Mac using the same mechanism used by Visual Studio without interference of editors, extensions or any other Visual Studio artifacts.
Finally, if you're not using the latest Xamarin version (currently 4.2.0) please give it a try, it does not only includes connectivity improvements, but it also improves the tracing around connectivity, which can give us valuable information to diagnostic other potential issues.
Thanks!

Team Foundation services are not available from server - The remote name could not be resolved

We are working with Visual Studio 2010 and Team Foundation Server 2010. We did not have any problems for about half a year, but:
Since a couple of days we get the following error: Team Foundation services are not available from server (...) The remote name could not be resolved; (...)
The problem occurs randomly (we are unable - yet - to pinpoint the conditions on which it occurs) and persists until we restart Visual Studio. The problem occurs about 8 times per day per developer.
Because we seem not to get past this problem and we cannot find anybody writing about this specific combination (the error and the 'remote name' part), I thought it wise to ask you guys about it ;) . Could anyone please help?
This is a client, server or infrastructure related problem on network level. The DNS entry for your TFS server cannot be resolved correctly at times for host dfz-vm223.
Suggestions for troubleshooting:
On some developer systems, replace the hostname dfz-vm223 by the ip-address of the TFS server. If the problem stop occuring there the DNS system is instable.
Setup a continuous ping stream (ping -t dfz-vmm223 from command window) and see if the host system is pingable in case you have TFS server problems.
Just found out what the problem was: the problem is proxy related. When we disable our proxy, the problem is gone. It appears our proxy and TFS are troublesome together. If anyone experiences the same problem and you are working with a proxy server, I would suggest you try disabling the proxy too.
I had the same problem, although I'm using VS2012 and a WAN connection to TFS.
I solved the problem by flushing the DNS cache.
To flush the DNS cache, start a command prompt with admin rights: ipconfig /flushdns
You need to do this in all the computers where the problem occurs.
I know this is old, but I had this problem sometimes when I ran Fiddler.
Sometimes Fiddler would crash or not clean up properly and the whole machine would get into some weird state where not even reboots were helping. The solution to it usually is to start Fiddler again, turn off any interceptors/collecting traffic and shut it down again.
Some of my co-workers and I had this problem as well. Out of about 25 developers, most never got this error. But three of us got it pretty consistently. The symptoms are identical, but we are using Visual Studio 2013 almost exclusively. In this version of Visual Studio, the error is preceded by the code: TF400324.
We found eventually that the three of us had all installed Productivity Power Tools 2013. And the developers that were not affected by this error had not installed it. Most had not heard of it. This used to be a very popular extension, so I have always installed it as I set up my system since about 2007. But apparently, in its modern incarnation in Visual Studio 2013, perhaps in combination with some quirk in our network or something, it can cause this problem. We have each uninstalled it, and have not gotten this error since. (It's been several months now.)
If you have this extension installed, you probably already know about it, because you probably installed it yourself. You probably started using it years ago, and it became a habit to add to each new installation. You will find that today, the default installation of Visual Studio actually includes most of its features already. To uninstall, go to Tools --> Extensions and Updates... Then click on Productivity Power Tools 2013, and click Uninstall.
Hade the same issue. For whatever reason the windows DNS Client service on my PC wasn't running. Changing it from Disabled to Automatic solved this problem for me.
Too long for comments:
First off, as #kroonwijk stated, this is an infrastructure issue. Your DNS queries are either timing out or the DNS server is not responding at certain times.
In a comment you mentioned a change over from regular machines to laptops for your entire dev team. If I had to make a bet I'd say that the DNS configuration on the laptops is not the same as what you had on the other machines.
You need to take this up with your infrastructure people. If you still have access to the older machines boot one of them up and compare the IP configuration. If not, get them to fix the problem. The DNS resolution problem could be any one of a number of factors. For example, the new machines could be pointing to an incorrect DNS server that has network issues or their might be some incompatibility between how Win7 makes DNS requests and your DNS server.
I have also experienced this problem and it doesn't always have to do with name resolution.
If you add an entry to your %systemroot%/system32/drivers/etc/hosts file for your TFS server, it removes any dependance on your name resolution servers.
If you are still experiencing the problem, then it has to do with either visual studio or one of the VS Extensions that you are running. There may be a memory leak somewhere. Disable all your Extensions using the extension manager, restart VS, and see if you still experience the problem.

VS2010 Test Runner - Unable to start agent process

I can't run any tess in VS2010. Even tests that have run before. I remember setting some services to manual start a few weeks ago, but can't remember what!
Problem: Which agent process / service do I need to start to make this work?
Edit: Even after uninstalling and reinstalling Studio2010 (and taking off the Novell Netware Client which I though may be an issue) it still doesn't work.
Got it! Avira Antivirus (even when 'disabled') seemed to be the culprit. Uninstall of the Antivirus made everything work again.
I'm using VS2015, I was experiencing the exact same error as the original poster (OP). My solution turned out to be simply turning on the add-on's within Internet Explorer so that I could start recording proper tests of my webapp. There were 3 or 4 add-on's that I simply had to enable. After I did that, this error "Unable to start agent process" never came back.

Resources