How do I manage pairing Visual Studio to multiple Mac's? - xamarin

I work from home and for my job I am using Visual Studio 2022 on Windows paired to a MacinCloud running Big Sur using my company's Apple Developer account for Xamarin development.
In the evenings, I'm playing with MAUI so I'm running the Visual Studio 2022 "Preview" version and I have my own Apple Developer account and my own separate MacinCloud running Monterey.
When I open Visual Studio (either version) it looks like it just tries to pair to the last Mac I used and then it also tries to install updated SDK's etc. if necessary.
How do I manage this? Ideally I want to stop it from auto-pairing and then choose the correct Mac each time.
Thanks in advance,
Paul Lonsdale.

You can open Tools - Options - Xamarin - iOS Settings on Visual Studio on Windows computer. On the Pair to Mac dialog window select "Forget this connection" (right click context menu on the connection).

This isn't really an answer but a workaround. The issue only really happens when both macs are running which is rarely the case. I will, in future, make sure that only the mac I need for the project I am working on is up and running. That way even if VS tries to connect to the other one it will fail.

Related

Problem Running Visual Studio Code on Mac

When I download Visual Studio Code for my MacBook Pro (running the latest version of MacOS, 10.15.1), I get a message:
“Visual Studio Code.app” can’t be opened because Apple cannot check it for malicious software.
Is there a way around this, or is the app being updated?
This is a security mechanism from your operating system. If you trust the app, you can right klick on the file and open it from the context menu. Then you have to confirm again that you want to open it and it should work as expected.

Cannot launch Android Emulator visual studio 2019

After installing windows 10 update whenever launching an android emulator I get
Could anybody advice what do to? How do you reinstall the sdk,remove it
many thanks
Try the obvious first - restart the Visual Studio and the PC.
If that doesn't work then try selecting Tools->Android->Android Device Manager and play around from there. Try creating a new instance of a different device. Google Pixel or Nexus for example.
Try different options from there.

Deployment error in Visual Studio 2015 while running Xamarin app

I am running visual studio application on genymotion virtual machine. But it shows deployment errors while debugging. It seams it is something with the emulator. I know there are similar questions but none of them solve the problem. Anyone for help?
error occurred:
A numeric comparison was attempted on "$(_DeviceSdkVersion)" that evaluates to "" instead of a number, in condition "$(_DeviceSdkVersion) >= 21".
Solved ( genymotion users)
Go to Genymotion select the virtual device you are using.
Settings>>ADB>>Select the option "Use Custom Android SDK tools">>copy and paste the same location your sdk (like in Visual Studio >>Android Settings >>Android SDK Location
restart genymotion. It worked for me!
Solution actual for emulator, but not for devices. Solution for devices - kill all shuame_helper.exe processes, that takes TCP-port which is required to poll the device's SDK version... Shuame_helper.exe raised every time you reconnect your device to PC..
I seams the problem is with genymotion: there are different paths of SDK path in visual studio and genymotion.
Solution:
First go in Visual Studio-> Tools -> Options. In options choose Xamarin->Android settings. Copy the path in part: Android SDK Location.
Then open genymotion. Choose virtual machine that you will be using. Than settings->ADB-> use custom Android SDK tools, and paste the path there. If you get message that says Android SDK tools found successfully. Close the window and then restart Visual Studio and run your application again.
For more details look at this link
http://enblog.clock-up.jp/entry/2016/06/26/xamarin-android-device-sdk-version-error

Can't create a UWP app

I recently, upgraded to Windows 10 and got Visual Studio 2015 Community hoping to build UWP apps and ASP.Net 5 apps. At first, I installed everything, but ended up skipping / canceling the Windows 8.1 / 10 mobile emulators (my PC can't even run them). After everything was installed, I went to create a new UWP app (C#), and got this error:
Next, I try the same thing, but with JavaScript. It works perfectly! on the same UAP 10.0.0.0 that is supposedly missing. The link it provides is completely useless (it sends me to http:/microsoft.com/en-us) -_-. Oddly, this only happens when I try to use C# or VB.Net, JavaScript UWP apps seem to work fine. What is going on here? Where can I find the real link to the SDK I need?
UPDATE
JavaScript UWP apps will be create just fine, but when I attempt to build, I get:
Error "10.0.0.0" is not a supported value forTargetPlatformVersion.
Please change it on the Project Property page. Test
C:\Program Files (x86) \MSBuild\Microsoft\VisualStudio\v14.\JavaScript\Microsoft.VisualStudio.JavaScript.UAP.targets
This is the download link for the standalone SDK, maybe reinstalling the sdk will fix the problem.
https://dev.windows.com/en-us/downloads/windows-10-sdk
Normally you don't always have to reinstall visual studio when something goes wrong because it takes a lot of time to reinstall again. From your question you skipped/cancel that feature, the first thing to do is go to the control panel and double click on visual studio under programs to Modify the software and enable those features.
In the case, visual studio was working properly before but due to some updates it stopped, go to control panel right click the visual studio version you have under programs to repair.
If the above doesn't work try to reinstall it again. I hope this helps.

Windows Mobile Debugging

I am working on creating a windows mobile application and I have a quick question. I have looked around for the answer and cant find anything. Is it possible to run a windows mobile application on a physical hardware device from visual studio? I don't need to be able to debug really, I just would like to be able to select my device and have it build, copy to the device, and run. Is there anyway to set this up?
There is a "Device" toolbar that should let you choose your target device. Check for it under the View -> Toolbars menu (for VS 2008... not sure if you are on a different VS version).
If you are only showing emulators, you might need to install the windows mobile 6 sdk (I don't know for sure, but I do know I also have that installed... could be that this only includes the emulators as well).
Update:
It might also be worthing right clicking on your project in the solution explorer and selecting properties. From the properties page, go into the Device tab. It might be that some devices are listed there that are not listed in the target device drop down list on the toolbar. Worth a shot, but no promises.
It's simple believe me.
I'm currently working on Visual Studio 2008 and I have already installed Windows Mobile 6.0 SDK. It's simple just two steps.
Plug your device to your computer via usb cable then you should see the ActiveSync connected your device.
Open VS and choose from target device menu that "Windows Mobile Professional Device", then push the VS Debug button (it's slower that simulator but it's working perfectly). (look at the picture)
alt text http://img38.imageshack.us/img38/3638/screenhy.jpg
I hope this will be able help to you.
Yes. If it's like mine (Verizon Motorola Q) Visual Studio will copy several files to the device and the device will prompt you to allow them. You only have to do that part once. Then when you debug on your device you may get a prompt to allow the program you're debugging to run. It seems to copy your program over to a folder in the devices "Program Files" folder and runs it from there. And it leaves it there even after you stop debugging.
And one more thing. With Visual Studio 2005, you'll need at least the standard edition to do mobile development. With Visual Studio 2008, you'll need at least the professional edition.
Thanks for the help everyone. My solution was a mix of a couple answers. I had to switch the project to the Windows Mobile 6 Professional SDK first and then I was able to select "Windows Mobile Professional Device"

Resources