I am using a MacInCloud provider for the Mac and I am trying for my Appium to connect to it.
I have entered the remote host xxx.xx.xxx.xx. the remote port xxxxx and the remote path https://foo.macincloud.com/rdpdirect.html?server=bar but for this to work I would need to enter username and password then open the simulator or if that's enough access the real IOS device connected to my pc where the Appium is installed and Visual Studio that is paired to the MAC.
It looks like I would need to use a higher account and pay for that to be able to use Mac in cloud.
I'm getting an error :
Error: Unable to connect to the Microsoft Visual Studio Remote Debugger named 'minwinpc'. The Visual Studio 2017 Remote Debugger (MSVSMON.EXE) does not appear to be running on the remote computer. This may be because a firewall is preventing communication to the remote computer. Please see Help for assistance on configuring remote debugging.
I'm trying to deploy an app to my RPI 3 running Windows 10 IoT Core v.10.0.16299.15.
I've tried:
Reinstalling Visual Studio 2017
Installing Visual Studio 2017 Remote Debugger.
Restarting the VS.
I noticed that Visual Studio 2015 remoter debugger is running on raspberry pi and it has 192.168.0.6:8116 as a remote machine name while in VS2017, rpi's address is 192.168.0.6:4002. Why are they different? Can someone help me?
As Martin & Belekz mentioned,you can check the configuration of target device and firewall setting.And more,I want to add that,please note the configuration of Authentication Mode.You should set it as "Universal(Unencrypted Protocol)".Use the mode whenever you are deploying to a remote device. Currently, this is for IoT devices, Xbox devices, and HoloLens devices, as well as Creators Update or newer PCs.
Look at my post here i have the same problem and i tried several things, but only after i done this i can deploy remotely to pi again:
Uninstall old 16299 SDK and download new 16299 SDK from here
Repair VS from VSInstaller
run sfc /scannow
Also make sure you're using Universal authentication mode and type the ip without port number (or even using 'minwinpc' is enough)
hope this helps
I never deployed software from VS to a RPi using an port in the IP address before. So maybe you are doing something special, or I'm doing something basic, but;
dubble check if you need to assign a port.
Start Windows 10 IoT Core Dashboard and check if the Pi is visible
in your network.
--> If not, try to ping to your Pi, using the CMD
ping 192.168.0.6
--> If the ping fails, check your IP address of your Pi with a physical
monitor.
Check the address in the build properties according to the steps above.
Hope this helps!
You can configure the remote debugger's IP address and port to point to the correct endpoint of your Remote debugger.
Right-click the UWP app project, choose Properties, and in Debug tab you will see Start options with Target device which should be set to Remote Machine and below you can manually enter the Remote debugger's IP address and port into the Remote Machine field (192.168.0.6:8116 in your case). You should include the 8116 port in the Remote Machine field as well.
This should make Visual Studio connect to the Remote debugger instead of the RPI itself.
Also try to turn off the firewall to verify if it does not interfere with the connection.
i have see same problem in my laptop. i solve this problem by following steps..
first of all can you install Windows 10 IOT SDK in your .net?
if no then first of all download and install.
otherwise update vs 2017.
when install vs 2017 then automatically install iot sdk.
I am running my TCPIP remoting server application (.net version 4.5.1, VS 2013) in windows 10 but I got one server side crash given below, infact it’s perfectly working in windows 7
We have checked port details by "netstat" command and found that the server side port(9092 is my server port) is in listening state, even though we got following error
Error : System.Net.Sockets.SocketException (0x80004005): No connection could be made because the target machine actively refused it 127.0.0.1:9092
I hope the issue will come when the client try to register on the server listening port.
Is there any change in TCPIP connection/security settings in Windows 10 ?
I tried this tutorial for .NET TopShelf: http://lourenco.co.za/blog/2013/08/wcf-windows-service-using-topshelf-and-servicemodelex/ and everything works fine on localhost, but when I run Client app on other PC with host IP in app.config aplication return an exception in Program.cs in Client app in line:
var response = proxy.Service.Introduce(request);
The error message says: "tcp error code 10061 no connection could be made because the target machine actively refused it"
I've got windows firewall off. What can I do to connect two computers in LAN network using TopShelf?
I am developing an app for Windows CE with Visual Studio 2008.
If I connect the device via USB I can debug / deploy my app on the device.
But on the CE device the USB connection is just presented as another network interface with a private IP.
Now I am wondering If it is possible to dismiss the USB connnection an connect over the LAN (both my PC and the CE device are on the same subnet).
Yes it is possible, I do this at work. First you need to run IPConfig on the device and get the IP. Setup the IP in visual studio's connection properties. Next there are two executables and some files you need to copy to the device.. here this should explain
How to: Connect to Windows CE Device Without ActiveSync
Just execute those two exe's and you should be able to connect. BTW, debugging over ethernet is much faster and less buggy than activesync