We are pleased to present below all posts tagged with 'Windows CE'. If you still can't find what you are looking for, try using the search box.
We are to the last post of this tutorial that guides us through the creation of a proprietary component (using the M2Mqtt library as an example) for Platform Builder and its inclusion in the Windows Embedded Compact 2013. In this final post we will see how you can use this component in a sample managed application using also debugging. SDK and Application Builder When we build Windows Embedded Compact 2013 image that we have to provide to the software development team that will implement the high-level application for the target device, we must necessarily also make available its SDK. It contains all the header files and static libraries that developers can use to build applications in native code, avoiding the use of the APIs that we have not included in our image. Typically we would not need the SDK with managed applications based on .Net Compact Framework but unfortunately without any SDK installed, Visual Studio 2012 does not make available any templates for applications based on Windows Embedde ...
This is the fourth post of this tutorial that has as its object the development and use of a proprietary component into a Windows Embedded Compact in 2013 operating system image. In the first post, we saw how to sign an assembly compiled for the .Net Compact Framework 3.9 so you can register it into the GAC (Gloabal Assembly Cache) and to do so, we used the M2Mqtt library assembly. In the second post, we have developed a component that is visible in the Platform Builder catalog items and allows to easily include this library with all the settings required for the registration in the GAC. In the third post, we saw how you can deploy your component to any third party and how simple it is to include it in the OS image. At this point, the next step is to prepare the image with some debugging tools for the sample application in the last post. The Core Connectivity framework One of the main features of Windows Embedded Compact from the first releases is that you can debug managed applications (and not) de ...
In the previous post, using the tool CEComponentWiz, we have created a custom component that is visible in the Platform Builder catalog items. We used the assembly of M2Mqtt library compiled for .NET Compact Framework 3.9 and created the corresponding component that I made publicly available on CodePlex under the name M2Mqtt4CE ! M2Mqtt4CE : component description This component can be useful to any OEM that should produce Windows Embedded Compact 2013 operating system image that has a client for MQTT onboard and developed with .Net Compact Framework 3.9. Assuming to be OEM, we can download the M2Mqtt4CE package from CodePlex and extract the contents to the \WINCE800\3rdParty folder (as described in the ReadMe.txt file attached). The main files of the component are the following : M2Mqtt.dll (located in the Resources folder) is the signed assembly of M2Mqtt library that is included in the image and registered in the GAC; M2Mqtt.bib is the BIB file that determines th ...
In this post, I talked about a bug in the current release of Windows Embedded Compact 2013 to which the build system was no longer able to recognize the .Net Framework after the update from 4.5 to 4.5.1 version. In the same post I also described a possible workaround to be able to continue to use Platform Builder with no problems waiting for an official patch from Microsoft.
With the January 2014 update that you can download here ... the bug has been fixed!
If you have used my workaround, you should restore everything as it was before starting from the sources.ce file in C:\WINCE800\public\common\oak\misc (removing the variable _DOTNET40ROOT) and restore the system PATH variable.
After this recovery step ... perform the update and everything will work as always!
In the previous post we saw how to sign an assembly (my M2Mqtt library) to include it directly into the Windows Embedded Compact 2013 operating system image and register it into the GAC (Global Assembly Cache). During this post, we will see how it is possible to make a component for the Platform Builder catalog items through which include our library into the image in a very simple way. How to create a component ? The available solutions When we build an Windows Embedded Compact 2013 operating system image for a target device, there is often the need to add our custom component (an application, a library or any other type of file) to the image itself, without using the Platform Builder catalog items because this component is proprietary and it isn’t in the catalog itself. Unfortunately, in many cases, the simplest solution but also less "elegant" is to copy the files to include in the folder of our OSDesign (operating system solution) and change the corresponding BIB file to set inclusion int ...
With this post, I start a short tutorial on using a proprietary library (developed by us with .NET Compact Framework 3.9) on Windows Embedded Compact 2013, from the signing of the assembly (for registration in the GAC) to a sample application project, through the realization of a component exposed by the Platform Builder (in catalog items) that we can include in the OS image trivially. I will cover : How to sign an assembly; Creating a component for catalog items in Platform Builder; Distribution and inclusion of the component in the OS image; Support for application debugging for the example that will use the component; Development of a sample application; I'll use my M2Mqtt (MQTT Client Library for. Net) project as a reference, assuming that it is the component that we want to include in the image, so that third parties can develop an application that uses it having already onboard on a target device wit ...
On Saturday 15th of February was staged the second edition of Microsoft Embedded Conference which was held at the Holiday Inn in Naples and organized by the DotNetCampania community (I am a member of it), TinyCLR.it and Embedded101, this community that is a reference on Windows Embedded of which, I’m a "board of directors" member since November 2013. Also this year there was a good turnout of attendees even though it was Saturday, because the main topic was the Internet of Things and M2M Communication of which we hear persistently in the last period as the business of the future for the big network. At 8:00, the team was ready for the preparations and organization in order to accommodate very well the attendees and ensure that the event will start on time. As with all events, we started with the keynote of our president Michele Aponte, who presented the community and to whom I have given ...
This time Creg Duncan had to give more than usual explanations to justify the very first constant presence on the Coding4Fun blog!
“Today's Hardware Friday post is another project from our Friend of the Blog, Paolo Patierno (yeah, yeah, I know, it seems like I'm posting his stuff all the time, but hey, it's cool stuff) !”
I'm glad that my "small" open source projects had quite successful and this is the time of uNFC library that implements support for the NXP PN532 NFC chip for all Windows Embedded platforms (from. NET Micro Framework to Windows Embedded 8 passing Windows Embedded Compact).
About this library ... tomorrow it will be featured at the Microsoft Embedded Conference in Naples in a demo on Smart Home & Smart Factory System!
As always .... it is a pleasure to be there!
Today, preparing a Windows Embedded Compact 2013 image for an eBox 3310A and for the demo at Microsoft Embedded Conference in February 2014, the Windows 7 operating system (a virtual machine) decides to upgrade the version of .Net Framework from 4.5 to 4.5.1. Reboot the system and resume the job ... but the build system for Visual Studio 2012 has gone mad and the next attempt to build fails! A warning indicates that the .Net Framework 4.5 is not installed on the system and an obvious fatal error indicates that the compilation can not be done! I have found no official news from Microsoft to fix this problem but I have circumvented the problem in the following way .... First I open the file indicated by the fatal error, ie sources.ce in the path C: \ WINCE800 \ public \ common \ oak \ misc, which reports the error in case the environment variable _DOTNET40ROOT is empty. !IF "$(_DOTNET40ROOT)" == "" ! ERROR Error: Microsoft.NET Framework v4.x must be installed on your machine. ...
It’s well known that Microsoft made a very clear choice regarding the use of a DBMS within embedded products, from smartphones (Windows Phone) to tablets (Surface WinRT) via the devices based on Windows Embedded Compact 2013; this choice has a precise name and it is SQLite ! From WEC7 to WEC2013 : SQL Server Compact removed ! As far as Windows Embedded Compact, the change was made from version 7 to 2013, even removing the "SQL Server Compact" feature within Platform Builder Catalog Items (in the "Core" features related to the SYSGEN_SQLCOMPACT variable) through which it was easy to add support for this DBMS into the operating system image. Also, in the official MSDN documentation of .Net Compact Framework 3.9 it is described the removal of SQL Server Compact support within the framework itself and the use of SQLite is reported as a possible "workaround". At this point, we just have to accept the choice made by Microsoft and explore how you can use SQLite in our embedded systems. SQLite : nati ...