I try to install remote debugger in my remote machine, and connect to it in my local computer, using visual studio 2012 for asp.net web application, windows8.
remote and local computers are not in the same network.
I installed the visual studio remote debugger in the remote machine and run it. it's instance name is:"SERVER-PC:4016"
In the local machine, I work on the project by ftp and in debug-attach to processor in qualifier field I enter the name in this format: external_ip:4016, and get an error:"The Microsoft Visual Studio Remote Debugging Monitor (MSVSMON.EXE) does not appear to be running on the remote computer.."
p.s. I installed a local user in remote and local machine with the same name and password and run the relevant programs from this user name.
any ideas to solve my problem?
thank you!
Related
We have some released ASP.NET project and now we are supporting it. I installed Windows 8.1 on my macMini and cloned that project. The webSite works on server normally and locally on machines of other developers. IIS configured as well. When i trying to browse webSite from IIS manager I have the following problem in chrome:
This webpage is not available
ERR_NAME_NOT_RESOLVED
When i try to debug via Visual Studio by pressing the debug button i have this:
Unable to start debugging on the web server. The debugger cannot
connect to the remote computer. The debugger was unable to resolve the
specified computer name.
But i think it's ok, cause we are debugging this project pressing Ctrl+Alt+P and attaching to w3wp.exe process, but it's not launched. Actually this should be launched automatically, as i know.
Windows 8.1; MSVS 2015; .NET 4.5.1;
I tried to restart IIS. And i configured binding to my website with host name myWebsiteName and port 80.
Update 11.6.2015 :
And one more thing! The default web site works fine.
Are you running as Administrator? Also try these commands:
ipconfig /flushdns
ipconfig /renew
ipconfig /registerdns
from the command-line (running as Administrator)
I'm trying to debug an ASP.NET application for my company internal portal on a remote IIS v7 server running on a Win 2008R2 server. The IIS server is on the same LAN as my development workstation.
The portal mostly works, however there is one function that doesn't work correctly when published to the remote server.
If I debug the application locally, using either the Visual Studio Development server or the local IISExpress server, the function works as expected, so it seems that I need to debug from the remote IIS server.
I have installed the Visual Studio 2010 Remote Debugger (msvsmon.exe, x64) on the remote server and have published my web app there. I'm running msvsmon on the remote server as an administrator.
On my local Win7 development machine, I have the portal solution open in VS 2010 from my local hard drive, I can connect to the Remote Debugger from Visual Studio using the Tools | Attach to Process menu and I have selected the w3wp.exe at the process to attach. The msvsmon app on the remote server shows that I have connected.
Back in Visual Studio on my local machine, I set a breakpoint on a Page_Load method (where I suspect my problem code is), however, my debug options to Start, Continue, Step Into, Step Over, etc are all disabled.
I'm apparently missing some step or concept here, but I'm at a loss as to what it is.
My question is: why does a dev site work when the project is run in Visual Studio 2010, but not when served from IIS on the same PC?
I am trying to set up a dev copy of a client's site. On startup, the site makes a connection to a remote database server. The connection uses WCF and a SSL certificate to secure it. When I installed the site on my PC, following instructions, I installed a Cert Chain into the "Trusted Root Certification Authorities" and added registry keys and host entries to resolve connections to the remote service.
When I open the solution in Visual Studio 2010 on my PC and run it in the built-in ASP.NET dev server, it works -- my workstation connects to the remote service via SSL on a custom port (444) and the dev site queries for data successfully from the service. All of this is handled by a DLL provided with the project, and is outside my scope of work. I was briefed up front that the connection was very finicky about the SSL cert, system clock time agreement between the two machines, etc. and it took me a few tries to get it to work.
However, when I run the site in my local IIS (Windows 7, IIS 7.5) the site cannot connect to the remote service; the service won't accept the SSL connection. The startup code throws an exception when this happens, preventing the site from loading further.
Everything else seems to work fine: the only wrinkle is that VS requires a 32-bit version of the secure connection DLL while IIS on Windows 7 requires a 64-bit version. Both were provided to me and I swap them as required.
Per the comment, the answer is: check that the Cert Chain (to trust the SSL certificate used by the WCF connection) is installed to Local Machine (so that IIS sees it), not just to Current User (account used by Visual Studio).
I have local my projects asp.net open in visual studio 2010. And also copy this project to IIS folder in remote hosting. Cause in hosting directory I don't have VS so I copy there remote debugger application. I connect from my Visual Studio to IIS process on hosting, but any of breakpoints not fire.
Why ?
I had the same issue when I connected using the Transport in the "Attach to Process" dialog set to "Remote (native only with no authentication)". I was able to connect to the IIS process (w3wp.exe for IIS6 on Win2K3), but no breakpoints were hit when I navigated within the web app.
To get it working, I changed the Transport to "Default". Then I ran into numerous issues with successfully connecting to the Visual Studio Remote Debugging Monitor. But once I resolved them all and was able to get the list of processes from the remote machine, I could connect to W3WP.exe and voila, my breakpoints started working and I was able to debug normally.
You don't provide much detail on your local and remote configuration, so this just a guess whether it might help.
My asp.net web app is hosted on this URL on my local machine:
http://localhost:45433/
I want to access the same application from a different computer on the network. I tried replacing the localhost with my IP but it did not work.
any ideas!
UPDATE 1:
Now, I am getting this error:
Login failed for user ''. The user is not associated with a trusted SQL Server connection.
If your application is hosted using Visual Studio's built in web development server then this server does not allow remote connections. It is for testing purposes only and accepts connections only from localhost. In order to access your application from remote clients you might need to deploy it to IIS.
First, add the application as a virtual in IIS, and as long as you can access the machine on the network, you can do:
http://<machine name>/<virtual>
I do that at work, where I can access my co-worker's web site.
HTH.
That looks a lot like a url used by the development web server in visual studio. That web server only responds to requests from the localhost. It won't work for other requests from other machines on your network.
You need to install IIS on your machine (must be a Pro version of Windows) and deploy to that IIS install to share your app on the network.
I don't think the built-in version of Cassini (VS debug server) allows remote connections.
However, the UltiDev version, built off of the same code base with a few enhancements, does, and is a much lighter-weight install than IIS (especially if you can't find your OS install DVD). It also integrates nicely with Visual Studio for debugging purposes.