Install XAP file locally in windows phone 8.1 device - windows-phone-8

Hope You are doing well.
Actually i have created one windows phone 8 application. So for testing i have installed the .xap file locally into windows phone 8 and it is working fine. But if i am going to install that .xap package in windows phone 8.1 or later it is not getting installed.
I have made research and found that the windows phone 8.1 and later OS version devices are accepting the APPX Package. They will not allow to install .XAP locally. Now the scenario is like that my client wants to test this application in windows phone 8.1 device.
So, Can anyone help me out that how can we install locally XAP package into windows phone 8.1 device?
Awaiting Response. Thanks in advance.

You can sideload your .xap package on Windows Phone 8.1 device using Windows Phone Application Deployment Tool (for 8.1).
Before installing , you need to ensure the device has been registered for development. You can use Windows Phone Developer Registration (8.1) to enable your device for development.
And you could search for the tool from the Windows 8.1 start menu.

Related

Test windows phone 8.1 app update, after app is published once in store

I have build a windows phone 8.1 app, and i have published it in Windows Store.
Now i want to do an update, but before i want to test it in several devices. I created a package flight but it is only for windows os 10. How can i test in devices that have windows 8.1 os version?
When you publish application in Windows Store you can have a package for Windows 8.1 and for Windows 10. Even more - you can have multiple packages depend of build version.
When you fill the submission in Pricing and availability you can find option:
This way you can make it available for specific people

Windows Phone Emulator 8 can't install Xamarin application

I have created a Xamarin application and compiled to Release. It was succesfully tested on an Android emulator so I decided to deploy it to a Windows Phone 8.0 Emulator.
I tried to use the Application Deployment but it cannot install because it starts the emulator that never boots, it shows OS starting (starting the emulator on its own is working).
So I downloaded it to the phone and when I try to open it, it says:
Can't install company app. There is a problem with this company app.
Contact your company's support person for help.
Why is the app considered company app? How can I install it to the emulator? What should I set?
The solution consists of two steps.
The company app issue is present because I've downloaded the application from a website, so it is unsafe (the source is the Internet). I have to install it through application deployment (via Visual Studio 2013 or the Windows Phone Application Deployment application).
The second step is to discard (and uninstall) Windows Phone 8.0 and change to Windows Phone 8.1. That helps a lot.

How to debug windows phone apps on windows tablet

Ok so I got windows 8.1 nextbook to test on. I created some basic browser app in visual studio running on virtual windows server 2012 r2. My main machine is windows 7. When I connect with USB cable nothing happens (who could have predicted that). I thought I could deploy my app on tablet and do a debug like that but haven't find a way to do it. Anybody here with experience in this scenario, I googled everywhere and the only thing I found is that documentation sucks
You cannot run a Windows Phone app on Windows. You need a Windows Phone or a Windows Phone emulator to run the Windows Phone app. To run on Windows you need to write a Windows Store app. Windows 8.1 on a tablet is the same as Windows 8.1 on a desktop or laptop computer.
In your case you'll probably need a physical Windows Phone since you are already running virtualized. The Windows Phone emulator is a Hyper-V image and is not supported nested in a Hyper-V guest OS.
If you write a Windows Universal app then the code will be mostly the same for the Windows and Windows Phone targets (the UI layer is usually different), so you can write and test the bulk of the app as a Windows Store app to run on your tablet and then recompile for Windows Phone.

Deploying on windows phone 8.1

I installed the last version of visual studio to target windows phone 8.1 OS. After the installation I figured out that the 8.1 OS was not yet released and I couldn't deploy my application on my device. Can I target the windows phone 8.0 version when building the application?
Yes you can. Go to your project properties and there on your application tab, you can select the target OS.
Select This Project Template & It will prompt you to select your targeting Windows Phone OS
But Once you have targeted 8.1 you can't deploy on a 8.0 device or emulator.

Windows Phone 8 SDK debug wont start

I have installed Windows Phone 8 SDK, openened the VS express for Windows Phone,
created New Project with simple app, pressed F5, but the emulator wont start.
Is comes up with error:
Exception from HRESULT: 0x89721800
I don't have any network drivers installed which should be called Windows Phone Emulator.
I have Windows 8, with built-in Administrator account and full privs.
P.s. Main reason for this I want to deploy some apps on my Nokia Lumia 800.
I have unlocked it, but when i was deploying app with deployment tool, it came up with the same error message.
P.p.s I've installed Windows Phone SDK 7 and there the emulator worked, but i can't find any way to deploy app to phone
I blogged about this a couple of weeks ago. You can see the full details here: Resolving windows Phone Emulator Problems
XDE cleanup, and Hyper-V is a very common reson for problems with the emulator!
Regarding deployment to phone from windows phone sdk 7, remember to change debug device from "Emulator WVGA 512 MB" (or what ever you use) to "Device", and always start Zune before your start debugging and deployment.
If you had installed Windows 8 (Single Language or Home Edition) with Windows Phone 8 SDK you can't develop mobile applications because it doesn't support Hyper-V.
The only way to work with Windows Phone 8 is to change your OS to Windows Pro or higher.