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!
Related
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 ?
Unable to sign into TFS online using visual studio professional 2017 v15.2 (26430.14) - Visual Studio locks up few seconds after login dialog appears...
Seems sign-in dlg is displayed as VS attempts to connect to TFS online; but no matter what you do you get locked up 3 secs later.. No matter what... end result is me killing the process and left unable to access any project.
THE ONLY WAY OUT I did figure out that if you cancel(esc key) the dlg closes before it hangs. you can THEN connect to TFS via team/menus. life saver.
does anyone know why this happens or how to correct..? seems intermittent but sometimes lasts for days.. meaning, I have to do this on every startup; but then magically the problem goes away. An associate of mine also sees this problem.
It looks like this issue is resolved with the latest VS2017 update (15.0.26430.16).
I'm not sure what version you are running, but try updating as it worked for me.
I'm trying to build and run a simple project in Visual Studio 2017 (C++) in x64 using the Local Windows Debugger. However every time I try to run it using the debugger I get this error.
This error doesn't show up when I change it from x64 to x86, but I need it to compile to x64. This has happened on both computers that I've tried it on, and seems to happen in every one of my projects. I've tried reinstalling Visual Studio already and nothing's changed. I've tried adding 'devenv.exe' as an exception to the Windows Firewall but no changes there either, even when I disabled the firewall completely. My antivirus isn't affecting it at all either: still happens when I disable it.
The application runs fine when I find it in the explorer and run it manually but then I don't have any debugging tools.
What am I doing wrong here, how do I make it build and run my project as x64?
I get this error every time I have an active VPN connection. If you use a VPN, try disconnect and see if the error disappears.
If you want to use a VPN, the solution (assuming you have Visual Studio 2017 Version 15.7 or later) is as follows:
Go to the Windows Start Menu and launch the “Developer Command Prompt for VS 2017 Preview”
Run: "%DevEnvDir%vsregedit.exe" set "%VSINSTALLDIR:~0,-1%" HKCU Debugger UseAnonymousPipes dword 1
Restart VS if it is already running
That solution is from this link to Microsoft.
I have created a multi device hybrid project in Visual Studio 2013.
I am having a few major issues:
1) Changes to my scripts do not appear unless I completely rebuild the application when I am using Ripple to view the project.
2) Pressing F12 in the Chrome ripple window causes Visual Studio to stop running the application. This seems very strange. It's like if I were to quit debugging on a normal webapp.
Output shows The program '[1] http://localhost:4400/index.html?enableripple=cordova-3.0.0-NexusGalaxy: WebKit' has exited with code -1 (0xffffffff).
Has anyone had these problems or know what might be causing them?
Both of the behaviors you describe are expected. Ripple is not automatically refreshed when you save your changes so you will need to rebuild and deploy for it to pick up the updates. Since only one process can use the webkit debugging at once, the VS debugging session gets disconnected when you use the debugging tools in Chrome.
So, I'm kinda new into this VS world. I'm using VS 2012 and it was everything working correctly last time. Now I try to open my projects and none of them actually loads. When I go to the solution explorer I just see the message "Load failed" followed by the message: "The project requires user input. Reload for more information." But when I reload, it pops up a message "The operation could not be completed. There is no support for this interface."
I don't know what it means by "requires user input", i never opened my project with any input, I just click on the project's file and open it...
Anyway, what is going on??
Thanks.
I got the same message (using VS 2013) opening a project located on a network drive.
I Right clicked the project in Solution Explorer and selected 'Reload Project', a dialog appeared warning me about an untrusted location, I clicked OK and the project loaded successfully.
Change the folder name of your project. Then VS asks again if it is trustable. than click YES. after that VS reloads the project
I had to "repair" Visual Studio Express 2012 on my Windows 10.0 Laptop. You get the repair option if you already have Visual Studio installed.
This fixed my issue which was exactly like above.
I removed the ComponentModelCache folder and restarted Visual Studio 2012.
This solved the issue for me.
C:\Users\username\AppData\Local\Microsoft\VisualStudio\11.0\ComponentModelCache
This worked for me as well. I removed the contents of the folder, ComponentModelCache, then I restarted 2012 and the projects loaded without issue.