I have just updated my Windows Phone HTC 8S to Windows Phone 8.1 Developer Preview and I would like to begin playing around with any new API's. I did come across the Windows.Phone.System.LockScreenExtensibility namespace, but it says:
Minimum supported phone Windows Phone 8.1 [Windows Phone Silverlight
8.1 apps only]
Is there a difference between normal Windows Phone 8 apps that we're currently making, and "Windows Phone Silverlight 8.1" apps? I've never heard of Silverlight 8.1 apps before.
Windows Phone Silverlight 8.1 is a 'continuation' of Windows Phone 8 Apps (apart from native apps and some exceptions, most of WP8.0 apps were Silverlight 8.0). It gives more possibilites with little change to your code, you can read more here at MSDN:
The Windows Phone Silverlight 8.1 app model gives Windows Phone 8 developers access to some of the newest features available in Windows Phone Store apps without significantly modifying existing Windows Phone 8 code.
When developing Windows Store apps under 8.1 there are two main paths: Windwos RunTime Apps and mentioned Windows Phone Silverlight 8.1 -> MSDN. Both have advantages and disadvantages. Windows Runtime Apps can be far more easily ported to other devices, you will also find some API's available only for runtime apps and some other Controls under WinRT. You may also want to read about Universal Apps.
As for Silverligt you may also look at this video.
More about programming concepts you will find here at MSDN.
So when you find such a sentence:
Applies to: Windows Phone 8 and Windows Phone Silverlight 8.1 | Windows Phone OS 7.1
it means that it can't be used with WP8.1 RunTime Apps. And vice-versa:
Minimum supported phone Windows Phone 8.1 [Windows Runtime apps only]
only for RunTime apps. Good example here is different navigation in those two models.
Related
In my windows phone 8.1 project I am using MediaCapture Api for capturing photo's, but I experienced issue on the devices that comes with 8.0 and later upgarded to 8.1,
The problem is that on such devices camera capture fails after taking 10-15 images and it's just saves green screen instead of original image.
So what I thought is to create 8.0 class library and use CameraCaptureTask of 8.0.
Will that work? If so than Is it recommended way to do so?
Guessing that your 8.1 project is 8.1 XAML not 8.1 Silverlight the answer is no. The camera API really sucks in 8.1 XAML, if it is a core functionality of your app, just go with 8.1 Silverlight.
I have a Windows Phone 8.1 project, and a Windows Phone 8.0 library.
I need to add it into my Windows Phone 8.1 project; but at runtime, I have the following error:
FileNotFoundException: could not load or assembly Microsoft.Phone,
Version=8.0.0.0. The system cannot find the file specified.
So my question is simple: are 8.0 libs compatible with Windows Phone 8.1 app ?
If not, what should I do ? Migrate them ?
If your project is Windows Phone 8.1 Silverlight, that it should work fine. If your project is Windows Phone 8.1 XAML (which seems more probable according to the error message) , then no, no way to use it without rewriting.
I have developed a Windows Phone 8 App in C# but now I want to export it for Windows Surface.
I have already export my WP 8.0 app to 8.1 but this is a Windows phone 8.1 Silverlight app that is created whereas Universal apps use WinRT (if I have well understood ...).
So, there is a easy way to convert a windows phone 8.0 app (in silverlight) to universal app to be compatible with Windows Surface ?
I have updated my code to WP 8.1 and wanted to organise it better by using Class Libraries.
The doubt comes when I find there are 2 Class library project templates for Windows Phone:
Class Library (Windows Phone)
Class Library (Windows Phone
Silverlight)
If i select template 1, i see the assemblies referenced by default are .NET for Windows Store Apps and Windows Phone 8.1
If i select template 2, i got asked the target version of the Windows Phone OS (8.0 or 8.1) and the assemblies references by default are .NET for Windows Phone and Windows Phone.
Do you know the differences between them?
I have looked into the matter and seems it depends if you want to load the .NET runtime namespaces or not, am i correct? Are there any more differences?
The class library type will depend on whether your main app will be a Windows Phone 8.1 Silverlight app, or Windows Phone 8.1 XAML app.
The advantage of WP8.1 XAML app is that it is converged with Windows 8.1 - you can even create an Universal App that shares almost all code and xaml between the Win8 and WP8.1 apps.
The advantage of WP8.1 Silverlight app is that it is more closer to the old WP8.0 app - less changes are required, and also it has access to some APIs not available to WP8.1 XAML apps.
I am writing a Windows Phone 8.1 runtime app. The InkPresenter class which was available in Windows Phone 8 is not there in 8.1.
Now, 8.1 should be backward compatible with 8 and that all the apps that used the InkPresenter class in Windows Phone 8 can run on 8.1 too. So my guess(and I can be wrong in assuming this) is that the Inkpresenter class should be there in Windows Phone 8.1 too but might be under a different namespace. Otherwise, how could the apps of Windows Phone 8 using the Inkpresenter class be run on Windows Phone 8.1.
Is my guess true? If yes then please specify how to find the new namespace.
You are writing a Windows Phone 8.1 Runtime XAML based app which targets new sets of common WinRT API's for Windows Phone 8.1 . And Windows Phone 8 apps target sliverlight api's, if you want to use the same api's in Windows Phone 8 in your Windows Phone 8.1 then try writing Windows Phone 8.1 sliverlight apps, this will solve your problem. This will help you understand better