For testing an application, I have deployed my metro app by creating a app package which is provided in vs2012. I have deployed the package by opening using the PowerShell, but now I want to deploy the metro app in a Windows 8 device (tablet) for testing it, how can I do this?
Will there be a PowerShell option available in device also? (to deploy the app)
Are there any other ways of deployment?
i have used this to sideload apps for testing onto other devices including SurfaceRT
http://blogs.msdn.com/b/patricka/archive/2012/11/06/10365947.aspx
In addition to creating an app package in Visual Studio 2012, and deploying your app that way, you can also use the Remote Tools for Visual Studio 2012 for ARM to deploy and debug an app to a Surface or other tablet (for x86 or x64 tablets, use the matching remote tools install).
Once the remote tools have been installed on the target device, you simply start up the remote tools on the target, configure the access permissions, and then on your development machine, open the project properties, select the Debugging option, and use the dropdown to select Remote Machine as the debugger to launch. Click into the Machine Name field, and use the dropdown to select the machine name of the target machine running the remote tools.
Now, when you start debugging the project, it'll be packaged up and deployed to the target device, and you can set breakpoints and step through your code. And once deployed this way, you can re-run the app from the start screen using the app's tile.
EDIT: One important thing to note...whether you deploy/sideload using the PowerShell script technique, or using remote debugging, the target device will need to have a valid developer license. You should be prompted to obtain a developer license when you attempt to sideload your app, but you can also use PowerShell to obtain the license manually...instructions can be found here: http://msdn.microsoft.com/en-us/library/windows/apps/xaml/hh974578.aspx
Related
I am using MobileFirst CLI 7.1. I want to deploy my MobileFirst CLI application to an android device. How can I do that?
In studio i use to get a projected generated when I right click > Build and depoly for all environments.
Also I want to know how can I target remote server. (In Studio we had an option to deploy to remote environment.)
Do we have any commands for achieving the above two?
In studio i use to get a projected generated when I right click > Build and depoly for all environments.
You need to have google's ADT tools installed and execute the commands from the command-line, or import the project into Google's Android Studio IDE.
Also I want to know how can I target remote server. (In Studio we had an option to deploy to remote environment.)
In the Studio you did not have the option to "deploy to a remote server". You had the option to configure the application to point to a remote server (the properties you can edit in the worklight.plist/wlclient.properties file).
This feature does not exist in the CLI. After building the project, in case you want it to point to a different server, edit the properties in said file(s) to point to the remote server.
I created a Windows Store app using Visual Studio(2013). Right-clicked the project and chose "Deploy". Where was the app deployed? What I want to do is to be able to run that app from cmd, not from Visual Studio.
So the question is: where is the app deployed? Can I somehow change that location?
Normally installed Windows Store apps are found here: %programfiles%\WindowsApps\IdentifierForYourApp. But when you deploy from Visual Studio (for the purposes of debugging and whatnot), Visual Studio just registers the app to run from within your build output folder.
But I don't think you can launch the program from a command line. Even if you try to just double-click the executable, you get an error "This application can only run in the context of an app container"
You can launch the app via the IApplicationActivationManager::ActivateApplication function in C++ code. There might be another way via managed code, but I'm not aware of it.
I am beginner in windows 8 metro application. I have create a simple application on visual studio 12. it is running in same machine . How can i install this application on other device running windows RT without publishing app in app store. Help me plz...Thankx
Choose 'Store->Create App Package' from the projects context menu, then select 'no' when asked whether to create app store packages. Then copy over the generated folders and execute the included PowerShell script to install the application.
In case your project contains platform-specific code, you have to make sure it supports compilation for ARM devices, which is what Windows RT runs on.
http://msdn.microsoft.com/en-in/library/windows/apps/hh975357.aspx this will help you in creating package.
If you want to make a basic package, change debug mode to release mode and then follow these steps
project=> store=> create App Packages => next =>create
I want to make a build (like APK) of my windows phone 8 app for testing. How can i do so.?
When you Run the Windows Phone 8 app in VS 2012, an XAP file is created in the Bin folder of your app. Its similar to the apk file of Android app. But you cannot directly install this in the phone.
You need a developer account to developer unlock the device for testing. You can test the app in Emulator any way. You can also make use of the Beta testing feature of the Windows Phone marketplace, but again you need a developer account for this as well.
UPDATE:
You can get a developer account from the Windows Phone Developer site # $99.
And after getting the developer account, Open the "Windows Phone Developer Registration" tool from your start menu and unlock your device, by following the steps mentioned in that tool
You actually can deploy a XAP file to the phone, provided it is developer unlocked. The tool to do this comes as part of the SDK. Just go to Windows Phone Developer Tools -> Application Deployment. Then you can browse and select the XAP file you want to install. As mentioned above, you XAP file might be in the bin folder, but it could also be in the Debug folder, depending on your configuration. In Visual Studio, to the left of the debug icon (green arrow) you will see a drop down list of deployment options. Here you can choose if you want to deploy to the phone or to the emulator. You can also chose if you want to deploy in debug or production mode.
Background
We're using System Center 2012 to deploy a Windows 8 Metro-style application to Samsung slates in the field running Windows 8 Enterprise x64. The slates are joined to the domain and have a persistent DirectAccess connection back to it, allowing System Center to push applications and updates to the devices.
We have to deploy our application to potentially hundreds of devices in the field, which is why we went the System Center route. The code signing cert is installed on every device using Group Policy. To deploy the application, you simply provide the package output and specify the collection of devices to install it on. The app just shows up on the device in a few minutes.
The problem we're having is that when System Center deploys our application, the SQLite dependency is lost and none of our data access works.
About our project
Our application is a WinJS application that uses SQLite as a backend. However, all our data access code is in a C# WinMD project which the WinJS project references. We're using the sqlite-net library to talk to SQLite - we included the source for that in our C# project.
In Visual Studio, we installed the SQLite for Windows Runtime extension as described in Tim Heuer's article. The Metro application references this.
Testing using other deployment methods
SQLite data access from the application works fine when you debug or run it locally - in both Debug/Release and x86/x64.
The app packaging process provides a PowerShell script that you can use to install the application and a developer license if necessary. When installing our app using the PowerShell script, SQLite data access also works fine. Verified this by packaging and installing both Debug/Release and x86/x64 versions of the app.
Troubleshooting
When the application first tries to use SQLite, we see an exception about it not being able to find the sqlite3.dll.
We've tried/verified the following:
Confirm that we're deploying a Release/x64 build
Examine the appx in WinRAR and verify that it contains the sqlite3.dll
Reference the "SQLite for Windows Runtime" extension from the C# project instead of the WinJS project
Also reference the C++ runtime, this caused System Center to fail when deploying the app. Don't know why yet, but looking into it.
UPDATE
The issue is that System Center is having trouble deploying the Visual C++ Runtime Library dependency that the SQLite library needs. So unfortunately this isn't a programming question anymore. We're getting some help on this and I'll post the fix.
I wanted to post the details of a temporary fix that we're going with. We've also gotten closer to the root of the problem, so I wanted to provide those details as well.
Recap of Issue
When referencing the Visual C++ Runtime Package from our Metro project, System Center is unable to deploy the application to the devices because there is a problem deploying the proper version of the dependency for the appropriate architecture and build flavor.
Our development machines running Visual Studio 2012 (and packaging the project for deployment) are using a newer version of the Visual C++ Runtime (50727) than what is available in a fresh installation of Windows 8 (50712).
Worked with the System Center team and confirmed that this was a bug in the version we were using and has already been addressed in future builds. We're going to work on upgrading the environment but that will take a couple of weeks.
Workaround
I confirmed and tested the following workaround:
Remove the reference to the Microsoft Visual C++ Runtime Package from the Metro project
Install the x64 version of the Visual C++ Redistributable for Visual Studio 2012 - http://www.microsoft.com/en-us/download/details.aspx?id=3
Deploy the application
Works like a charm because the correct version of the dependency is there already. Obviously not a long term solution if we choose to also target x86 and ARM, but will get us over this hump.