We are pleased to present below all posts archived in 'March 2014'. If you still can't find what you are looking for, try using the search box.
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 ...
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 ...
Topics:
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 ...
Now Non Beta, have finished testing
In Beta the moment.
Re: SurfPad: Index
this is a good post that you have written you can add more about the outlook or some other technology...
-- Configure Outlook 2016
Re: Azure Sphere - Hands on!!
Cool
-- David Jones
Re: Windows 10 IoT Core: Shutdown and Reboot the Raspberry Pi
Bruce, I noticed that you are sending a REST web request for controlling the pi. I looked online a for...
-- Waleed Elmandouh
Re: Strange HP Laptop Keyboard Fix–It worked for me.
Eh its happened again! Yes [Fn] and [ctrl] keys are swapped. So time to shutdown and remove the battery...
Re: Win 10 IoT-Core - Raspberry Pi3 Bluetooth Driver Issue: Workaround
Thank you for the workaround. I just tried it on my Raspberry Pi 3 running Win 10 IoT. It solved the...
-- Paul
When the BLE dongle is inserted it shows up on the default startup app main page as two entries: USB...
The above "comment" is the Device tree on Device Portal-Devices for the Bluetooth Driver/s with the ...
>HTREE\ROOT\0 >ACPI ARM-based PC >Microsoft ACPI-Compiant System ...
Re: Bluetooth Low Energy on Windows 10 Creators Edition and a RPi3 issue.
FYI: On RPI2 ========== When my USB BLE Dongle is plugged in I get two entries on the main page for the...