I have been trying to deploy my metro app from win8 machine to a tablet .
I am able to complete the whole process of creating the package,signing it and deploying using Powershell in the tablet .The tile of the app appears on the start screen
but when I click on the tile the app just shows the splash-screen and crashes.
The deployment worked no for one of my sample apps but it's not working even for some of the MSDN sample apps like the LockScreen Personalization.
Have you added the "developer licence" on the target computer? This can be done using powershell (but in admin mode)
All information can be found here: http://msdn.microsoft.com/en-us/library/windows/apps/hh974578.aspx
Shortly, you need to run Get-WindowsDeveloperLicense from a Powershell in admin mode.
Related
I'm trying to deploy a Windows Phone 8.1 Application via Enterprise distribution.
For this I'm using BuildMDILAPPX.ps1to sign the application with a symantec certificate.
The Application works as expected when deployed via Visual Studio or via Application Distribution.
However once I try to install the application generated by BuildMDILAPPX.ps1 certain functionality (Database with SQLite) seems to produce an error, as the application behaves differently (e.g. stuck on screen).
Is there a way to debug this application via Visual Studio, or any other way?
Or is it possible to deactivate optimization via BuildMDILAPPX.ps1
Thanks for your help,
Dominik
I solved it by using Toast Notifications to display which line was executed or to display variables.
Not a clean solution, but it worked.
I have a Lumia 800 (WP 7) that used to be developer unlocked, but seems not to be anymore, so I can't deploy an app to it. OK, I tried to use the develop registering tool. It sees the phone, and then prompts me to log into App Hub with my Live ID. I understand this is the same as the Microsoft Account nowadays, but the tool says logging in does not succeed and asks to check the credentials.
At the same time I am logged in to the WP Dev Center with my Microsoft Account which works fine. So I'm confused why the developer registration tool does not let me in.
I have tried this with two computers, both running Windows 7 and Visual Studio 2010 Express for Windows Phone, with the same result. Tried also a Windows 8.1 and WP SDK running in VS 2013, which asks to run Zune. I haven't Zune there and failed when tried to install it.
I've seen this thread, which advises to use Windows 7 environment, but as explained it does not work for me. So what am I missing? Is the registration tool outdated?
When I go in to debug the app, it asks me to choose where I would like to deploy it. When I select Windows Mobile 6.5.3 Professional Emulator and click the Deploy button, it starts to work and throws up a command line and then it goes away and Visual Studio doesn't appear to be in debug mode.
I have the Device Emulator open, Windows Mobile 6.5.3 Professional Emulator loaded and cradled. Can someone help me figure out why it will not let me debug this project?
Brad, I downloaded the code and just unpacked the zip to D:\boxoffice_mobile (a local drive partition). Then I started VisualStudio 2008 and opened the solution file. I get a warning message that the project is not loaded from a trusted location (http://msdn.microsoft.com/en-us/library/bs2bkwxc%28v=vs.80%29.aspx). As I do not use a network drive, I ignored the warning two times and the projects load all fine.
BTW: I found a great tool to manage these 'security' warnings: http://blog.codingoutloud.com/2010/03/05/the-project-location-is-not-trusted-dealing-with-the-dreaded-unblock/. The message had nothing to do with a remote file access.
Then I just looked at the solution configuration to ensure that only the needed projects are build and did no change, as only BoxOfficeMobile and WebserviceTest are set to build and only BoxOfficeMobile is set to deploy.
Then closed solution configuration manager and just pressed F5 to start debugging to see what happens.
The startup project BoxOfficeMobile was build and deployed to "Windows Mobile 6.5.3 Professional Emulator". The emulator started and the files were deployed and the project was stopped by a breakpoint inside the code:
Here is another screen shot with the emulator set to 'Display: Always on top':
So, as you can see, the project is fine and the debug issue on your site is caused by a different setup.
Do you load the project from a network drive share? Try moving it to a local drive and run it from there.
Did you change Device settings in the VS2008 Tools:Options menu? Here is my setup (as coming as default, I did not change anything):
and the details:
The additional settings available via the buttons are empty (Configure) or unchanged (Emulator Options).
I am very interested in seeing what you changed to be not able to debug the project.
before you start developing for Windows Mobile 6.5 Prof, you need to setup your development environment.
First, install Visual Studio 2008 (no express version)
Download and install either ActiveSync (host OS <= Windows XP) or Windows Mobile Device Center / WMDC (Windows Vista/7)
[optional] Download and install Device Emulator Manager
Then download and install Windows Mobile 6.5 DTK (http://www.microsoft.com/en-us/download/details.aspx?id=5389)
Now, you can start a new C# project inside Visual Studio 2008:
Follow the wizard:
The list of Target Platforms depend on the Mobile/CE SDKs you have installed!
Select either .Net Compact Framework 2.0 or 3.5. The choose depends on what is installed on your PC and what is available on the device. If the device comes with 2.0 pre-installed, I would choose 2.0 except for I need something only available in 3.5 (ie Mobile.Status namespace).
Now you get an empty form:
You can change the target device in the project properties:
If you want to change the target platform, look at "Change Target Platform" in Project menu or just right click the project in solution explorer and select Change Target Platform:
The above has nothing to do with Device Emulator Manager or the installed Emulator Images!
You can run a WM5 targeting project on a Windows Mobile 6.5 device if you want.
To start debugging and SmartDevice application inside an emulator. Just Select an Emulator entry from the target device list in Project properties or just in the SmartDevice toolbar. Then click Debug and "Start Debugging". VS will start an emulator with the specified emulator image and deploys your project application files and start remote devugging.
You may also start an emulator image using DeviceEmulatorManager and then cradle the running Emulator image. To use the running and cradled (ActiveSync or WMDC connected!) emulator do NOT select an emulator inside VS but a Device. VS does not see the difference and uses the WMDC connected device, regardless of being an emulator or real device.
VS uses DMA to communicate with the emulator, not USB or Serial as with a real device.
Now start your development.
First of all clean your project.Then freshly start the emulator.Right click the project and select build.Then Debug the project.Your project will be started in Emulator (Don't Open the application from your Emulator at this time).
Just check your Emulator Start>File Explorer>My Device>Program Files whether the project has been previously installed.If so uninstall from the Settings> System > Remove Programs. And try re-building application and deploy it.
I have a small WP app and I need to show a (interactive) demo of it and show its features, to another person who doesn't have any WP-related software installed on his PC.
Is there a super lite version of the WP emulator that the other person can download?
Also, how can I create an installation file of the WP app so that it would be easy for him to install & run ?
Surely he won't need to install the whole SDK, including Visual Studio, right?
To run the emulator you'll need to install the full SDK (http://dev.windowsphone.com/en-us/downloadsdk) but note that this doesn't require an existing version of Visual Studio.
There is no stand alone installer for just the emulator.
Apps are compiled into XAP files (similar to APK) and the Application Deployment application (installed as part of the SDK) will allow this to be loaded into the emulator. This tool can also be used to load the app into attached, developer unlocked, devices.
In terms of demonstrating an app to someone not familiar with Windows Phone, I've found that getting them to experience it on an emulator is often a sub-par experience and doesn't create the best experience. It's far better to get people to experience applications on actual devices. Alternatively, if it's very early in the application's development it's often better just to capture a video of the application running (from the emulator if fine and normally easier).
He would need to install VS Express with all the requirements that needs (Win8, CPU support for Client Hyper-V).
Emulator works pretty well over Remote Desktop and other remote viewing tech such as Skype, so that's another option.
Ok, i think i've found the needed steps:
send the XAP file from "Documents\Visual Studio 2010\Projects\AppName\Bin\Release\" where "AppName" is the name of the app.
download and install the sdk . not sure if Visual studio is needed.
run "XapDeploy.exe" tool which will allow to run the emulator and install the XAP file into it.
The file is somewhere similar to :
C:\Program Files (x86)\Microsoft SDKs\Windows Phone\v8.0\Tools\XAP Deployment
run the app from within the emulator.
I'm trying to debug an app running inside the windows phone 7 emulator, but I can't connect to it from visual studio - Attach to Process -> selecting Windows Phone 7 Emulator transport displays an error:
"Unable to connect to 'Windows Phone 7 Emulator'. Not implemented"
What am I missing?
As a workaround:
open the solution configuration manager
next to build is a deploy column, uncheck your project
press F5
This will launch the app that is already on the device without overwriting it (and deleting its storage).
I don't think it's possible to connect to an app that is already running on the emulator.
It sounds like you're trying to connect to the emulator directly yourself,rather than the app running in it. Which I don't think is what you want anyway.
It may help if you think of the emulator as a virtual machine. That's what it is. (near enough.)
If you want to debug an app in the emulator, you need to launch it through Visual Studio.