Install metro application in windows 8 device - windows-8

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

Related

Not able to run hybrid application in windows phone 8 in IBM Worklight

I made a project in IBM Worklight Version 6.2.I am have added android,iOS and WindowPhone8 Enviournment for the project.I am able to build and run the application in android and iOS.But when i imported the project in VS2012 for windowPhone8 It is not Working.It is not showing the Css and the click events are not working.Seems like it did not loaded Js and css but these files are present in folder structure.
Do i need to do any changes or am i doing anything wrong.Kindly help me running my project in Windows phone 8.
Thanks in Advance
From tests performed, the Windows environment is built and displayed correctly. You've been asked to provide the project where this is happening to you. Do that.
Try cleaning Visual Studio's cache, try to preview your app in MobileFirst Studio and make sure there are no errors.

Titanium Studio with Windows Phone Plugin: Titanium SDK does not support the Windows platform

I want to do Windows Phone development with Titanium Studio.
I followed https://wiki.appcelerator.org/display/guides2/Getting+Started+with+the+Windows+Phone+SDK#GettingStartedwiththeWindowsPhoneSDK-UsingStudio(Preview) in order to get the Windows plugin. After a required restart of the software, the Windows option apears in the Deployment Targets when creating a new project.
Unfortunately, for all Titanium SDK Versions I have installed, 3.5.1.GA, 3.5.0.GA, 3.4.0.GA, 3.3.0.GA, I am getting an error like "Titanium SDK v3.5.1.GA does not support the Windows platform".
So I basically cannot create projects for Windows Phone.
I am using Titanium Studio 3.4.1 and followed the installation tutorial, though I deleted the SDK path after setting it (it is the default path, setting a value caused an error message, also I left the publisher GUID and Windows Store Certificate empty, since I just want to develop and don't have publishing credentials yet).
How can I create an app that runs on Windows Phone, too?
Edit:
I add some images to show the problem better. In the last step, I don't have the possibility to create a Windows project in Titanium Studio.
2nd edit:
As per Eduard's answer, I skipped https://wiki.appcelerator.org/display/guides2/Getting+Started+with+the+Windows+Phone+SDK#GettingStartedwiththeWindowsPhoneSDK-WindowsPlatform(Preview) and had to do it. Now I got Titanium SDK 4.1.0.v2015... and I get the option.
Unfortunately, it still does not work.
https://jira.appcelerator.org/browse/TISTUD-7171
So I also need to update Titanium Studio.
Well, I guess mobile development has to be buggy and cumbersome, at least that is my experience so far with various (cross-platform) products.
Try opening the solution generated in Visual Studio to attempt packaging the .sln to .appxupload to upload it to the Windows Store. Hopefully that will serve as work around until Titanium has full support for Windows (very likely 4.0.0 or 4.1.0 Titanium SDKs).

How to test the developed app in Windows 8 RT

Recently I had developed a C#/XAML METRO Application, I created the package which generated the Add-AppDevPackage.ps1 and all other files from VS2012.
How to deploy this package in real device for testing in Surface RT tablet?
Right click on "Add-AppDevPackage.ps1", select "Run with powershell". Follow the instructions in powershell. Please note you must be admin. If you are prompt for developer licence login with Live a/c.

How to deploy a metro app to windows 8 device/Tablet?

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

Deploying a Windows 8 Metro application that uses SQLite

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.