Also this time an update arrives on time for my M2Mqtt library now reached to version 3.1.0.0 ! The main updates concerning better management of QoS Level 2 , some client properties exposed to the outside but especially the fact that it assessed and added some requests that I received by users that obviously thank you ! Also, in some parts of the source code you will see a compilation directive that is conditional on the definition of the symbol BROKER ... why ? I standardized the library code of M2Mqtt with the code of a MQTT broker that I am developing and which will shortly be released in beta version. Its name is GnatMQ and the project is already published online on CodePlex and then open source. Please note that currently it is still a version in development and not completely stable but the release is imminent ! In addition to updating the project on CodePlex , I updated its package on Nuget ( which has now passed 1000 downloads ! ), the code in the Microsoft Gallery and the project M2Mqtt4CE to in ...

Read the rest of entry »

Now same version as in Compact13Tools:

• Compact13Tools includes Compact13Minshell as one of its subcomponents.

This version also sorts the menu.

Read the rest of entry »

Those who follow my blog know that the publisher Packt Publishing was a sponsor of the Microsoft Embedded Conference 2014 in Naples on February 15th.

I want to speak about an interesting promotion that is taking these days to celebrate the 2,000 titles and that is to purchase a book to receive another for free !

At the following link you can find all the information on this incredible offer !

Hey, I’m excited! I hope you are too. I’ve cracked the code for building C# apps directly with the OS build. That is, as an OS Subproject of a Windows Embedded Compact OS project the Managed Code project can be built and run as with Native Code apps. No SDK needed! No second instance of Visual Studio. There are actually a few ways for doing this but shouldn't we be able to do it like native code subprojects.

Topics:

• The Compact Framework
• CE.NET
• Corecon and SDK app development
• Managed Code apps in the OS Build
• Partial Solutions for so doing

Read the rest of entry »

Updated list of Windows Embedded Compact/CE on Codeplex.

Last updated: 21/03/2014

Read the rest of entry »

Topics:

• Announcement:: CESerialTerm
  • A Simple Serial Terminal for Compact 2013/7
• Updates in Compact13Tools Version 4.0
  • Includes a Windows style Start Menu
• A Deep Dive in Compact13Tools and MinShell
• The new Start Menu

Read the rest of entry »

  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 ...

Read the rest of entry »

  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 ...

Read the rest of entry »

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 ...

Read the rest of entry »

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!