Extensions not downloading/updating - visual-studio

I'm using Visual Studio 2019 version 16.2.5 and trying to download any extension and it doesn't work so I tried to update existing extension and all my try end up with the same error this error :
so I thought that windows firewall could effected visual studio so I turn it off and still can't update or download any Extention
I also tried to close my solution and download extension but it also doesn't work, I tried to search for solution on the internet but I didn't find something useful
now I have no idea what to do to fix this problem.

(Without enough info to reproduce, I can't give a direct answer.Here are some troubleshootings and to avoid losing contact in round-trip comments, I post it as answer instead of comments)
Check if you can access the Cloud Explorer for VS2019 using IE browser, and then you can try to download the xx.vsix or xx.zip there.
If the remote name not resolved error only occurs when downloading extensions in VS, I agree that this issue is related to VS. But if we failed to download the extension from the website with IE, I think we can locate this issue is related to Internet connection issues.(Because VS actually fetch the vsix package from the marketplace just like we did manually by browser. See this similar issue. I have no idea what kind of Internet issue could result in it, but since VS use same Internet settings like IE browser, if we can't download that extension in IE, then we can't do it in VS either.
Go Tools=>Options=>Environment=>Web Browser you can find Internet Explorer options there with the note:
except for home-page settings, all changes made to IE will affect
both IE and Internal browser in VS.
So if you can't access the website and download the extension manually from VS marketplace by IE, this issue could be related to your Internet options,Corporate Firewall...
But if you can download the extension manually from VS marketplace, firstly you can double-click the xx.vsix to manually install or update the extension to VS.(If it's a xx.zip file, rename it to xx.vsix) And then run a VS repair and clean all VS cache(VS2019--16.*) to check if it helps to resolve the issue in VS.

Related

Visual Studio Debugging is stuck at "Attaching to the web server"

When I run my Web API application I get the following window:
It just stays like that indefinantly, until I hit cancel.
When I do hit cancel, this error message is shown:
I have tried rebooting, and running iisreset /restart but it does not fix it.
Any ideas what I can do to get my debugger working again?
NOTE: My Web API 2 project's Servers setting is set to Local IIS. My service is hosted by IIS and when I am not debugging, it works fine.
A possible fix:
Check the "Enable Just My Code" in Tools->Options->Debug
I just did a reset for all the settings for VS and it worked again.
Tools => Import and Export Settings => Reset All Settings
good luck!
I had this issue for Visual Studio 2017 and like with the previous post I had Debugging option "Enable .NET Framework source stepping" ticked. Un-ticking fixed the issue.
So as I commented before I had this same issue, but I now figured out the cause and have a solution.
I just got a new machine last week (this issue was actually one of the reasons why) and after a while I had the same issues, not being able to debug my projects. Luckily because I was installing all the updates one by one I was able to pin-point when it started happening.
It seems the latest update for the "Microsoft ASP.NET and Web Tools" extension breaks something.
Sadly, uninstalling or reverting the Web Tools extension is not easy: Remove this extension by going to the Windows control panel and modifying your Visual Studio installation. I had to remove Visual Studio completely and reinstall it (repair didn't do the trick).
You can update and install all your extensions as you wish, just make sure that you don't update the Web Tools extension
I tested this on my old machine and it did the trick there as well.
I've also created an Issue on GitHub as I won't be updating the extension until this is fixed, if anybody has additional information please add it to the Issue.
In Visual Studio 2015, go to Tools -> Options -> Debugging and deselect "Enable .NET Framework source stepping". This may relate to an issue with loading symbols, so if you want to keep the ability to debug .NET Framework source, then it may help to search the web for how to clear the symbol cache, or preload it, or set your symbol server, and so on.
In Visual Studio 2017, I just restarted my machine and ran the solution, no other windows opened not even a browser, although visual studio took a long time to open (30+ projects in a solution) the problem did not reoccur.
I had the same issue in VS 2017 and un-checking 'Native code' did the trick. Not sure why it was checked.
In my case I set Debugging ->Symbols -> To "Load Only Specified Modules" to include the symbols for, in my case a devops symbols feed for some internal NuGet packages
Options>Debugging>Symbols>Load Only Specified Modules
By checking the option "Always load symbols where located next to modules" the setting won't mess with the regular/classic debugging in VS for your own code
This way the Symbols are still loading where needed and Visual Studio is not trying to load debugging information for all the IIS .net dlls that were loaded by w3wp
Alternatively it can also be configured to not load symbols for microsoft.*.dll and it will also work.
Didn't see this in the current answers, so thought I'd give my 2 cents in 2022:
What worked for me:
Make sure to check that your IIS application pool hasn't been stopped (and restart it if it is), and then if that's not the case, restart your IIS server.
If you don't where those settings are, open our Internet Information Services (IIS) Manager, Application Pools are in the left-hand column, and restart/start/stop your server is in the right column.

Visual Studio 2015 Extensions Manager Index was out of range error

Env: Visual Studio 2015 Community Edition on Windows 8
Trying to open Tools --> Extensions and Updates results in the following error in a message box:
Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index
Tried running as Admin, same result.
I've tried looking at the log but nothing mentions that error.
In the log there are 3 error entries related to extensions which could be related, they say the following:
Error loading extension: Could not find a part of the path 'C:\path\to\APPDATA\LOCAL\MICROSOFT\VISUALSTUDIO\14.0\EXTENSIONS\ZW2UF5JV.JVN\extension.vsixmanifest'.
The other 2 are identical except the odd string at the end is HQ1Y5EQD.TMG and 3KWE1LJF.Z1W.
Interestingly, just before those errors in the log appear, there is a line for each saying the extension was loaded successfully but if I try to go to the path it's got listed, it doesn't exist.
I can't find any reference to those strings on my machine. I've also searched the registry but can't find any reference in there either.
I can get into the Extensions manager if I click on one of the update notifications but the original error message just displays in the main pane and I can't do anything else. I can get to the online window but as soon as I click an extension, I am prompted with the original message.
I haven't installed any extensions or VS updates for a while but my Web Compiler extension extension has stopped auto compiling JSX files which is why I started trying to look at the Extension manager. I'm guessing the issues are related.
I can still work, compiling can be done manually which is inconvenient but not the end of the world. My worry is some other extensions are also misbehaving and I just haven't noticed yet.
Don't really want to re-install VS as a) it took ages last time and b) it might not fix the issue. Is there any good advice on troubleshooting the error or anything else I can try before I re-install?
I refreshed the GitHub extension on VS 2015 and got this error. Deleting the two cache files:
extensions.en-US.cache
extensionSdks.en-US.cache
from the AppData\Local\Microsoft\VisualStudio\14.0\Extensions causes them to be rebuilt and eliminates the error.
No reinstall needed.
Problem got worse, I started getting the error message when starting Visual Studio and things like the package manager wouldn't load. Each restart seemed to yield a different combination of windows not loading, sometimes Solution Explorer, sometimes Team Explorer etc. Not good.
A repair to VS 2015 via the Control Panel took a while but didn't help, same problems.
I ended up completely uninstalling and trying to re-install. However the installer threw an index was out of range error but weirdly VS 2015 was now listed as an installed application again.
So I'm guessing the original uninstall left some problematic files lying around which messed up the next install. So I uninstalled again, renamed Microsoft Visual Studio 14.0 folder, cleared all files from AppData\Local\Microsoft\VisualStudio\14.0\Extensions and re-installed.
It installed and ran fine.
The problem I now had was that I couldn't find the SQL Server Object Explorer window anywhere. I tried repairing SQL Server Data Tools but still no luck. So I uninstalled SSDT and then re-installed. This seemed to fix it.
Now I realised I also couldn't connect to Azure through the Server Explorer window, the option was simply not appearing in the list like it used to. This time a repair to Azure Tools for Microsoft Visual Studio 2015 - v2.9 and a repair to Azure App Service Tools v2.9 - Visual Studio 2015 fixed that problem.
I confronted same issue and found this thread. I tried the above suggestions, but unfortunately, it went all unsuccessful. I even tried to uninstall/install with even worse result as Visual Studio became unable to start due to new "missing components" issue. Reinstallation was nothing better.
I finally came by a piece of magic. It was Visual Studio Uninstaller which although would remove all your installed extensions, it would perform a complete cleanup. It would save you from installing new Windows (at least it was my case.
Just go to releases and download the first zip file
This way you will be able to perform clean install of Visual Studio.

Visual Studio 2013 breaking Web Site

I have a really weird problem, be interested in some pointers
We have a website that we have coded from Visual Studio 2003 -> Visual Studio 2010. We are now looking at moving to 2013.
The website is in IIS, when I navigate to it using IE it works. When VS2013 is -open-, not running, but has the project open we get a weird effect where the contents of the website gets duplicated by 3, its as if there are 3 iframes on the page, all with a copy of the same web site.
I close VS2013 and it goes back to normal
So, just to be clear, we don't even have to run the web site from within VS2013, just the project being open is enough to cause the weird effect
We use subversion as as far as I can tell no files have been modified when VS2013 is open
Any suggestions?
Thanks
It's Browser Link that's doing it! If you switch off Browser Link it works.
The source shows some extra script entries before the final tag but other than that the whole source is duplicated.
We don't need Browser Link and I don't have reflection capabilities on Asp.Net source so as to why that's for some one else to determine, I noticed a few people complaining when I searched on it so it may be something that just gets fixed in a future version

TF30063: You are not authorized to access Collection. Nuget and Tfs conflicting

Latest Comment
I believe my problem occurs when using Nuget, however, if you are reading because of the TF30063 error. Have a look at the answer I provided and accepted.
Original Post
I am getting this error message when I try to check out. This happens randomly and can occur even if minutes ago the same instance of visual studio allowed me to check something else out for edit.
The current workaround is to reopen VS2010.
Using W7x64, vs2010 ultimate with TF2010 and sql2008 on my local dev machine. I am not part of a domain. I am the administrator of this computer.
Additional 2011-08-09
When the problem occurrs, I "close solution" under file. And then reopen the solution. I then get a uid/pwd box. I put my admin uid/pwd into it and then get a further error message. Again, closing vs2010 and reopening solves the issue.
Additional: 2011-08-30
I believe this has to do with nuget. I have provided an answer and so far after many months I have not had a TFS error. Where I should have had an error given the types of operations I have been performing which were identical to the scenarios making it fail.
I noticed that the problem occurred mostly after i installed a nuget package. After adding a nuget package i found that I could not check out. Restarting Visual Studio helped.
Based on this discussion:
http://nuget.codeplex.com/discussions/254328
i used this solution which appears to be working:
(I have copied the solution here if ever the webpage disappears)
Control Panel / Internet Options / Security Tab
Select "Local Intranet"
Click Sites button
Click Advanced Button
Add your TFS server http address to the list. e.g. http://tfs
Restart Visual Studio
Source: http://blog.rthand.com/post/2011/08/26/Fixing-combination-of-NuGet-and-Team-Foundation-in-workgroup-configuration-401-Unauthorized.aspx (Go straight down to The Solution half way down).
Don't let the Internet Options part fool you. I do not use Internet Explorer and this solved my issue.
I found this issue and the accepted solution didn't work for me. For me the problem occurred when trying to add a NuGet package to my project (through either the console or the GUI) and it would show the login prompt but not accept my user/password. It would try around 4 times and then fail and roll back the installation.
It turns out for me the issue was that I had Fiddler open and as soon as I closed it (to undo the proxy settings) I was then able to install the package without any issue. I didn't even have to restart Visual Studio to get it working.
Just thought I'd share this for the next person who comes across this issue.
I want to add a solution for people who are using VisualStudio online. My problem was that I was logged into VS2013 with the wrong Microsoft Account.
I would like to point that the accepted solution didn't work for me - probably it is for IE users.
My fix was to "clear the package cache"
Open VS
Go to Tools-> Options
Open "NuGet Package Manager" and select General
Click in the button: "clear the package cache"
When I had this problem I checked Event Viewer on my TFS machine and it showed a bunch of insufficient permissions Windows Sharepoint Service errors. I ended up just disabling the Sharepoint aspects of TFS since I wasn't using them anyways.
Got the error TF30063: You are not authorized to access Collection when comparing or merging the solutions in tfs 2012.
I found that enabling and disabling the windows authentication in IIS did randomly fix the error but found the disk space issue,
Once i cleared it, and enabled the windows authentication for TFS in IIS, it was a fix for me.!
-Pasha
This answer got me far enough to solve:
Control Panel / Internet Options / Security Tab Select "Local
Intranet" Click Sites button Click Advanced Button Add your TFS server
http address to the list. e.g. http://tfs Restart Visual Studio
On our internal network, for some reason, our computers don't always recognize other computers as being part of the domain - resulting in connections being sporadic/intermittent. My user had a restricted list set by domain policy, so I couldn't edit it. However, I could change the connection from just the computer name to the computer's fully qualified domain name and that appears to have solved the problem.

Visual Studio 2010 hangs when opening websites

My Visual Studio 2010 Professional hangs up 99.999% of the time when I try to open a website as "Remote Site" through an HTTP address. However if i open the site through a unc path instead of through HTTP, it works fine. Of course that is not always feasible, for example when working from offsite. The same sites (assuming they are not NET40 sites) work fine in Visual Studio 2008, so I'm pretty sure it is not a problem with the Front Page Server Extensions.
If i run 2010 in /safe mode, it opens the projects fine. So i figured maybe it was one of my installed extensions. I therefore disabled all my extensions and tried again, but it still hangs up. So it is apparently something in Visual Studio itself that is different between safe and normal modes.
I ran it in logging mode, and checked the log but did not see anything that stuck out to me. The log is uploaded here: http://pastebin.com/aUnVanB1 .
The exact symptoms I am seeing are that when i click on the project name, it pops up and asks me for my credentials. I enter those, and click OK, and it then loads the solution explorer, and i see the tree view, but then it just hangs with the progress dialog that says "Preparing Solution...". The progress bar keeps cycling, but it never finishes loading, and the spot where the properties window would be in the VS UI is completely unpainted, with just a blank, empty, white space.
Any one have any clue what else i could do to try to figure out why 2010 hangs when attempting to load websites via HTTP? Thanks!
Thanks for your question... you gave me the right clue to solve my problem!
My VS 2010 was hanging (in fact was very slow to get available) when I was openening a solution containing a remote website and I was due to press Escape a few times to cancel the pending operation... As you suggest I tried to open such a solution with /safeMode and VS2010 became available quite instantly.
So as you pointed the VS Extensions... I checked mine (all from Telerik): opening the extension manager I discovered that some updates where available. I thought the extensions updates were automatically proposed and so never checked that before. In fact, you need to manually check with the extension manager if some are available.
I've updated all my Telerik extensions... and now I may open normally all solutions including a remote website.
Thanks a lot! Perhaps... you need to updates your extensions???
Check you network order preference in Windows.
I had a similar problem where DNS would cause a hang of 1 minute before trying again (and again and finally on the next network).
Under Network, Advanced Settings (WinXP):

Resources