If I use visual studio 2012 RC write an application for windows phone 8. I want to know whether I can install and run the same application on windows phone 7?
No, there is no back-compatibility. You could do it the other way round, though, and write a WP7 app that would run on WP8
It is not possible to build for WP8 and deploy to both WP7 and WP8.
It is possible to build for WP7 and deploy to both WP7 and WP8.
The best solution is to code carefully, and clearly separate out your use of WP8-specific APIs.
You could then have two projects, one for WP7 that you build using WP7 tools, and one for WP8, that you build using WP8 tools. Linked files in visual studio would be a good way of achieving this.
Related
I develop many UWP apps to Windows 10, but to Windows 11 I have so many questions and sometimes the Microsoft Docs it's confusing. I want develop new apps to Windows 11 but I am totally lost!
What is the difference between Windows App SDK and WinUI 3? I dont understand :(
And what is the best way to develop Windows 11 apps? Still UWP? Or Windows App SDK? Or WinUI 3?
UWP dont have round corners thats correct? I create a new project in my computer with Windows 11 in visual Studio 2022 and only the window of my app have rounder corners, but another elements (for example buttons) dont have rounded corners!
And Mica is not only availabe in WinUI 3?
The Windows App SDK is the next evolution in the Windows app development platform.
WinUI is the UI part of the Windows App SDK. It provides UI features for the Windows App SDK apps. When you create a Windows app SDK app, you have to use WinUI3 to create the UI layout. The previous version of WinUI like WinUI 2.7 could be used in UWP apps.
Using UWP or Windows App SDK depends on your own requirements and scenario, both of them could work on Windows 11.
I had developed one application for WP8 devices(Target OS is WP8) in VS 2013 with WP8.1 SDK.Now I need to give support to WP7 also.Can I use WP7 SDK on VS2013 and develop app for WP7.So, I will create 2 apps for WP7 and WP8 and upload both on store.
What should be better solution?
Thanks.
I've encountered this problem several times, unfortunaly VS13 does not cooperate if you want to work with WP7 projects.
So if you really want WP7 apps, which I would reconsider since the marketshare is relatively small and I'd guess that people who download apps already have newer versions. Don't forget that lot of features may not be suported and you'd have to come up with new solutions..
Anyway, in case you decide to create WP7, dowload VS12 Express for example, create WP7 project and then copy files from your WP8 and see what works and what not.
You can open an existed project of WP7 using VS2013, but can't create new project by it.
When you create a new project in VS2013, it can only be WP8.0 or 8.1.
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.
Since the release (and in some cases prior to) the release of Windows Phone 8, several WP7 apps on the marketplace have had updates that simply state "Updated for Windows Phone 8."
What does this mean, exactly? Because the marketplace allows multiple XAP uploads, is it a new XAP for WP8 but the app only allows a single description (thus "updated for WP8")? If so, does the marketplace push an update for WP7 even if the WP7 XAP hasn't changed?
Or, are there changes to the 7.1.1 SDK that optimize for WP7 apps on WP8? If so, could you provide a link outlining this? (I did a search, but all I could find is the 7.1.1 update targets 256MB devices.)
Bottom line, although I know WP7 apps are compatible on WP8, is there something I should be doing with my WP7 apps for WP8 while still functional on WP7?
Take a look at this, seems to be an issue that is being worked on at the moment.
http://social.msdn.microsoft.com/Forums/en-US/wpsubmit/thread/789b3017-d242-4151-9d0b-84c85c4b3c24
These tags of "Updated for Windows Phone 8" don't necessarily mean that the app has been upgraded to a Windows Phone 8 application. It could also mean that the developer has tested and fixed bugs that can break functionality for a Windows Phone 7 app in Windows Phone 8. For example, I found two bugs involving local storage in Windows phone 7 projects when running on Windows Phone 8. Therefore, I had to make some adjustments to get my project running 100% on Windows Phone 8 (but its still a WP7.1 project). For more information on bugs and "quirks" when running WP7.1 projects on Windows Phone 8 here is a link to Microsoft's information.
http://msdn.microsoft.com/en-us/library/windowsphone/develop/jj206947(v=vs.105).aspx
I must be doing something wrong when I'm doing my builds. I want my current update to be available for Windows Phone 7 and Windows Phone 8. I am using the WP8 SDK and targeting OS 8.
When I upload my XAP I get the AnyCPU.xap and now my app is only available on WP8. How can I make it available on WP7 as well?
DevCenter and the WP runtime works as following:
You can have one WP7 XAP and that could run on both WP7 and WP8.
-or- You can have one XAP for WP7 and one (or more) XAPs for WP8. The "or more" part comes in for multiple resolutions.
However, there's no way to take a WP8 project compiled in VS2012 and run it on WP7. You can't run WP8 XAPs on WP7. That's pretty obvious once we think about it since the assemblies being used in WP8 aren't available on WP7.
So, developers have to choose which code sharing model across WP7 and WP8 works for their app:
if your app only uses WP7 featuresets and looks OK on WP8 HD, use a WP7 XAP.
If your app only partially uses WP8 featuresets, create on WP7 XAP, and share the codebase to create WP8 XAP that lights-up with WP8 featursets.
And if your app must have WP8 featuresets (e.g. NFC or Bluetooth centric apps, etc) then you obviously can't target WP7 and can only submit WP8 XAPs.
Here's a print screen demoing the DevCenter support for submitting multiple XAPs for the same app on different platform versions and different resolutions:
For more information on how to target both WP7 and WP8 see this Nokia developer article. The article explains how to share code between WP7 and WP8 at runtime & compile time, what new features are WP8 exclusive and how to support multiple resolutions. I helped author that article so hopefully you'll find it useful. There's lots of helpful techniques that might not be obvious.
The Dev Center now allows you to have multiple xap files submitted for a single app.
So you can have one version submitted targeting 7.* and others for 8.*. E.g.
This allows you to target both platforms from one app.
You need to reupload the XAP file with Target Windows Phone OS Version in Visual Studio project properties set to Windows Phone OS 7.1