A client has asked us to "revive" an old Windows Mobile application that is used by their receiving department.
At some point they wrote a custom Windows Mobile 6 app for Windows CE devices (a Motorola MC55A to be specific).
They have a project in place to replace this app - but it won't happen for a bit and they want to install the custom app on some newly refurbished devices they found as an interim solution.
I found the source code for the application. It even contains an installer project that generates the CAB files.
What I do not know how to do is get the compiled app and installer onto the device.
I am using one of their legacy computers to build the app and connect to the device. The computer has Windows Mobile Center installed and when I see the device connected - I the ability to add / remove programs on the device.
Not sure if this is the route I should be going. Ideally I want to put the installer behind a web page and just have each device download the installer to install the app.
This stuff is pretty dated - I am having a hard time on the specifics of deployment.
You can put the CAB file on the device and launch it manually using the file explorer on the device to install the files.
Some industrial devices like Honeywell, Intermec, Motorola, Symbol, Zebra and others support the auto install of cab files, if the files are put in a special folder on the device. For former Intermec Honeywell devices, this folder is called \Flash File Store\CabFiles. If a cab file is placed in this folder, it will be installed on the next reboot.
You may also put a link to the CAB file on a web site and open that web site within the Internet Explorer on the device. The device will ask for the installation, when the file link is tapped. Please note that some web server like IIS by default block CAB files from being loaded! If so, you need to configure the web server to allow cab file downloading.
Many months later, but I wanted to answer this for future reference, when you DEPLOY Solution, Visual Studio (2008 was the last one supporting windows mobile apps) will ask you for a target device or emulator, here you can select the device and it will be installed, there will be no entry in add/remove programs on the device unless you install it via an installation CAB. You must create an "Smart Device Cab Project" and configure it for your solution.
Are there any ways to simulate ionic hybrid apps on Windows 7 without using MacOS or virtual machine such as VMware/virtual box?.
Specifically, I read ionic documents and references and tried to apply sim-ios & sim-deploy on Windows 7. However, on Windows, sim-deploy seems not supported.
and the information I am looking for related to this is pretty much out-dated.
NO..., To simulate a app you need Xcode installed which you cannot on windows, You can get away with browser testing using Chrome built in browsers but that's about it.
I had the same issue when I wanted to Deploy a IOS app on windows
We know that Blackberry 10 can run Android app. Does somebody tried Telerik Nativescript for Android and make it run for Blackberry 10?
If so, is it possible to explain the steps to be able to do it? Does Webworks gives any help?
Telerik NativeScript for Android does indeed work on BlackBerry OS 10 I've tried on (10.3.2.2474). I'll list some tips to get you started, but please keep in mind that NativeScript doesn't officially support BlackBerry OS.
Deployment with the {N} CLI tool (tns) might be problematic - it produces an apk for the app, but it can't deploy it on the device itself, so you need to transfer it somehow and install it on the device.
Alternatively you can use Telerik AppBuilder to build the app (either version will work - VS plugin, CLI tool, Windows or Web clients) and deploy it on the device via QR code scan and install. However, apk installation is a bit slow process on a BB10, so you may choose to use the NativeScript companion app for development. Deployment to the companion app is done via QR codes - it has an integrated QR code reader - and since no installation is necessary, development cycle is faster. There is a small issue with the app - it may seem to crash on the first run, but you can still find the Sync and Scan buttons in the BlackBerry Hub, which you can use to scan the code and start your app.
Releasing the app in the BlackBerry store is out of my scope, but you can check these documents:
https://developer.blackberry.com/android/documentation/rpkg_with_bb_plugin_for_android_stdio.html
https://developer.blackberry.com/android/documentation/publsh_your_app_to_appworld.html
Make sure you've built the app for release as mentioned.
Let me know if this helps.
I have a developer unlocked Lumia 635 just yesterday updated to Windows 10 Mobile Technical Preview (OS version: 10.0.12562.84).
After creating "Blank App (Windows Universal)" targeting Windows Phone 10 in Visual Studio 2015 RC and tried to deploy it to the device (and have changed configuration to ARM for that exactly purpose) I've got this error:
Error : DEP0001 : Unexpected Error: A Prerequisite for an install could not be satisfied. (Exception from HRESULT: 0x80073CFD)
After quick look at the app "references" it is turns out there are some of them specific to Application Insights (and few others) with disregard to the fact that I've specifically unchecked the Application Insights integration on project creation dialog before (surprise!). So I've removed them all leaving only the following (seems like unremovable):
Analyzes
.NET for Windows Store apps
Windows Universal
But this didn't help, unfortunately - still can't deploy this "default" app to the phone.
Though, deployment of my current working universal app that target Windows Phone 8.1, to this phone was just flawless.
Working OS is Windows 8.1 Pro, if that matter.
Update
Strike-through text above is not important anymore, see accepted answer.
I'm on the .NET/UWP team. The official answer from Microsoft is here:
https://msdn.microsoft.com/en-us/library/windows/apps/dn706236.aspx?f=255&MSPPError=-2147217396
Let me write out the steps from that link above. These steps apply today (May 20th 2015, using VS2015 RC that was released at BUILD.) Deploying to mobile was not possible prior to May14, when the correct build of Win10 Mobile came out.
Your machine should be running Windows 10, build 10074 or higher, from here: https://insider.windows.com/
I installed it "clean" on my SurfacePro1. To do this, first download the ISO of Windows10 from http://windows.microsoft.com/en-us/windows/preview-download, and then use "Rufus" http://rufus.akeo.ie/ to create an installable USB image from the ISO. Within Rufus, for my SurfacePro1, I had to choose "FAT32" and "GPT for UEFI". I don't know what you need on other machines.
Install VS2015 RC from here: https://www.visualstudio.com/en-us/downloads/visual-studio-2015-downloads-vs.aspx
During installation, you get to choose which components to install. You should choose "Windows 10 tools and emulators". Installation takes from one to several hours.
It will install Windows 10 SDK version 10069.
There are some glitches with the installer. If you go back to AddRemovePrograms and modify which components of VS2015 RC are installed, then it ends up installing more than it really should.
When VS runs for the first time, it asks if you want to sign in. I always used to click "no" and it'd then ask me more configuration questions. But if I answer "yes" and I sign in, then it bypasses all those configuration questions, and ends up being quicker. Lesson learned: I now always sign in.
You can run Win10 apps upon emulators. The emulators came with the Win10 SDK, and so are running version 10069 of the Win10.Mobile operating system.
You can run Win10 apps on your local machine. To do this you local machine must be Win10.Desktop version 10074 or higher and must be unlocked.
Instructions for unlocking are at https://msdn.microsoft.com/en-us/library/windows/apps/dn706236.aspx. Here's a "TL;DR" version:
Run gpedit.msc > Local Computer Policy > Computer Configuration > Administrative Templates > Windows Components > App Package Deployment. Then right-click to enable two things,
"Allow all trusted apps to install"
"Allow development of Windows Store apps"
You can run Win10 apps on your phone. To do this your phone must be Win10.Mobile version 10080 or higher (which came out on May 14th). Your phone must be unlocked.
Instructions for unlocking are at https://msdn.microsoft.com/en-us/library/windows/apps/dn706236.aspx. Here's a "TL;DR" version:
Plug your phone in by USB. Run "Windows Phone Developer Registration" tool from your desktop.
The key fact about Win10 is that you can write software against one particular SDK (e.g. the 10069 SDK that came out at //BUILD), and still run it on a more recent version of Win10 (e.g. 10074 that's current for Win10.Desktop program, or 10080 that's current for Win10.Mobile insider program).
In the .appxmanifest file, MinVersion="10.0.10069.0" says that your app will refuse to deploy to any machine which is running a lower version of Win10.
In the .appxmanifest file, MaxVersionTested="10.0.10074.0" says that if your app is deployed to a machine which is running a higher version of Win10, then it might have to do "quirking".
Both of these things are controlled by the Project>Properties dialog, and are actually stored in the .csproj/.vbproj.
The answers by #user4855870, #Rexobias and #Sevenate were hacks. They were sticking in an artificially low version for MinVersion to work around the fact they hadn't yet updated their devices. That's a fair approach (and I did it while I was waiting for Win10.Mobile 10080 build to be released). But now that it has been released, there's no need for these hacks, and you should just update your device.
I found that:
Solution Explorer -> Right click on project -> properties -> debug -> on start options -> target device: choose device and save.
Deploy again!
Hope this helps!
In Package.appxmanifest try changing the TargetDeviceFamily to the following:
<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.1.0" MaxVersionTested="10.0.1.0" />
I just faced the same problem described by #Sevenate.
Following the response of #user4855870 I'm finally able to deploy my blank Universal App to my Lumia 520 running W10 TP.
1) On the phone, go to Settings, System, About, More Info and write down the OS version (in my case it is 10.0.12534.59);
2) On Visual Studio, open Package.appxmanifest and in the same line mentioned by #user4855870 on the "MinVersion" write "10.0.1.0" and on the "MaxVersionTested" write the OS version you got from your phone.
<TargetDeviceFamily Name="Windows.Universal" MinVersion="10.0.1.0" MaxVersionTested="10.0.12534.59" />
My blank Universal App works on computer and phone as it should ;)
Ok, I've managed to finally deploy this sample app to the Windows Phone 10.
Short answer
In your project's Package.appxmanifest change the MinVersion from "10.0.10069.0" to "1.0.22816.1" (unexpected, hah?) like this:
<Dependencies>
<TargetDeviceFamily Name="Windows.Universal"
MinVersion="1.0.22816.1"
MaxVersionTested="10.0.10069.0" />
</Dependencies>
Longer answer
After you'll build the project just created from new "Windows 10 Universal Blank App" template in VS2015 RC the original Package.appxmanifest available from solution explorer in Visual Studio will copied to YourBlankWin10PhoneProject\bin\x86\Debug\Core\AppxManifest.xml (notice the Core subfolder in the path) and updated with new dependency - .NET Core Runtime package:
<Dependencies>
<TargetDeviceFamily Name="Windows.Universal"
MinVersion="10.0.10069.0"
MaxVersionTested="10.0.10069.0" />
<PackageDependency Name="Microsoft.NET.CoreRuntime.1.0"
MinVersion="1.0.22816.1"
Publisher="CN=Microsoft Corporation, O=Microsoft Corporation,
L=Redmond, S=Washington, C=US" />
</Dependencies>
(Don't confuse with another copy of the original unmodified version of the manifest at YourBlankWin10PhoneProject\bin\x86\Debug\AppxManifest.xml)
As you could see MinVersion for both dependencies is different and the application's one is greater then the Core Runtime component's. Now if you update MinVersion in the original Package.appxmanifest from the solution explorer to match the MinVersion of the Microsoft.NET.CoreRuntime.1.0 package, i.e. to 1.0.22816.1, next time you'll build the project the Core copy of the manifest will be updated accordingly:
<Dependencies>
<TargetDeviceFamily Name="Windows.Universal"
MinVersion="1.0.22816.1"
MaxVersionTested="10.0.10069.0" />
<PackageDependency Name="Microsoft.NET.CoreRuntime.1.0"
MinVersion="1.0.22816.1"
Publisher="CN=Microsoft Corporation, O=Microsoft Corporation,
L=Redmond, S=Washington, C=US" />
</Dependencies>
Now application should be deployed to the phone without problem.
PS. Found the hint to solve this in Deep Dive into XAML and .NET Universal Windows App Development video, fast forward to 0:19:50.
Deploying a Windows 10 app to phones is not currently supported*. The functionality is expected in a future update (to either Windows 10's phone version, the developer tools, or both).
For now you can use the emulators to test apps on the phone form factors.
edit: here's the official word from Microsoft:
MS Developer Tools Blog link
*it looks like some are able to hack it to work
I would like to learn something about i phone development. So, first i want to know that, Can i run basic application on windows?
Is there any apps or tool available for the same. I knew, We can run this on Mac/Ubuntu. But, I have installed windows 7 in my laptop.
would be grateful for help.
For learning purpose you can install a virtual machine install OSX and try some of the examples (which i'm guessing is not legal). But if you want to create an app to upload it to the store you will need a mac machine.