Unable to download any Microsoft Visual Studio 2019 Extension - visual-studio-extensions

This issue has been there for a while now. My internet connection is very good. However, I am unable to download any VS marketplace extension. I am able to get all extension lists from VS, but always unable to download it from Extensions -> Manage Extensions or even from VS marketplace website

I am able to get all extension lists from VS, but always unable to
download it from Extensions -> Manage Extensions or even from VS
marketplace website.
When you click the Update button in VS Extensions Manager UI, it actually downloads the xx.vsix from VS Marketplace website. So I think the root cause is that you can't download the extension from the website, and it could be something wrong with Internet Connection. You can try to access the marketplace website with IE browser to check this point.
I assume this issue is similar to Error caused when trying to Installing package in .Net, it might be something wrong with your DNS or proxy, or maybe the settings in your firewall corrupt the download. I think that's why your Internet is good but can't access the website well.
And if you can't resolve the Internet issue in short time, I suggest you can try to install the extension you need by another machine which can access the website successfully. An extension is a xx.vsix package, you can install it from the website by another machine and copy the xx.vsix to your current machine, double-click it to install or update automatically. (And if it works, it actually indicates something is wrong with your Internet.)
Hope it helps :)

Related

Problems publishing site to localhost on windows 2008 rs server

I must preface this post by saying that I am not an experienced developer, I am in the process of learning through trial and error and a lot of google searches so detailed (step-by-step) feedback would be greatly appreciated. I created a website, which does not use a database, using visual studio 2015 and I am attempting to host it locally on a Windows 2008 R2 server.
I installed IIS and loaded the asp.net v4.0 framework. The site works fine, produces no errors when I test it and works after being published only if the visual studio is still running.
However, when I close the Visual studio and open my browser window to http://localhost:50044 (which is the URL listed in properties menu in VS), I also tried using port :80 and nothing. When trying to add Web Site via the IIS management utility I receive the following authentication error: ”Cannot verify access path (C:\Inetpub\wwwroot).”
I checked the permissions and windows authentication is enabled with read access, and all other permissions seem to be correct. I am at a loss, I'm sure it is probably something simple that I am missing due to my lack of knowledge and experience. Any help would be appreciated.
It's sounds like you are running on IIS express which in your case stops running when you close visual studio. Normal process is create a new website in IIS and point to the folder where your web.config is. You can then hack your host file (C:\Windows\System32\drivers\etc) so DNS works. Add an entry like "127.0.0.1 mytestwebsite.com". I hope that helps
So I figured out part of what was happening. I didn't realize that visual studio has built in IIS and was using that by default.
I ran VS as an admin, created a new project, then attempted to create a virtual directory thru VS under the project/properties/web tab. I selected local IIS and entered http://localhost/boc and it returns an error: unable to create vd. Web server http://localhost... Could not be found.
I then went in to the IIS manager and set up a virtual directory with no issues. However, when I attempt to reference it thru VS I again receive an error message.
Any ideas?

Can't load DotNetNuke (DNN) Install Wizard - .js,.css 404 errors

I'm attempting to install a fresh installation of DNN, to evaluate it as well as extend it with custom functionality. The end goal is to gain knowledge on how it behaves prior to receiving a DNN-based product from a third party developer. I've been stumped right from the outset, so am reaching out to the forum for some help.
Problem Statement
I am unable to install DNN at all, because the installation wizard does not load properly, and is missing some controls. It doesn't load most external resources (.css, .js, etc), and inspecting the headers shows those resources are returning 404 errors. Notably, the browser continually (over 1000x) attempts to load dnn_logo.png, each time returning a 404. I would like to know how to install/configure the site source files so that the installation wizard works properly, and I can continue the installation process. I am using the "Installation Package" variant of the software.
Problem Background
I checked the path of dnn_logo.png and it does in fact exist.
I've been using this guide to install the site: http://www.dnnsoftware.com/wiki/page/install_dotnetnuke (the 2nd section, with separate DB).
My installation environment: Win7 x64, IIS 7.5; SQL Server Express, named instance, using windows auth
DNN version: 7.3.1
Installation folder permissions are:
IIS AppPool\DotNetNuke --> modify
NT Authority\Network Service --> modify
SQL Permissions: both users above are set as db_owner for the database
Attempted Resolution Steps
Followed the written tutorial, as well as four installation videos authored by the DNN team
Reinstalled the site three times - first was using outdated v.7.3, 2nd selected the "unblock" option when unzipping the source
Adjusted folder permissions and double checked them; for user DotNetNuke
Added user Network Service with permissions, according to the info in the linked doc
Adjusted web.config and turned off URL rewriting; ended up reverting all changes
Solved
IIS 7.5 (and others) needs to have the ASP.NET server extensions installed, and this will fix the problem. To get you started: you can add these by either going to Turn Windows Features On or Off from the Start Menu of Windows 7, or by using the Microsoft Web Platform Installer from within IIS (if you've downloaded IIS separately).
The solution was in the developer docs located elsewhere on the DNN site, found here: http://www.dnnsoftware.com/wiki/page/development-environment .
I ran into similar issues and thought I would share my solution for others that may need it. It turned out that turning on IIS Management Service solved my issue. To enable this feature go to turn windows features on or off as mentioned above. Select Internet Information Services -> Web Management Tools & check IIS Management Service.

Opening Visual Studio Solution from Server Explorer

I don't know if this is possible, but I am trying to open a Visual Studio 2010 solution that is on a remote server from in Visual Studio. The project I am on is using Kentico CMS and we would like to be able to sync changes made to the hosted site (on the server) using TFS and Visual Studio as well as changes made via the Kentico CMS Desk portal. I haven't found anything on the Visual Studio or Kentico dev site or in the documentation. Whether or not this is possible, or if there is a better way of achieving this goal, I would appreciate any insight you could give.
I believe this system would help you accomplish syncing your development environment to a remote server.
http://www.kentico.com/Product/All-Features/Other-Modules/Staging-and-synchronization
You can check out what gets synced on this page:
http://devnet.kentico.com/docs/devguide/index.html
The content staging is good for synchronizing changes made via the user interface.
For synchronizing changes in the file system (e.g. changes in the code files in Visual studio), you can use some third party tools to keep the folders up to date - i.e. Drop box or Google drive (but there are also other tools and utilities).
After talking with a couple developers who were a bit more familiar with Kentico, we eventually found a good solution to our problem. It's not perfect, but it will work for our purposes.
We had the Kentico administrator generate a new license code for Kentico for 'localhost'.
In Visual Studio, we pulled down one of the default Kentico projects from the server.
On the project properties, we set Use Dynamic Ports to false and chose a number to set the ports to.
Once the project was built and running, we could navigate to 'localhost:1501/[ProjectName]/[PageName (CMSDesk, Landing.aspx, etc.)]' to access the CMS Desk portal.
In the CMS Site Manager, navigate to Sites > (click the Edit button for the site) > Domain Aliases > New Domain Alias and set a new domain alias (the website you want to use when viewing the site (for us it was dev.[projectname].com). This allows other developers to log onto and use the pages via the domain alias when the project is on the server. Changes made on the localhost copy must be pushed to the server before they are visible.
Using the local copy, we could work with the web parts and sync changes to TFS. We still have to manually copy the project from our local machine to the server in order to deploy, but we are hoping to set up a build machine that will push the TFS build to the server on a regular basis, which shouldn't be especially difficult.
If we find any better way to achieve this goal, or find any potential problems, I will be sure to update.

"unable to start debugging on the web server" MSVSMON.EXE failed to start. VS2010 error

having a real problem getting VS2010 to debug IIS.
I've searched on the internet for a few days now and tried every single solution I can. VS2008 works perfectly but I've installed VS2010 and when trying to debug an IIS site (by pressing F5 on a project that uses IIS) I get the error message
"unable to start debugging on the web server. Microsoft Visual Studio Debugging Monitor (MSVSMON.EXE) failed to start. If this problem persists, please repair your Visual installation via "add or remove programs" in the control panel."
when i try attaching the process manually, i get the same message.
I've tried repairing the software. I tried it, it failed, so I uninstalled using the Microsoft Visual Studio 2010 Uninstall Utility (http://archive.msdn.microsoft.com/vs2010uninstall/Release/ProjectReleases.aspx?ReleaseId=4321), then reinstalled and it still has the same problem. With the SP1 update this still happens. I can run the website fine when running "start without debugging" and it runs fine.
I've gone through all the guides I can and all tried all the settings on IIS I can and still no luck. I'm using Windows 7 64bit if that means anything. I can detail much more about all the things i've tried.
also have a laptop and have done the same, installing VS2010 and TFS (also on win7 64bit), and this works perfectly for debugging. Didn't have to mess around at all. I can't see any difference between this and my PC with the problem. I'm scratching my head here and thinking I might have to format my PC and try again from a fresh install (which would be seriously annoying!)
Thanks to anyone that reads this,
Dan Gent
I had a HOSTS file entry resolving the project URL to a DEV server instead of local machine. Changing the entry to point to 127.0.0.1 fixed the problem.
Are you installing from a purchased disc or did you download it? Either way, you need to download a fresh copy and install that (sounds like original is corrupted).
Also, make sure you have all the IIS & Web components installed on your machine. Is your OS home or basic?
http://technet.microsoft.com/en-us/library/cc731911.aspx
i've fixed it now. ended up formatting machine, reinstalling windows 7, and then taking backups everytime i installed a new program so i could roll back. installed VS2010 first, F5 worked. then installed VS2008 & everything else and debugging still works on VS2010. not sure what happened as the above problem happened on a fresh install. something must have corrupted something somewhere
thanks for all your help and narrowing this problem down to something that was worth formatting my PC to fix.
cheers,
Buswell
This can also be caused if you are using a host name in IIS and make a mistake in your hosts file.
Check that the hosts ip is set to the local machine 127.0.0.1 and not somewhere else. In my case I had accidentally set it to the development server.
Have you tried starting MSVSMON manually? I had the same problem you are and found the service was stopped. So I tried enabling the service and made sure that it was using the correct credentials.
I hope this helps!
Thanks!
Don
The only thing that worked for me after I tried practically every solution on the Web is to right-click the project on the solution explorer, and select Debug->Debug as Administrator.
Right click on Project, "Use Custom web server" checkbox will be selected, select check box "Use local IIS web server".
I resolved this issue with this and its working.
Managed to resolve this error by At solution explorer-> right click the project->select Debug->Start new instance.
I think it was because i had copied the project folder from another server.

How do I use ASP.NET with Visual Studio 2008

I haven't used Visual Studio since VB 3 and am trying to give it a shot with ASP.NET. It seems that it should be able to connect to a website (via some sort of ftp like protocol I figure) and allow to edit without having to manually upload/download the files. Is this the way it is supposed to work or am I mis-understanding? I have tried using 'create new website' and 'open website' using my testing domain (hosted by godaddy, wondering if that may be the issue as well), each time it gives me errors. I'm not sure if I'm doing something wrong or trying to do something it wasn't meant to.
You really don't want to be working directly on a live web site, do you? That's just crazy. One little mistake and you've hosed the site.
Visual Studio now has it's own built in web server. You use that for testing. If you really don't want to use that you can put IIS on your local machine or set up a Dev/QA server somewhere. In that case, you'd edit it via a file share.
You should be using some kind of source control. Even for a single developer it's very important. When finished with a programming session, you check your updates back into source control.
Finally, only after the site's gone through a suitable QA process, the production server is updated from source control, not from within visual studio.
I would develop your website locally and ftp it to your godaddy website after or use the publish website feature in VS

Resources