After using Notepad++ to develop a website for a while now, I decided to try a more advanced IDE and installed Visual Studio.
In NPP I used the NppFTP plugin to work on my webserver and never had problems doing so. But when I try to acces my code with Visual Studio, weird things happen.
So I click on "Open Website" on the Start Page.
There I select FTP.
When I fill in the same server, port and login data, which still works in Npp, I get an error saying "Rebex FTP/SSL does not support SFTP/SSH protocol.
When I write sftp://aiatlas055.cern.ch instead of aiatlas055.cern.ch, Visual Studio displays an empty dark blue page and starts lagging and being unresponsive.
Can anybody tell my what is the proper way to connect to my webserver ?
Related
I am making a command line application in C++ for WinPE, which I am booting from my flash drive. I made a C++ console application in Visual Studio (2019), and I put the app on another partition of the flash drive. I tried to run the application in WinPE, but it said that the application was not compatible with WinPE. I tried deciphering this page by Microsoft (I couldn't find anything on other sites), and I tried some of the things it says, but it just wasn't working. I don't think I fully understand some of the things on that page, but maybe you do.
Visual Studio 2017 - 15.8.4 (but happens on previous versions), Windows 7, IIS Express 64. Chrome 64 (Latest when posting).
When I launch Chrome for debugging from within Visual Studio, debugging works fine until I hit "Choose File" to browse a file for upload and selecting a file (not uploading it, just selecting it). Visual Studio debugger will immediately stop without giving any reason.
When using IE's "Browse..." button and selecting a file, which is the equivalent of the same Chrome HTML element, everything is working as expected.
My hunch is that Chrome is trying to do an extra socket connection which is upsetting IIS Express and triggering VS to stop debugging.
Do you know any solution to keep debug running as expected, on Chrome?
I just stumbled over the same error and for me, it was because I have AVG antivirus installed, and because it starts the debugging in an AVG Secured Chrome instance. I just changed it to normal Chrome, and it stopped exiting debug-mode. Hope it helps!
I have been using Visual Studio for ages, version after version. Lately I installed VS.2017 but every time I try to install a tool or extension things go wrong. I am using a restricted (non-admin) account as I always have.
Select Tools in the menu bar at the top
Select Extensions and Updates in the drop down menu
Try to select any from the list
When I do that I get a very informative dialog that only says "Access Denied" and nothing else. As a result I cannot install any extensions. In some cases after doing that then I cannot start VS anymore without getting "Unknown Error" which luckily I got rid of thanks to another post in SO.
Why is this happening in the new VS 2017? I never had any problem installing extensions or updates while running a Restricted User Account.
I recently downloaded Visual Studio 2015 from DreamSpark. I downloaded the iso file and ran it, starting the installation. From there, it just basically installed itself. Afterward, the program didn't launch because I had to restart my computer. Upon starting Windows back up, there was no icon on the desktop, there was no shortcut in my tool bar at the bottom of the screen.
Perplexed as to why this wasn't part of the installation, I checked the folder I installed it to, which was the one that it defaulted to. Navigated to C://ProgramFiles(x86)/Microsoft Visual Studio 14.0/Common7/IDE. From there I searched through the executable files and found nothing that looked like a way to open the browser. All I can find are some peripheral features like the Web functionality, the Graphical interface, but nothing to get to the C++ coding interface. Any suggestions? Am I looking in the wrong folder or something?
I read a post about Visual Studio 2012 being able to support Windbg commands in the immediate window. This requires that one chooses the "Windows User Mode Debugger" option while choosing the Transport under "Attach to Process" option.
While this seems to work for the local host qualifier, I am interested in knowing if i can debug a remote target process using this method just like we do by selecting the remote transport.
I am using Visual Studio 2012 Premium.
I tried giving the IP of the machine in the qualifier section with the "Windows User Mode Debugger" transport selected but i got the "Could not connect to the machine" message.
I also tried the steps mentioned in this link:
http://msdn.microsoft.com/en-us/library/windows/hardware/hh439381(v=vs.85).aspx
but it did not work.
Also , i'm not sure if this article is meant for a different version of Visual Studio since the button that i see next to the Qualifier field is named "Find..." rather than "Browse" as the article mentions.
Can someone please help me with the right steps here?
Have you run dbgsrv.exe in the remote target machine.
Step#1:
Install Windows SDK in the remote target machine
Step#2:
Run command:
cd C:\Program Files (x86)\Windows Kits\8.1\Debuggers\x86
dbgsrv.exe -t tcp:port=12346
Step#3:
As you said, refer to:
http://msdn.microsoft.com/en-us/library/windows/hardware/hh439381(v=vs.85).aspx
This doesn't seem to be documented and I struggled with this myself a year or so back, but the WinDbg integration is Visual Studio is for what's called the smart client way of debugging. You need to run dbgsrv.exe on the server and then you'll be able to connect.
See more information about dbgsrv.exe etc. here: Process Servers (User Mode) and especially here: Activating a Process Server.
I wasted hours on this.