Project > Visual C# > Cross-Platform > Mobile App (Xamarin.Forms)enter image description here. The form that appears after hitting "OK" does not provide UI Technology options: (Xamarin Forms/Native) like it used to.
This issue has been logged on the Visual Studio developer community forum: https://developercommunity.visualstudio.com/content/problem/215468/ui-technology-options-are-missing-in-cross-platfor.html
In the meantime, if you are looking to develop a new Xamarin solution using Xamarin native instead of Xamarin.Forms, you can do this by creating each platform app individually, and then creating your shared project or class library all within one solution.
For Android native: Project > Visual C# > Android > Blank App (Android)
For iOS: Project > Visual C# > iOS > Universal > Blank App (iOS)
If you're using a class library to host your shared code, remember to add a reference to the class library in both the Android and iOS projects.
Related
I am a newbie working with Xamarin Forms in Visual studio 2019.
When I create a blank page for Mobile App(Xamarin.Forms) , I do not see a Xamarin.forms portable template app in my project solution.
There is no PCL anymore. PCL is outdated. Just use the Mobile App (Xamarin.Forms) template. It will create all you need.
The core project (that contains your shared code) will be a .net standard project.
.net standard is way better than PCL, because you don't have a artificially limited set of APIs.
this creates the following 3 projects
Your shared code should go into the App8 project
I am developing a xamarin cross platform project in visual studio environment, I want to add CoreBluetooth library to my project. According to this link xamarin link
I am new to develop xamarin.Please let me know how to add this library.
I have a project in Android Studio (on a pc), and as far as I know now Microsoft owns Xamarin and its free once you have a Visual Studio license, then you can develop apps using C#(Already know that I have to port the JAVA code) and then compile in a MAC the IOS app.
My 2 concerns are:
When you can't compile, will the IDE show the IOS related errors?
There is a clear implementation of "cross platform code" vs "specific code"?
How Xamarin manage it?
In addition, our plan is to finish the app for Android which is our primary target and then manage the IOS, besides the other questions, what I need to know is if that is possible.
Yes, the VS IDE will show you build errors from the iOS build server.
Yes, you can build an Android app using Xamarin and later extend it to build an iOS app also. This is easiest if you use Xamarin Forms, but it also possible with native Android/iOS UI, but will be much more dependent on how you architect your applications.
I'm working with Xamarin plugin in Visual Studio 2013.
I have an iOS app and I want to add the Azure Mobile Services client component to that app. But when I click "Get more components" and search for the component in the store, it is not found.
I tried doing the same from the Xamarin Studio on my mac and the component is there.
Is this a bug or am I doing something wrong?
Update
The component is now available in the component store for unified api projects. It became available 1 day after I asked my question :-)
My guess is that you are trying to add it to an iOS Classic project on the Mac with Xamarin Studio but using an iOS Unified project on Windows with Visual Studio.
Looking at the Xamarin Component Store the Azure Mobile Services client is currently only available for iOS Classic projects. You can see that by the tags. It has an ios tag but not an ios-unified tag.
Xamarin Studio will not show the component when you click Get more components if it is incompatible with the current project.
I have some confusions About the IDE to use for MvvmCross
a) VisualStudio (VS) uses Xamrarin.iOS and Xamarin.Android plugin for iOS and Android development. But can we also use PCL(Portable Class libraries) and MVVMCross/Monocross frameworks in VS? I see the PCL option on VS but, i don't see the support for Android & iOS. Do i need to install additional plugin for PCL to support these two platforms as well?
b) Xamarin IDE supports Android and iOS development on Mac but, is it true that Xamarin doesn't support Mono.iOS on windows? Isn't it strange that Visual studio can use the network mac for iOS development but why not Xamarin Studio?
Thank You for your time.
Regards,
Saurav
a) VisualStudio (VS) uses Xamrarin.iOS and Xamarin.Android plugin for iOS and Android development. But can we also use PCL(Portable Class libraries) and MVVMCross/Monocross frameworks in VS? I see the PCL option on VS but, i don't see the support for Android & iOS. Do i need to install additional plugin for PCL to support these two platforms as well?
MvvmCross currently uses Profile104 for Portable Class Library development. You can easily develop for this profile without installing Android and iOS. The mapping of PCL profile to platforms is, however, quite confusing (it's not exactly obvious) so the easiest way I find to create a Profile104 PCL is:
to create any PCL
then to manually edit the csproj file to say Profile104 - look for a line like: https://github.com/slodge/MvvmCross-Tutorials/blob/master/Babel/Babel.Core/Babel.Core.csproj#L14 in the csproj
I have customers who develop in medium size teams where only some people have the Xamarin tools installed - most people have just Windows tools and work on the PCLs using Unit Tests and using WindowsPhone/Store user interfaces.
b) Xamarin IDE supports Android and iOS development on Mac but, is it true that Xamarin doesn't support Mono.iOS on windows?
Yes, this is true.
Isn't it strange that Visual studio can use the network mac for iOS development but why not Xamarin Studio?
This may feel strange, but I believe this is actually this is Xamarin listening to their customers.
I believe, that the reason customers wanted Windows support for iOS was because they wanted to use Visual Studio and they wanted to use plugins like Resharper. Xamarin provided this in their 2.0 release.
It is true that they could also have added iOS functionality to XamarinStudio for Windows as well - but this (I believe) wasn't what any of their customers were asking for - so adding it would have created more work (both in creating and maintaining it) without adding any significant benefit (IMO)