I'm developing a MP3 player for Windows CE using Compact Framework, but my target device does not contains aygshell.dll which, in turn, contains the SndPlaySync function I want to use.
Looking here I downloaded a ZIP contains some of this DLL, but neither of them export this function!
Where can I found the ORIGINAL DLL?
Regards,
Daniele.
Aygshell.dll can be included in a Windows CE 5-6/Windows Embedded Compact 7 OS image but, IIRC, it is not included in the core OS license that is what most of devices carry. If you can modify the image and its licensing, then you can add the DLL to your OS image by just selecting the aygshell component from the OS catalog.
The Windows CE version does not provided 100% of the features supported by the Windows Mobile one, it was originally provided to improve the app compatibility between the two OS.
You are lost. AYGSHELL.DLL is only part of Windows Mobile/Embedded Handheld/PocketPC but NOT on any Windows CE device. The build of Windows CE is totally free to the OEM. They can include/exclude whatever they want. Whereas Windows Mobile is a standardized platform where the OEMs must let there builds ceritify by MS.
You may look around for a windows ce port of ffmpeg/ffplay or similar open-source software. Possibly these will also fail as the device has to provide audio drivers.
Related
I have about 20 app demos, mostly for Windows Mobile but some for Windows CE. They were all created in Visual Studio 2008 for Mobile 6.1, Mobile 6.5, and CE 5.0. They are a mix of C# and VB.NET. I've been asked to update them.
I've done a fair bit of research, and I understand you can't do the standard Visual Studio project conversion, but is there anyway to salvage these projects? Ideally, I need to get them running on the current version of Windows Mobile/CE and compiling in the current Visual Studio. Is there any hope for them?
The latest version of Windows Mobile/CE is WEC 2013, and is supported in VS2012 and later. Note that for .NET CF development you will need an Application Builder SDK from the device vendor.
Whether you will be able to port the applications really depends on what they do.
For instance, one of the main differences between CE 5.0 (and its mobile derivatives that you mention) and WEC 2013 is that in WEC 2013 user mode code can no longer access hardware directly, so if the applications rely on direct hardware access you will need to find or implement device drivers to do this. On a related note, P/Invoke is always a potential cause for concern when porting.
You'll also need to determine if the target device includes all the OS features that are required by the applications. Remember Windows CE / WEC are componentized OS's, and the device vendor might have excluded features from the OS image that the applications need in order to function.
I would like to create a C # program to be inserted into a Falcon X3 (that is a barcod with a touch display with installed windows embedded professional 6.5) but when I've copy the project into device and I've tried to open this file it said that i have to install framework compact 2.0. So I download this file from microsoft but the size is not accepted by device. I read that there is cab file that are supported by this device but i don't find anything about this size to istall windows framework in cab size. I Have a Question, what can i do to make a program for this device?
Is there a direct windows based library that I can use to scan a document in c#?
Or my only option is to use a commercial vendor such as leadtools, dynamsoft etc.
I tried to use the wiaaut.dll and it is not compatible with older windows versions such a s XP.
I don't believe Windows XP included any TWAIN or scanning support built into the OS. TWAIN drivers were always supplied by the scanner vendor. So if you're wanting a no-third-party-libs solution that runs on Windows XP, I think you're out of luck.
i am trying to build the 7zip code, which i can use in my windows mobile project..
does any one know how to build 7zip code and use the same in windows mobile application..
I have looked at the 7zip's website here and to quote what they said '7-Zip works in Windows 7 / Vista / XP / 2008 / 2003 / 2000 / NT / ME / 98. There is a port of the command line version to Linux/Unix.' A quick glance at the source code shows that there is x86 assembly involved to achieve a compression algorithm. This could explain why you could not port it across to Windows Mobile as the processor is not x86.
There is a folder within the source code called `\Asm\x86\7zCrcT8U.asm' so obviously does not target the processor in which Windows Mobile run on.
I did a quick google to see if there is indeed a version that is suitable for the Windows Mobile device. But, this could be the one you're looking for?
Hope this helps,
Best regards,
Tom.
7-zip doesn't work on windows mobile check the main page
If you need to get the algorithm to work under another OS (or processor architecture) than you should take a look into the LZMA SDK. Here you got the algorithm to en- or decode a 7zip file in C, C++, C# or Java.
With these you should be able to create a library for the ARM. And if you make a little more investigations into the sources from 7zip itself you should be capable to link these to parts together.
I have been trying to implement the autocomplete functionality mentioned
here.
The problem is I am developing on a windows xp machine and I cant seem to find the right dlls used to develop this feature.
Using vista for development is not an option, but the production environment is on a Vista Tablet PC. I have downloaded and installed the Tablet PC SDK version 1.7 to no avail (still cant find the libraries).
The implementation seems to use COM libraries. The examples are all written in C++ and I am developing in .NET.
Has anyone ever successfully implemented this feature?
If so, how did you go about doing it?
Any help will be appreciated
Here is an image showing what I am trying to achieve
alt text http://i.msdn.microsoft.com/ms695043.ba59a513-e538-4092-89a6-6d691424dc3d%28en-us,VS.85%29.jpg
There is no need to call the DLLs directly. As long as your solution is based on .NET Framework 3.0 or above you just need to enable AutoComplete mode on the specific textbox. Deploying your solution to Vista should enable the functionality.
However, one caveat is that the autocomplete integration is for Vista and above only. You will therefore be unable to debug this aspect of your project on an XP machine - you'll have to remotely debug on your Vista Tablet PC. The Tablet PC SDK does not include down-level compatibility for this option on XP as it's baked into the Vista OS.
I hope this helps.