I'm using Facebook C# SDK 5.0.8 Beta binary build.
When I try to add a reference of Facebook.Contracts.dll to my Windows Phone application I get the following warning:
If you add a reference to a silverlight assembly can cause unexpected behavior of the application.
Is it an error?
nope it's just that the dll was compiled against the desktop version of silverlight. This doesn't mean that it won't work, and you should be fine assuming that the dll has be tested on the phone.
Related
I try to create a new Xamarin.Forms project for Android and Windows Phone, but I'm getting stucked by two errors.
First of all, I have the following error:
DEP3321: To deploy this application, your deployment target should be running Windows Universal Runtime version 10.0.16299.0 or higher. You currently are running version 10.0.14393.0. Please update your OS, or change your deployment target to a device with the appropriate version.
I've found the solution for this error, on some forums people said that setting the TargetMinVersionPlatform to the current running version of Windows Universal Runtime and setting the TargetVersionPlatform to the expected one should resolve the error. Yes it's true, but now I'm receiving another error:
NU1201 Project App3 is not compatible with uap10.0.14393 (UAP,Version=v10.0.14393) / win10-x86. Project App3 supports: netstandard1.6 (.NETStandard,Version=v1.6)
and after I did some research I found that this problem is resolved by doing backwards all the workarounds that I've did for resolving the first problem.
So, in conclusion I'm being stucked between this two errors. Can anyone help me?
Thank you!
As the .NET Standard document, netstandard 2.0 can be used on UWP version 10.0.16299. It can not be used on UWP version 14393, so you can not change your app target min version to 14393. Currently, Windows phone version is 15254 and you can not run the .net standard 2.0 on windows phone. So the solution would be like # magicandre1981 said on his thread Xamarin.Forms UWP project wont install on windows 10 mobile
Besides, you can also try to create your Xamarin app target version 14393 on the VS 2015 directly.
I've developed a UWP project with Behaviors SDK in VS2015 (Windows 10).
Then I've installed VS2017 and tried to run the app without any changes. Unfortunately I'm getting below error for Behaviors SDK.
Are there any solution or workaround for this problem?
Reference Image:
Error Output:
error MSB3774: Could not find SDK "BehaviorsXamlSDKManaged, Version=12.0"
You should use the Microsoft.Xaml.Behaviors.Uwp.Managed nuget package instead (or Microsoft.Xaml.Behaviors.Uwp.Native if you develop your application in C++). The source code of these packages are available on GitHub.
Behaviors SDK was created for WinRT projects (Windows 8.0/8.1). Microsoft.Xaml.Behaviors.Uwp.Managed package seems to be a recommended replacement for the Behaviors SDK for the UWP applications (even in VS2015).
I have a Xamarin.Android application that is being built through a build server. The application is targeting API Level 23 and Min Android Version 4.1 (API 16). During debug the application works fine, but when the build server compiles the application, packages it, signs, and aligns it, it crashes on load with the error:
Unable to get provider mono.MonoRuntimeProvider: java.lang.RuntimeException: Unable to find application Mono.Android.Platform.ApiLevel_23 or Xamarin.Android.Platform
Most phones result in an immediate crash with the error mentioned above, but a handful of devices work fine. The only thing those devices have in common is they were used to deploy the application during development. This leads me to believe they have the shared run time installed and hence why it doesn't fail. The build server has the latest Xamarin.Android (just like the dev machines), latest Java, latest JDK, and latest Android libraries (per the SDK Manager). The configuration being built doesn't use the shared runtime, it is not linking (although I also tried it with linking SDK assemblies only), and it only supports armeabi-7va ABI.
What am I doing wrong?
I have finally found the problem which seems to be a bug with Xamarin (or Mono?). We have AndroidManifest.xml and AndroidManifestAlpha.xml. During the build we specify /p:AndroidManifest=Properties/AndroidManifestAlpha.xml to the MSBUILD arguments, but the compilation adds all the activity, services, and mono information to the AndroidManifest.xml file only. The build eventually uses the specified AndroidManifestAlpha.xml file and compiles the APK without the mono runtime; resulting in the error mentioned above.
Change the Target Android version. In VisualStudio on Mac, the path is Project->.Options->General->TargetFramework.
If someone finds this error check my answer in another post:
https://stackoverflow.com/a/52678522/1106547
It's for Xamarin Studio, but I guess should work for VS Xamarin extension too.
The main idea in my case was to put android-25 (or android-23 for the case of the original question) folder to the Android SDK platforms directory.
I suppose it allowed the Xamarin engine to install correct "..Platform.ApiLevel_" APK and use the shared library.
currently I have to port an existing mobile application which runs on Android and IOS to Windows 8. Unfortunately it is using a lot of C++11 Stuff, which is not supported by Windows Phone 8.0. The project itself was written with cocos2d-x 2.0. It contains a C# Part which loads a C++ library with the major part of the application. Also it includes modules from "Project Angle", which is a library to convert OpenGL calls into DirectX calls.
The first thing I tried was to upgrade the project to Windows Phone 8.1 using the 'reassign project' option from Visual Studio. I still had to remove a bit of C++11 Code, but now at least the project itself compiles. After compiling I got some linker errors for functions like 'getenv'. The angle libraries don't even compile and gives me errors like 'Cant find include file vccorlib.h' for every single source file.
Since I'm completely new to Windows development, I don't know if something went wrong on upgrading the projects, or if I have to fix something within the projects. But I tried to upgrade an other project, which was already ported to WP8, and got the same errors.
Now I have to deceide if I have to fix the Windows Phone 8.1 version or if it's easier to remove C++11 Code for 8.0 (which means a few days of work and let my heart bleed)
I also found a compiler update for Visual Studio 2012, which has extended support for C++11, but it seems it's not compatible for Windows Phone.
I hope someone of you could give me a hint, what I have missed for WP 8.1 or has another idea. Thanks for your help!
Cocos2d-x should work on Windows Phone, but you have to get the right version. You can't use pre-built binaries for other platforms (even desktop Windows) and you need to make sure you're building correctly. See the download page.
Visual Studio 2013 Update 4 is the latest stable release of VS that supports Windows Phone projects; you can see the level of C++11 support listed here along with support in the not-yet-finished Visual Studio 2015 compiler.
I'm following this tutorial for mvvmcross and I'm trying to get the "Windows Phone UI" project working. However when I try to set references to the mvvmcross binaries, Visual Studio (2012 Premium) displays an error: a reference to a higher version or incompatible assembly cannot be added to the project.
I am using the mvvmcross binaries from 2013_01_28 as specified in the tutorial and have installed Windows Phone SDK (7.1 and 8.0). I have tried with both WP7.1 and WP8 projects but same error occurs.
Are there perhaps different binaries I should be using for WP8 VS2012?
What am I missing here?
Thanks in advance!
My guess is that you downloaded the files from the Interweb and Windows is protecting you from evil.
Try unblocking the assemblies:
http://pcmusings.wordpress.com/2012/10/31/vs2012-windows-phone-and-the-reference-to-a-higher-version-error/