I have built an smart device app in VS 2008. I could deployed and debugged in Windows Mobile OS devices successfully.
But, I must have to deploy and debug the same app usign Windows CE 4.1 device as well. The problem is compact framework version that indicates the app is higher version of compact framework so i can not run the app in CE 4.1 device.
So I have tried to debug the app using emulator.
I would like to ask that I have failed to debug the app in any emulator which is listed in VS 2008 devices list.
I'd be glad if there is a workaround to solve the issue!
thanks!
Check out this topic: Minimal system requirements for .NET Compact Framework 3.5
It may help you. Deploying maybe possible but debugging will be very slow if it is working. I tried this with a PPC2003-device and this was horribly slow.
You have too keep in mind that CF3.5 needs much more CPU and Memory.
Related
I am new to WUP and researching on Windows Universal platform, I have following questions for the same:
1)I would like to know if anyone has used it, and if it can be deployed anywhere else other than the windows store. How can we make the app available to the users/client without deploying it on the Windows store. (where else can we deploy the app?)
2) Will the app developed using WUP only works on Windows 10 or previous version of windows as well?
3) Can it be developed using 2015 or 2017 is mandatory?
Thanks in advance
1)How can we make the app available to the users/client without deploying it on the Windows store. (where else can we deploy the app?)
Typically, you download these apps from the Store and that is how they are installed on your device. But you can sideload apps to your device without submitting them to the Store. This lets you install them and test them out using the app package (.appx) that you have created.
For more info, please refer Sideload your app package.
We can also use the App Installer, it is a Universal Windows App that is pre-installed as part of the Windows 10 Anniversary Update. The app enables a user to double-click any .appx or .appxbundle for easy installation, eliminating the need to run PowerShell or specialized scripts.
Please refer the App Installer.
2) Will the app developed using WUP only works on Windows 10 or previous version of windows as well?
Windows 10 apps can only run on Windows 10 (and newer). If you want to target 8.1, you have to build a Windows 8.1 app. A Windows 8.1 app should run on Windows 10 without any problems.
You can refer the Develop apps for the Universal Windows Platform (UWP), it lists the requirements of UWP apps.
3) Can it be developed using 2015 or 2017 is mandatory?
Yes, we can use the VS 2015 or the VS 2017 to develop the UWP apps.
Please refer the document of Build UWP apps with Visual Studio.
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.
I have universal project targeting Windows Store 8.1 and Windows Phone 8.1 platform.
The windows one works fine but I having trouble running the WP one on an emulator. I get the error message saying:
Microsoft Visual Studio Unable to activate Windows Store app
'numbers-here!App'. The Kiss.WindowsPhone.exe process started, but the
activation request failed with error 'Msg in polish that the app did
not start'.
If this was Windows I would check System Event Log and see the logs just before the error what DLL the system was trying to load and that helped a lot when I was debugging similar problem with Windows Store project, here I have no clue on how to check what exactly was being loaded.
The worst part is that I created package (appx) and checked the dll's being packed with exe, it seems that it includes dependencies that the app explicility uses yet something is still missing and this might be some 'hidden' dependency of one of the other dlls.
Any ideas how to debug such issues with emulator?
For me it was due to having WIC code in my App and/or calling CoCreateInstance in a windows phone environment ( on PC it works flawlessly though )
I ran into the same problem on Windows 10. Turns out, that there is no Kernel32.dll on Windows 10 phone!
Instead you need to link against OneCore.lib which provides the entire Win32 API subset that is supported in UWP. This "umbrella library" will load the correct dlls at runtime.
See also:
https://msdn.microsoft.com/en-us/library/windows/desktop/mt683763(v=vs.85).aspx
I'm a little new on Window Embedded Compact 7.0(WEC 7) so I have some question about it :
1- Is there any handheld device that runs with it? All I found run on 6.5 and lower win CE versions ( check this link please : http://www.microsoft.com/windowsembedded/en-us/evaluate/windows-embedded-handheld-devices.aspx)
2- what's its .Net framework version? .NET CF 3.5 or .NET CF 3.7 ? I don't know whether its technology related to windows 7 or windows phone 7. If its .NET version is .NET CF 3.7, can I run my old .NET 3.5 apps over it or I should change them to silverlight version? (As I know I cannot run them on windows phone 7)
3-I couldn't find any screenshot of it.
4- For window phone 7, there is a free add-on on VS 2010 for development (although publishing is not free). Is there any free development toolkit & emulator(handheld emulator indeed)?
Thanks in advance
4-..or Completely I'm in a wrong way of thinking? ;-)
About your questions:
1- Is there any handheld device that runs with it?
Yes there are.
The Windows Embedded Partner Program might give you more alternatives
2- what's its .Net framework version? .NET CF 3.5 or .NET CF 3.7 ?
Windows Embedded Compact 7 includes the .NET Compact Framework 3.5
I don't know whether its technology related to windows 7 or windows phone 7.
AFAIK, it is not related to Windows 7, and it is not realated at all with Windows Phone 7.
If its .NET version is .NET CF 3.7, can I run my old .NET 3.5 apps over it?
The .NETCF version is 3.5, so yes, you can run your old >NETCF applications.
or I should change them to silverlight version?
If you do that, then your application will not work anymore. WinCE 7 does not support managed silverlight, it only supports something that is somehow called Silverlight but it actually targets development in native code using C++.
3-I couldn't find any screenshot of it.
Here, enjoy:
4- For window phone 7, there is a free add-on on VS 2010 for development (although publishing is not free). Is there any free development toolkit & emulator(handheld emulator indeed)?
You can use VS 2008, but AFAIK it is not possible at this time to create an emulator for it, since Microsoft has not released the Emulator BSP for WinCE 7.
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).