I have a Windows 8.1 app that I'm trying to upload on store. I've done it multiple times before, but now it's popping this error:
Project "XXX" depends upon SDK "Microsoft Player Framework v1.8.1.0" which supports apps targeting "Windows 8.0". To verify whether "Microsoft Player Framework v1.8.1.0" is compatible with "Windows 8.1", contact the SDK author or see http://go.microsoft.com/fwlink/?LinkID=309181.
Only thing I remember doing is updating the "Update 2" for Visual Studio. Except that, everything is more or less the same. Previous versions of the app contained the same Microsoft Player Framework version and there were no problems uploading to store.
Also I'm coding in XAML/C#, but don't think it's relevant on the subject.
Related
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.
I have made an app that targets Windows 8.1, and on my phone i am running Windows 10 Mobile Insider Preview. Now while debugging with the emulator and the device i had no problems with the app, but i believe since the app is not showing up on Windows Store (App is in the store, published earlier today) while browsing with my phone it could have something to do with my version of Windows on the phone.
As the title says, can i make a project in VS2013 that targets both Windows 10 Mobile and Windows Phone 8.1 (or even 8?), and does Windows 10 Mobile find Windows 8.1 Apps in store?
You don't need to do anything special. An app targeting 8.1 would show up in the new store, and anyone would be able to download it.
It's possible that your app just hasn't been published yet. The publishing process takes quite a while, from hours to a day or two. Check out your store dashboard to verify your app's progress.
Windows Phone 8.1 Apps will show up in the Windows 10 Store automatically.
It takes 1-2 day to be searchable on store. If it doesn't, contact Windows Store support, through dev portal, and report the issue. https://dev.windows.com/en-us/community/windows-app-support
If you want to make use of the Universal Windows Platform which is new to Windows 10 (including Mobile), then that particular app wouldn't run on Windows Phone 8.1. If you're not dependent on Windows 10 specific APIs or functionalities, then you could consider targeting Windows Phone 8.1 as Universal App.
You can also create a solution with a shared project in Visual Studio 2015 (free in the community edition, in case you're up for switching over) - in that case you can have a Windows 10 (Mobile) specific binary as well as a Windows Phone 8.1 version that share some code - this would be the best of both worlds in term of target system optimisation, maintainability and avoiding code duplication.
There is a nice step-by-step guide: http://www.c-sharpcorner.com/UploadFile/7ca517/shared-project-an-impressive-features-of-visual-studio-201/
I get the following error compiling my new universal app for Windows Phone and Desktop version 8.1:
The SDK "MSAdvertisingXaml, Version=8.1" cannot be referenced alongside SDK(s) "MSAdvertisingXaml, Version=6.1", as they all belong to the same SDK product Family "Microsoft.Advertising". Please consider removing references to other SDKs of the same product family.
They both use the same tool, AdControl, and it was running phone while I built the Windows Phone side of the app. Once I dropped the same control into the Windows Desktop side of the app, I get this error. I can't get ANYTHING to return when I Google the error message. What is the problem???
In the top portion of the list within your "Solution Explorer" control (of MS Visual Studio - my version is 2013), look for a "References" section. Simply delete the 6.1 item, as you want the latest version of the AdControl, which should work with both sides of your universal app.
I was watching some video tutorial for developing Windows Phone 7 apps (& hoping to develop Windows 8 apps on that basis ;) The guy in the video tutorial was using Visual Studio 2010 and I have Visual Studio 2012. He created a new project using the option "New -> Project -> Silverlight for Windows Phone". Although I don't have such an option I do have an option called "New -> Project -> Windows Phone". This got me wondering whether there is a difference between those two. Could anybody explain the difference between them, if there is any?
Visual Studio 2010 can only make applications for Windows Phone 7. And Silverlight is the only API available to third-party developers on WP7 (even XNA is based on Silverlight).
With Windows Phone 8 (supported by Visual Studio 2012), new kind of applications were added: native (C++ based), HTML5... That's why calling the category "Silverlight for Windows Phone" didn't make sense anymore, and it was renamed simply "Windows Phone".
It's just a name, it makes no difference to you. When creating a new "Windows Phone app" project, Visual Studio will ask you which version you want to target. If you pick "Windows Phone 7.1", you'll get the exact same API that you had in Visual Studio 2010.
Microsoft only trying to reduce the terminology and popularize certain ways.
Windows phone app is the same as Silverlight for windows phone. the only difference is that Silverlight project in visual studio 2010 targets at the developer choice windows phone 7.0 or Mango (Mango is numbered by the SDK as Windows Phone OS 7.1, while users call it Windows Phone 7.5) or 7.8 according to updates installed. But if you use the windows phone project in visual studio you will target either Windows phone Mango or 7.8 or 8. please note that optional updates may be needed to target some platforms as Windows phone 7.8. windows phone 7.8 is basically a windows phone 7 with some feature backported to it from windows phone 8 as multi size live tiles and some features not backported to it as arabic support.
Silverlight and XNA were completely separate ways to make apps in Windows Phone 7.0. No code silverlight code could be used in a XNA project, nor XNA code could be shared in silverlight project in WP7.0 . Programmers of Windows Phone 7.0 had to know the meaning of each and when to use before choosing. The learn paths of silverlight and xna were too separate that you could learn one and totally ignore the other; in fact most programmers learnt only one of the two. You had to choose your path between the two before implementing a big app, as there is no way back :i.e, no way passing code between the two.
However, starting of Windows Phone Mango, Microsoft introduced Silverlight/XNA. Silverlight/XNA is a new application model for Windows phone Mango. It allows XNA inside Silvelight App. Migrating an XNA game to Silverlight/XNA is not an easy task, but would be rewardable.
Silverlight have UI controls as Textblock and Drop list and have layouts as Grid and stackpanel; so it is easy to make an app in silvelight that look like a form, while XNA is geared toward games , as it is a state based programming . it is very hard to implement a drop list in XNA for most developers.
Silverlight app was renamed to windows phone app to popularize it as a starting point, without having to do a deep thinking in a choice.
Silverlight is a stripped down version of Windows presentation foundation, removing the ability to define your own controls.And Silverlight for windows phone is an even more stripped down version , removing all controls that do not fit on mobile , and removing most of cryptography libraries.
This is the same way microsoft renamed metro-style apps to be windows 8 app, and windows apps to windows forms apps; and then windows forms and WPF were renamed later to Windows desktop apps.
I have built my app for WP7.0 - will it still work on WP7.1?
Do I need to rebuild it using WP7.1 sdk? If yes, how can i rebuild my current app to 7.1 mango?
Your 7.0-built application will work as expected in 7.1, but the fast application switching (multitasking) experience may not be optimal.
To rebuild/optimise your application for Mango:
Install the updated tools (currently RC)
In the Properties pane of the application, change "Target Windows Phone OS Version" to "Windows Phone OS 7.1"
Update your code in App_Activated to only process the state if ActivatedEventArgs.IsApplicationInstancePreserved is false
Keep in mind that, for the next few weeks, you cannot release a bug fix for users with 7.0 once you release a 7.1 build.