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.
Related
I was busy for a while, so I couldn't work with UWP enough. : )...
Today, I made project with Windows Template Studio, a powerful template.
after I created it, I clicked a XAML page. but XAML design viewer shows message that I need to update to Windows 10, version 1809 ( 10.0.17763.0) to see the contents of XAML viewer.
but I'm worried that my laptop said that its windows version is up to date. 1803
I'm a korean user, and if this problem will not be a long-term problem, and just localization problem with windows policy. then I would be happy and I would go to practice with building a tiny App.
but, if this problem is my problem. how can I update to windows 1809 or, just download SDK to solve this problem ? or can I degrade Windows template studio ?
addded
if I make project with blank uwp app - target version 1803 -, XAML design viewer works well. but if i make blank uwp app with target version 1809, I get same error message.
Right-click the solution in "Solution Explorer" and select "Retarget Solution". Set the Windows SDK version to 10.0.16299.0
In my case I installed only one sdk and that is why I was getting the above mentioned error. From VS installer I installed SDK support for each version and it worked fine for me and my machine is still on windows 10 1803 (I believe they haven't rolled out update for my machine).
Using VS2015 I upgraded a WP 7.1/7.7 project.
I was developing and testing fine using the 8.1 emulator for a couple of months until I realized that I was missing then newer 8.1 controls in the toolbox.
I started a new separate 8.1 project and I can see a large range of new controls like Listbox and ComboBox that don't exist in the 7.1 upgraded app.
Looking at the project properties the Target Windows Phone OS Version is set to Windows Phone 8.1.
I've searched all over and can't find any other settings to tweak.
The project has the older Windows Phone Toolkit 4.2013.8.16.
I wonder if that blocks the new tools?
How can I get the 8.1 one controls to turn on?
There's two frameworks on Windows Phone 8.1: Silverlight and WinRT. When you upgraded to 8.1, since your project was using Silverlight (WinRT wasn't available on Windows Phone 7), it was set to target Silverlight 8.1. That's why you can't use the WinRT controls. The thing is, WinRT and Silverlight have completely different controls, so you can't automatically convert a project from one to another. You've got to consider whether you really need/want to use WinRT. If so, you'll have to rewrite large portions of your UI code to accommodate with the new controls.
If you want to make the conversion, you should first have a look at the Microsoft documentation to understand the key differences between the two frameworks: https://msdn.microsoft.com/en-us/library/windows/apps/hh452743.aspx
Note that Windows 10 universal apps (the ones that can run on phone and desktop) use WinRT. Silverlight is deprecated, and sooner or later you'll have to upgrade.
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.
i am currently developing a Windows 8.1 app, trying to use live tiles.
The problem is, that the tile isn't showing up within the Windows Start Page. How do i let the tile appear? Are there any options in Visual Studio 2013?
Thanks!
In Windows 8.1, tiles aren't automatically pinned to Start for newly installed store apps like they were in Windows 8 - this is as true when Visual Studio is installing the in-development build as it is when users install it from the store.
You need to pin the tile to the start screen yourself. You can do that by either searching for the app's name or going to the "All Apps" view of the start menu and finding it there.
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.