I'm building a Windows Phone application and my client has given me a list of languages that he would like the App to be localized for.
The problem is that some of those languages are not supported by Windows Phone and I then decided to check out the list of supported langauges which is available here. I noticed that there are two OS option for Windows Phone, i.e. 7.0 and 7.1 but during development I am not sure of how to check for which OS the phone is running so that I know which list of languages to supply to the user.
I'd like to know how to check if the Windows Phone OS is 7.0 or 7.1 (I'm assuming that his caters for later OS versions that might have come after the list was created)
Check this Windows Phone Team Blog post.
Microsoft already stopped the support for OS 7.0, so you don't need to worry about 7.0. GO ahead with 7.1
Microsoft is closing it's marketplace for devices running Windows Phone 7.0. So you shouldn't need to check if it's a 7.0 device, since your app probably won't be installed on one of those.
Here is an article describing this.
http://www.mofonu.com/2012/04/26/windows-phone-marketplace-closing-its-doors-to-devices-not-running-mango/
Related
I am developing new windows phone 8.1
[RT] application working fine , but now my client want to give support to tablet also . Does my application work in tablet or I have to create a universal project ?
Please help me out for this .
Windows Phone 7.x or 8.x apps do not run on Windows 8/8.1/10 "out of the box" - you need to either have a universal app, or share your code (for example as a portable class library) to allow it to also run on the desktop variant of the OS.
If you want your app to run on over vendors tablets (such as Android or iOS) there are solutions that allow some code sharing, but again, you're looking at supporting another codebase to achieve this.
Apologies for the noobish question, and I did try to search but couldn't find the right answer (or didn't search properly).
Currently have an app developed in a windows desktop environment because it gives us access to deeper features of the PC such as serial port comms etc. that the normal metro environment wouldn't allow. We're currently developing the UI based on metroUI so we can run it on an 8.1 touchscreen (metroUI looks good, gives us a touch-screen experience with PC features) but we have no intention of putting it on the marketplace.
Just wanted to confirm if this is in fact doable, and we can have this desktop application with a metro UI? Or is my noobishness meaning I'm overlooking some technical feasibility that makes it impossible?
This is doable with the Windows 8.1 Update (from April 2014). It's not supported before that since Windows Store apps were blocked from communicating with desktop processes.
The Windows 8.1 Update adds a feature "Brokered Windows Runtime Components" designed to allow side-loaded Windows Store apps to communicate with a desktop back-end. This will allow your Windows Store app UI to call the desktop component to access API that aren't available in the limited app package environment.
See Brokered Windows Runtime Components for side-loaded Windows Store apps for details.
See Try It Out: Sideload Windows Store Apps on TechNet for how to enable side-loading on your systems. See Windows 8.1 Update: Sideloading Enhancements for updates on how to enable a system for sideloading (no license required when on a domain, and significantly easier to get a sideloading license for non-domain joined systems).
The developer license system is designed for development and test purposes only. You really don't want to use it for production. Use the proper enterprise side-loading system instead.
From my understanding, the whole point here is to make it look like a Windows Store app. If you're app is a WPF one, you can already use Mahapps.metro.
You can create a Windows Store app without going to the store by Sideloading it. You create an app package first. The user has to right click the .ps1 file in that package to see the option Run with PowerShell and install it in a very old fashioned DOS like manor. It will only run when the user has a Microsoft Developer License and renew it every month. However, it is not allowed to keep using a Developer License of the end user to run a Store app. In the end, the system has to be domain bound to be allowed to run these apps, or you have to buy a Enterprise Sideloading key. These come in packages of 100 for $ 3000,- or you can unlock all PC's for 1 client for $ 100-.
It would be nicer if the specific pros of a Store program were available in a desktop environment but with W10 coming up I do expect a bit more integration and less restrictions.
Hope this answers your question.
I found two links for creating a SQL Database. What is the difference between two approaches? Which one is better? This or
this?
I need my app to run on all versions of windows phone(7,7.5,8)
thanks in advance......
If you want your application to run on WP7, 7.5 and 8, then go with what the second link mentions - local database in your app.
Sqlite is officially supported in Windows Phone 8 only so that will not be the best choice for you.
Sqlite is more powerful, and cross platform with other mobile ecosystems, but not with older version of Windows Phone.
I am developing Windows Phone 7 application with C#.Application have to download torrent files.So it's extension ".torrent".But Windows Phone doesn't support torrent files.So it says "Can't download file.Windows Phone doesn't support this file type." What can I do ?
There's no way to add handler for custom extensions in Windows Phone 7. According to rumors based on the leaked SDK, it may be possible in Windows Phone 8 (but no official announcement yet). So for now, there's nothing you can do.
I want to develop an application for Windows 7.5 mango OS phone like HTC Mozart, I am already having Visual Studio 2008, will the apps built by Windows Mobile 5 smartphone SDK be supported in a windows phone?
No, the Windows Phone SDK is the only one that is supported. In short, Windows Mobile != Windows Phone.
Also the UI is drastically different and the underlying runtime and .NET framework is also different. You might be able to port the logic of your code across easily to the new SDK, but the UI will need rewriting.
There are also a lot of freedoms lost in the new iteration as "the user is king". This means you need to review what your current app requires and provides to see if it is even a good fit for the new range of phones.
No, Windows mobile SDK wont work for Windows phone 7 applications.
See, the .NET Framework for windows phone 7 has changed completely . Infact the classes and APIs have changed .you can carry forward your previous experience of Windows Phone development into this new one but that certainly might not be the same code and services working in the same platform