Went to Tools --> Options --> Tools for Apache Cordova --> iOS Configuration in Visual Studio on my Windows machine.
On my Mac Machine I ran remotebuild certificates generate and got back:
Enable remote iOS processing: True
Host: hostname
Port: 3000
Secure mode: True
Security PIN: 000000
(I replaced host and pin such that this question may be useful to others in the future).
In Visual Studio on my Windows machine I filled in my hostname, secure mode, pin, etc according to the remotebuild certificates above. I have also tried replacing hostname with my mac IP address.
I am getting the message The host hostname could not be resolved. However, when I go to my Mac machine and do localhost:3000 I get a page saying
Remote build Express server open for business on port 3000
and on my terminal, the server responds with GET / 304 2.185 ms - -, so I know the server is active. What is the solution to fixing this on the Visual Studio side?
I found the solution : turns out my computers were on two different WiFi networks..
Related
I recently had to reinstall my solution in Visual Studio for Mac. When I clicked run for the first time it asked for my system password to trust an SSL certificate. I clicked yes. Now the solution runs on localhost port 5001 instead of 5000 and is using https instead of http. I am now getting mixed content errors on my HttpRequests. How do I change it back to http and port 5000. This is Visual Studio Mac Community 8.6.5.
Ok so I just removed the reference to https://localhost:5001 in the ASP.Net Core run configuration found in Project Options and it was back to normal.
I have a fairly large web application developed in Visual Studio 2013, working perfectly on my local IIS. I have deployed to my remote server (Windows Server 2012) and have the usual problems with adapting to remote vs. local. My main issue is I cannot remote debug out of VS2013. The message I get is this:
Error Message from VS2013
What I have tried so far:
As per Firewall ports needed for Visual Studio 2013 Remote Debugging I have opened both TCP 4018 and 4019. First inbound, then also outbound.
Since that did not work I also opened DCOM (TCP 135) and UDP 4500 and 500. I did not create a new DCOM rule, only enabled the existing ones.
A few things to note:
1. The correct version of Remote Debugging Tools for VS2013 is installed
2. The Debugger is running and waiting for a new connection (run as admin)
3. My local machine and the remote server are both on the same VPN using LogMeIn Hamachi
4. I can see the machine when I try to attach process in the VS2013 debug configuration, it just won't allow me to connect.
I am out of ideas here. Any help is appreciated.
See the required ports for remote debugging here:
https://msdn.microsoft.com/library/ee126350(v=vs.100).aspx
[TCP] 135, 139, 445 - Required
[UDP] 137, 138 - Required
[UDP] 500, 4500 - Required if your domain policy requires network communication to be performed through IPSec.
[TCP] 80 - Required for Web Server debugging.
hope this helps ;)
In Visual Studio 2015 RC, When trying to remote connect to another machine for remote diagnostics ( or to deploy an app to a Raspberry Pi ), Whilst searching for Remote connections it fails and returns with "Found 0 Connections on my subnet" even though there are 2 devices currently visible to the IoT Core Watcher.
If we ignore this and set the IP of the machine and build -> Deploy, It will fail and bring an error up of
Error : DEP2100 : Cannot copy the file "FILENAME" to the target machine "IP / Name".
Attached is a screenshot of our problems.
Visual Studio Failing to find devices and IoT Core found 2
Reason for the error: Ethernet was connected to Router not Host PC.
Connecting to Host PC and enabling network sharing works.
The search is not currently working.
Deploying an application by manually providing the IP address is working though. I reviewed the screen shot that you attached. I don't understand why you have entered an address of 169.168.137.79 when the device is at 192.168.137.79. Is this a typo? Everything else looks ok.
Mark Radbourne (MSFT)
I'm trying to set up remote debugging across domains. My Windows 7 workstation running Visual Studio 2010 is on one domain and I'm trying to debug an ASP.NET app running in IIS 7 on a Widows 2003 server box in another domain. I have found many instructions on how to set this up, this being the best, most clearly written one: http://blogs.interknowlogy.com/2011/11/16/remote-debugging-from-visual-studio-2010/
However, I can only seem to connect to the remote debugging monitor on the server if Visual Studio is being run as the local user on my workstation, not as the domain user. This creates a number of challenges, such as loss of source control connectivity. When I try to connect using the domain user I get the following error: "Unable to connect to the Microsoft Visaul Studio Remote Debugging Monitor named 'username#servername'. The specified account does not exist." (I have substituted a generic username#servername for the actual values)
I have found a number of sources suggesting this will work with the domain user running VS2010 but have had no luck. Any idea what I might be missing?
Solved
First, i've read #KyleMit's answer on the same question and done all steps.
But, for across domain debugging also need to edit C:\Windows\System32\drivers\etc\hosts file on local computer.
Just add remote computer's ip address like this:
172.172.172.172 SRV-TEST-ADRESS
Where:
172.172.172.172 - ip address of your remote server
SRV-TEST-ADRESS - Server's name from Visual Studio Remote Debugger
Monitor on remote computer
You can know your server's ip address by ipconfig in cmd
After that, i could attach to proccess on remote computer across domain.
I have a test machine that runs Windows 7 Enterprise x64. I setup MSVSMon (tried both 64 and 32 bit versions) on it and made sure that the Firewall settings would not block the remote debugger. Now I'm trying to connect to this from my dev box running Windows 2008 R2 and Visual Studio 2010. However when I try to connect to the remote debugger, it shows me the following error message:
"Unable to connect to the Microsoft Visual Studio Remote Debugging Monitor named "xxxxx". THere is no server by the specified name running on the remote computer.
Some obvious things:
- I have verified that the name I'm using is correct (picked it up from teh MSMSMon.exe options dialog)
- The dev box does have access to the remote machine, I can check that by connecting to it's file shares.
- The same instance of visual studio is able to connect just fine to another similar test machine, but one running a 32 bit Windows 7 Enterprise.
Any ideas?
Vin
Make sure if you are debugging from VS2010,its the debugger for 2010 and not 2008, and/or vice versa
I would check your firewall is not blocking the connection. Just because you can connect to the fileshare doesn't mean it's allowing the DCOM connection to the Remote Debugger.
See http://msdn.microsoft.com/en-us/library/bt727f1t(v=VS.100).aspx
I generally run MSVSMon on the remote machine from a share on my dev machine where I have several versions of Visual Studio installed. I get "There is no server by the specified name running on the remote computer" error when I run the wrong version of MSVSMon. For example if the VS2008 version of MSVMon is running on the remote machine and I am trying to attach to the process from VS2010.
Default location of MSVMon for VS2008 :
C:\Program Files\Microsoft Visual Studio 9.0\Common7\IDE\Remote Debugger
Default location of MSVMon for VS2010 :
C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\Remote Debugger
I've found alot of ppl bump into this scenario. Tried to cup the solution in my blog post:
http://livshitz.wordpress.com/2013/02/26/remote-debugging-visual-studio-unable-to-connect-to-the-microsoft-visual-studio-remote-debugging-monitor/#more-144
Here is the snippet of the solution:
Make sure firewall is not blocking your request
Make sure the installed version of Visual Studio Remote Debugging Monitor is supported by the running Visual Sutdio
Create local user on remote target, with the exact user name and password as the debugging user (that runs VS process)
If dns resolving is unavailable (source and target on different domains) open this file
"c:\Windows\system32\drivers\etc\hosts"
and add a new line at the bottom:
"xxx.xxx.xxx.xxx TargetHostName" (without quotes)
This will map the target host name with an IP.