Connection error when connecting to my mac from visual studio - c#

For me all I do is open Visual Studio, click on connect to Mac, and then I get this error message:
The Broker initialization exceeded the timeout of 60000 millisecs
without receiving confirmation from the Broker.
I have tried restarting my Mac and PC and creating a new project. I have the latest versions of VS installed on both my Mac and PC. This issue is really annoying so any help would be much appreciated.

Related

network connection error running CE emulator in VS2008

I have read through the previous answers on this topic as well as other coverage online. But I still can't get this working. I have not worked with CE/hardware code before.
I am working with legacy code for a barcode scanner in VS 2008 and deploying the application as "USA Windows Mobile 5.0 PocketPC R2 Emulator."
Initially we were getting an error that the emulator could not connect to the rest server that I was running on my machine. After researching that, I decided to host the rest server on a different machine to avoid the issue. Calls to the rest server work fine using Postman.
ERROR:
Now when I attempt to run this solution, the rest calls return the error "Could not establish connection to network."
ATTEMPTED FIXES:
I can't get a network connection to work by playing with the settings under:
File -> Configure -> then select Network tab on the Emulator Properties dialog.
Selecting the "Enable NE2000 PCMCIA network adapter and bind to:" does not work:
Every option under this results in an error that "The required Virtual Machine Network Driver could not be found. Make sure that Virtual PC 2007 is installed. You can install ..."
But of course, I cannot install because Microsoft has stopped supporting this stuff at all.
I tried selecting the "Host-only networking" option.
I tried using Tools -> Device Emulator Manager in Visual Studio and setting the emulator to "Cradle"
set up conn with my ip and dns
Why does Microsoft still hate developers?? :(

Android emulator starts but app doesn't show up

I'm new to Xamarin, I created a blank app just to try it out
I have Windows Home so I can only have Android Studio's emulator. The emulator works fine when I either launch it from avd manager or visual studio, but from the latter my project just won't load.
From xamarin broker logs I get this error :
System.Net.Mqtt.Sdk.ServerPacketListener: Error: 0: Server - An error occurred while listening and dispatching packets
System.Net.Mqtt.MqttException: The keep alive tolerance of 00:00:45 seconds has been exceeded and no packet has been received from client
[[ From the avd manager when I launch the emulator I get this error "Telnet connection failed", idk what this means bc I can still access the internet through the emulator ]] EDIT : I activated telnet so i dont get this anymore, still not working tho
I tried to reinstall everything (sdk + vs)
I found several solutions which involve launching the emulator from the avd manager then deploy the solution from vs, but that seems to be possible only with visual studio emulator
I tried this App not run in visual studio emulator for android in visual studio 2015 but it uses a visual studio emulator which i can't have (it needs windows pro or enterprise for hyperV)
Thanks for your help

Cannot deploy UWP app to raspberry pi 3

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.

Unable to connect Xamarin MacAgent from VS 2017?

I am working on a Xamarin Project. I am trying to connect Xamarin MacAgent from my Windows - VS 2017 Community Edition to Macbook to test the iPhone Simulator. However, I am not able to connect.
I am connecting from Windows to Macbook using usb-ethernet cable. In the MacBook, System Preferences - I have set the Sharing option - Remote Login - All Users.
My MacBook has Xamarin Studio, XCode Installed on it.
I tested the connection from Windows - Commmand Prompt by pinging the MacBook IP Address, I get response. I have turned off firewall on both Macbook and Windows.
In Windows, I have cleaned up the files in the folder : Local\Xamarin\MonoTouch
In MacBook, I have cleaned the cache.
However, i am still getting the error as " Couln't connect to MyMacbook"
How do i fix this ??

Failed to deploy WP 8.1 application to the mobile device

I am using MS Visual Studio 2013 Professional Edition with Update 3. When I try to deply a WP 8.1 to the mobile device, I am facing the following errors.
Error: DEP3100: Attempts to stop the application on target machine "127.0.0.1" failed.
This may cause the deployment to fail.
The network connection to the Visual Studio Remote Debugger has been closed.
Error DEP2300: The deployment tool (TailoredDeploy.exe) failed to run on the target machine "127.0.0.1".
The object invoked has disconnected from its clients.
I have earlier deployed application to this mobile device.
Why am I facing such an error now?
I manually uninstalled the app. And when I tried to re-install the app, the same error occurred. But the solution was more simpler than I thought. I restarted the phone after switching it off. Voila. Worked. I installed the app once again. Successfully debugged the application & was able to deploy it to the device.
PS: But still I don't know why this error occurred.

Categories

Resources