I am not able to install the appbundle file in windows phone 10
I have tried copying the file on device and also via the winappdeploycmd.exe tool
But nothing works!
If you use .Net Standard 2.0 and Xamarin.Forms 3.0 you can't install the app on Windows 10 Mobile, because .Net Standard 2.0 support was added with the Windows 10 v1709 Build 16299, but Microsoft never released that version for phones. They hang at lower feature2 branch with Build 15254.
So you have 2 options:
use PCL as shared code with Xamarin.Forms 2.5.1 and Min/TargetBuild 14393/15063 to serve both, Desktop/Tablets and phones
create separate brach/app with PCL for mobile (Min/TargetBuild 14393/15063) and 1 app for desktop which uses .net standard 2.0 (Min/TargetBuild 16299/16299) and latest Xamarin.Forms version.
Related
The current official Xamarin website only supports iOS and Android:
https://developer.xamarin.com/guides/cross-platform/transport-layer-security/
The same goes for ModernHttpClient PCL (iOS/Android only)
So is there anyway we can support TLS 1.2 for Windows 8.1 and UWP platforms? If Yes, please share and provided tutorial with source code
I am using Profile 111 for my PCL
Many thanks!
Xamarin is meant to cover iOS, Android and Mac. As long as you are working on a Windows based platform, you're working with Microsoft .Net. This means, there is no need for any additional tooling and no Xamarin/Mono involved here. As of .Net 4.6 (or was it 4.5 - I don't remember 100% sure) you'll get TLS 1.2 support.
The above is also true if you are using Xamarin.Forms to run your apps on Windows (Phone) 8.x or UWP.
I just signed up for an Evernote API key and downloaded the Evernote SDK for Windows in Visual Studio 2015 (suing NuGet) only to be told "Evernote.SDK 1.25.0 is not compatible with uap10.0".... so it seems it only supports .Net v4.0 which is very disappointing. I had a great idea for a UWP app that I wanted to synch to Evernote but I guess now I can't do it.
In case you're not aware UWP (Universal Windows Platform) is now the standard for developing current and future Windows 10 apps that run across all W10 devices. Can anyone at Evernote tell me if the SDK will support this and if so when? More people already use Windows 10 than use iOS (on PC's and tablets at least) so I really hope this platform will be supported in the very near future.
From the 1.25 version number you mention, it sounds like you're trying to grab the older C# SDK. You can try the newer SDK for Windows and see if that works.
If that NuGet package also doesn't work in your UWP environment, you should be able to grab the source from Github and put that in your VS solution.
The requirements for the Visual Studio Tools for Apache Cordova specify that SDK for the API Level 19 must be installed. Do that means that apps created with it will only run on android KitKat devices? Any way to target older devices?
Please review the following article for reference:
https://msdn.microsoft.com/en-us/library/dn757054.aspx
Cordova targets a single SDK (currently 19 though a upcoming release will move this to 21). However this is just the SDK used to build - by default Cordova apps can be deployed on devices running API level 10 or higher (2.3.3). Unless you're creating a custom plugin that will use an API only available on Android 5.0, you won't be affected by the SDK used.
The Android tab on the config.xml designer allows you to set alternate values for what goes in "AndroidManifest.xml" file, but the build itself will always use SDK 19.
http://developer.android.com/guide/topics/manifest/uses-sdk-element.html
Android 4.4.x (API level 19) is required by Visual Studio to build app or create app package targeting Android platform not for running the app. You can create Cordova app targeting device running Android released before KitKat.
My company is developing corporate Windows 8.1 apps for use within the organisation. Although we are only targeting Windows 8.1, we are interested in developing our apps with a view to eventually target Android and/or iOS by using Xamarin.
So, we want to develop using PCLs that are compatible with Xamarin, but we haven't licenced it yet, since we're not ready. Can we simply install the PCL profiles for Xamarin so we can at least be assured that our classes will be compatible, if and when we are ready?
So you have couple of possibilities.
As m-y mentions in his comment you can install the trial and you will get the PCL profiles.
You can get someone else with the Xamarin tools installed to grab a copy of the PCL profiles on his machine (a bit harder to maintain).
You can buy the product (might not be what you want)
However, you could go ahead, make the PCL you are currently using and target it to WPA8.1 and Windows 8.1, and later on just change the profile and make the minor corrections it would take to get it working with Xamarin.
The profiles are not xamarin profiles - they are .net profiles which xamarin support.
The profiles are installed as part of visual studio 2013 - or can be installed as extensions to visual studio 2012.
If you select WindowsPhone Silverlight 8.0, .net 4.5 and Windows Store apps then this will allow you to build a profile 78 pcl library - which is one of the profiles xamarin support - and is a pretty good choice for modern development...
I have PCL with ".NET 4 and higher, Silverlight 4 and higher, Windows Phone 7 and higher, Windows Store apps (Windows 8)" (from project->properties window).
I have Microsoft.Bcl version 1.1.3 installed.
When I want to update the reference to 1.1.6 I see following.
Install-Package : Could not install package 'Microsoft.Bcl 1.1.6'. You are trying to install this package into a project that targets
'portable-net40+sl40+wp+win', but the package does not contain any assembly references or content files that are compatible with that
framework. For more information, contact the package author.
Looking at packages folder I see following:
./Microsoft.Bcl.1.1.3/lib/portable-net40+sl4+win8+wp71
./Microsoft.Bcl.1.1.6/lib/portable-net40+sl4+win8+wp71
Now the questions:
What is the difference between sl40 and sl4 profile, win8 and win
profile and wp and wp71 profile?
How can I update Microsoft.Bcl 1.1.6 in my project?
Microsoft.Bcl is targeting a later version of Windows Phone than your PCL project which is why it is failing to install.
Framework differences
sl40 and sl4 - same framework
win8 and win - same framework. win means win version 0.0 but NuGet maps this to win8
wp and wp71 - different frameworks. wp means wp version 0.0 but it is equivalent to wp7 by the way NuGet maps the frameworks.
Updating to Microsoft.Bcl 1.1.6
To install Microsoft.Bcl you will need to update your PCL project so it targets wp71 or above. So you can choose to target Windows Phone 7.5 or later or Windows Phone 8 or later.
If you choose Windows Phone 7.5 or later that seems to map to wp71 in Nuget.