I'm running Embedded Visual C++ 4 with service pack 4, to develop an application for a device running CE 5.0. I'm using the CE 5.0 SDK for this purpose, which works fine except for the fact that while it will target my device (i.e. an SH4 based PDA), it will not let me select anything other than the StandardSDK emulator for debugging. If I go to Tools / Configure Platform manager, I can connect to my device under Windows CE default Platform, but I cannot select it from the Build Toolbar for output and debugging purposes. Is there any work around for this. I've considered moving to VS2008 for this app, but it breaks a large amount of 3rd party code.
Embedded Visual C++ and "Platform Builder" are different tools. The "Windows CE" SDKs are designed to work with "Platform Builder" to make things like OSes and drivers. However, Applications generally use the "Windows Mobile" or "Pocket PC" SDKs.
So here are three different solutions:
Continue to use EVC++ 4.0
If you want to keep using Embedded Visual C++ 4.0 instead of one of the newer IDEs, you can use "SDK for Windows Mobile 2003-based Pocket PCs". Which I believe is the newest SDK for EVC++ 4.0.
Upgrade to VS2005+
This details how to migrate from EVC++ to VS2005 while still making native apps.
You can use the 5.0 SDK line of features in the "Windows Mobile 5.0 SDK for Pocket PC"
Use Windows CE SDK to make Applications with EVC++ 4.0
It actually is possible to make Applications using a CE SDK. This is used by OS developers to make applications for their OS.
You can develop an application using
Microsoft® eMbedded Visual C++®
together with Platform Builder. Before
you can develop an application, you
must use Microsoft Platform Builder to
create an OS design, build a run-time
image, and then download the run-time
image to the target device.
When you download a run-time image,
Platform Builder uses a download
service to copy the run-time image to
the target device. When the run-time
image runs, Platform Builder
communicates with the target device
over a kernel transport.
To develop an application, keep
Platform Builder connected to the
target device, and then run eMbedded
Visual C++. After you write, compile,
and run the application, eMbedded
Visual C++ uses the established
connection to run the application on
the target device.
Note The previously mentioned
process differs from the process used
to develop an application for a
run-time image not downloaded by
Platform Builder. When you do not use
Platform Builder, you manually connect
to the target device using the
application connectivity
communications framework of Platform
Manager. For more information about
application connectivity, see
Application Connectivity.
-- http://msdn.microsoft.com/en-us/library/ms859575.aspx
Related
I'm trying to use NativeScript + Angular + SQLite to create a mobile application and following this video. At 3:00, it says to run the command tns platform add ios in the folder and I get the error "Applications for platform iso can not be built on this OS." The OS that I'm running is Windows 10 Home. Any help would be appreciated. Thanks!
You can not build apps for iOS using Windows OS, it's not limitation from NativeScript but from Apple itself. You need Xcode to build apps for iOS which can only be installed on Mac OS.
If you have an iOS device with you, you may use Playground or Preview to run your code directly on your device from a Windows machine. The CLI / Sidekick even support cloud builds.
If you like to use Simulators, the only option is to install Mac OS using Virtual Box but that may be terribly slow.
Currently I am using Ubuntu linux and I want to create a WinObjC app on Linux plateform. Is there any way to create WinObj apps on linux.
Sorry to disapoint you, but unfortunately there is not. WinObjC is intended to bring iOS apps to Windows 10. Basically it just enables you to write Windows 10 apps in Objective-C but you still need a Windows 10 machine to compile it.
A Windows 10 device and Visual Studio are mandatory at the moment, to create WinObjC apps.
Related to this
I'm planning to develop an app for Android using Qt Quick Controls and an Android Emulator. The same set of components is said to work on Windows Phone. Thus I'd like to build the app for Windows Phone as well.
Unfortunately, Qt for Windows Phone is only available for Windows.
I don't own any Windows phone. I'm using a computer running Linux.
Is it possible to build the app for Windows Phone and test it in an Emulator without virtualizing/dual-booting Windows
Well there is Wine. This is what wikipedia says about it;
Wine (short for Wine Is Not an Emulator) is a free and open source compatibility layer software application that aims to allow applications designed for Microsoft Windows to run on Unix-like operating systems. Wine also provides a software library, known as Winelib, against which developers can compile Windows applications to help port them to Unix-like systems.
You can find more info about Wine here; https://www.winehq.org/
I haven't tried it before but since it says "allow applications designed for Microsoft Windows to run on Unix-like operating systems," I'm thinking it should work.
This is your only option. If it doesn't work, then i guess you should think about running windows on virtual machine or dual booting with windows. Good luck!
I am developing Qt application for Windows CE 5.0 device.
My setup is:
Qt 4.7.3 compiled with Visual Studio 2005 using Windows CE 5.0 Standard SDK.
Everything works OK on real device, though I would like to test software "locally" in an emulator.
Visual Studio 2005 provides Pocket PC 2003, Windows Mobile 6 emulator images but no Windows CE 5.0.
Windows Microsoft CE 5.0 Emulator does that, but its sample device is based on i486, so this doesn't work for me...
I found some kind "Plaftorm Builder" and "ARMV4i BSP for Windows CE 5.0", but I am not building device or it's SDK, and I am not interested in specific device at all. All i need is "generic" AMRv4 WinCE 5 image for basic testing...
So what is possible outcomes for me?
Microssoft stopped providing Windows CE OS images for the emulator after the x86 emulator was abandoned, and for good reason. Windows CE is a modular OS so it's not possible to create an Emulator OS image that matches what all devices are and my guess is that there were too many support calls and complaints about how the emulator either contained something unwanted or didn't contain something that was wanted. The point being that there is no "generic Windows CE device" so there's no way to create an emulator of one.
The response from Microsoft was to provide the ARM-based Device Emulator 3.0 (available as a Standalone Release) and a BSP for the emulator so developers can create their own OS images that match their actual target hardware OSes.
So your options are to either create an OS yourself or find an OEM that provides an emulator image for their device (I'm not aware of one offhand, but I very, very rarely use the emulators so I've never bothered to look).
I have an embedded device,its includes windows CE 6.0 Build 3112.I want to run silverlight application on this device.I downloaded silverlight application,when I want to install it says "Silverlight is not valid application windows CE"
so what can i do?
Thx.
In Addition to ctacke's answer. Not all Windows CE devices have to have any specific component and that includes Silverlight for Embedded Devices.
To check whether your device includes Silverlight For Embedded devices, you can check whether your \Windows folder contains the xamlruntime.dll file. If it does not contain the file, then your OEM did not include Silverlight in the image.
If you want to check out a simple Silverlight for Embedded devices application you can download the code from the following tutorial: Silverlight for Embedded Tutorial
THe issue you're seeing is that while it's called "Silverlight", Silverlight for Windows Embedded really isn't what most developers who know Silverlight would call Silverlight (in fact I wish they'd rename it).
While it does use XAML and that XAML can be created using Blend, the code itself has to be written in heavily templated C++. You can't take a compiled Silverlight binary from anything other platform and use it under CE.