If you don't have a device to deploy to, you'll need to setup an Android emulator or use a device. If you've already done this, you can skip this step.
I have installed all the tools for development with Xamarin in Visual Studio 2015, but somehow I do not see Blank App (Native) template when I create new project. I am only able to use Blank Apps (Xamarin Forms) template. I have already tried to reinstall Xamarin, reinstall Visual Studio install all the Xamarin sdks separately, but still no. Visual Studio for Mac.NET. Azure DevOps. Azure DevOps Server (TFS) 0. System.Windows.Forms not available in Visual Studio 2019 for Mac. Visual studio for mac. Genaro Salierno reported Jul 22, 2019 at 10:54 AM. Show comments 4. On the left-hand side of the New Project window, under the Multiplatform category, click App, select Blank Forms App, ensuring that the drop-down box next to it is set to C#.
If this if your first time building a Xamarin application, you'll need to create a new Android Emulator. You'll see 'Android Emulator' in the debug menu. Click it to start the creation process.
This brings up a UAC prompt to be accepted and then the emulator creation process. The options are automatically populated for a base emulator. If required, change any options and then select Create.
At this point, you may be prompted to agree to the license agreement for the Android emulator. Read through and select Accept to continue the process. This will download the emulator images and finalize the creation of the emulator for use in Visual Studio.
Once the emulator has been created, you'll see a button that says Start. Click it.
Mac Visual Studio Blank Forms App Net Standard Not Available 2017
You may receive prompt to enable Windows Hypervisor Platform. Follow the documentation to enable this feature for optimal performance.
The Android emulator will launch. Wait for it to fully finish starting and you'll see it displayed in the Visual Studio debug menu.
Your Android emulator has now been created and is ready to use. Next time you run Visual Studio, the emulator will appear directly in the debug target window and will start when you select it. If you ran into any issues or have performance issues with the emulator, read through the full setup documentation.
Answers
@RobertoFonseca:
Just to be sure:
The iOS-simulator is loaded on the MAC (not on your windows machine).
If you want to debug to an iPhone / iPad the devices also has to be connected to the MAC.If this don't work, you - maybe - have a problem with your configuration (versions on PC don't match versions on MAC).
Yes, my device are connected on mac.
And this isn't explain the simulators don't appear. When the version don't match the visual studio simply don't connect with build host. I think. And I get a warning.I'm using parallels desktop. It could be some network config and the visual studio isn't get everything it need to work.
I will check both options, version and network, and reply.I noticed one more thing:
When I click on Show iOS simulator and the simulator are closed I get 'failed to show simulator on build server';
But if the simulator is already open, when I click it goes to front of the screen.Yes, Before run your iOS application you need to run simulator on your mac.
Just another unexplained bug.as usual with this 'solution'
Make sure you have Xamarin installed on Windows and it matches the Mac version.
- 2
You need to post this on the VisualStudio forum if your using the latest stable release or any 4.x release. Also note it does from time to time not connect so go to Tools-Options-Xamarin-iOS and double click on the build host, it should re-connect.
This works for me when it happens (assuming Xamarin 4 installed):
1. Open the Xamarin Mac Agent dialog - either from the iOS toolbar or from Tools > Options > Xamarin > iOS Settings > Find Xamarin Mac Agent button.
2. Right click on the Mac agent that you're connected to, and click Disconnect in the context menu.
3. Once disconnected, reconnect to the Mac agent in that same window.
4. iPhoneSimulator device options should now show in the build toolbar.Another thing to be aware of is that the iOS device options will go away if your startup project is not the iOS project. For example, if you have a solution with multiple assemblies and one of the others happen to be set as the startup project. In this case you just have to set the startup project to the iOS project and the list of devices should show up. If not, then try the steps above. As a last resort restart Visual Studio.
That doesn't work for me as the iOS build host times out intermittently. Only a restart of VS solves it. There's some stability fixes to improve this in the upcoming SR2 release, also in the Cycle 7 alpha release. They are addressing the issues I raised which is encouraging.
I've been trying to use VS for Xamarin.iOS development for years and there are always 'upcoming stability fixes' to the build host. Definite improvements over the early days. Back then any efficiency gains I realized by using VS over Xamarin Studio were lost and then some due to constant build host issues. Now, I can actually develop in VS with reasonably few issues. I can only imagine this will continue to improve with Xamarin being acquired by Microsoft.
Out of curiosity, is your setup something like a Parallels or VMware Fusion on a Mac, or are you connect across a network to a dedicated Mac build machine?
No VM's, Win10 x64 talking to (sort of) a Mac Mini across a network. A Hotfix solved the timeout so it's definitely something they can fix, it just never made it into a cycle release but they have ensured it's been added now along with the fix for ad-hoc in house profiles in VS. I know most of the workarounds but it's still a pain, like you say, I think post MS acquisition things will improve in that area but it might take a little while for us to see the benefits on the product engineering front.
Same problem for me too , I just realized that if I rebuilt iOS project it appers. Or I start Project While the Emulator is open it works. Dont forget build and start project while the Emulator is on.
- 0
@seanyda said:
Make sure you have Xamarin installed on Windows and it matches the Mac version.This worked for me