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.
New release for my M2Mqtt library, MQTT client available for any platform based on .Net Framework (from the desktop to the micro via the compact), now at version 2.4.0.0 and as always is available on CodePlex and Nuget. Bug Fix : message identifier no longer cross-broker This time the update contains, among other things, an important bug fixes on the message identifier generation for PUBLISH, SUBSCRIBE and UNSUBSCRIBE messages provided by the MQTT protocol. In previous versions, the generation of this identifier was encapsulated in the base class of the hierarchy of messages, the MqttMsgBase, highlighting the anomaly of a message identifier increasing cross-broker, which was used the same variable (static) for the generation also if the client was instantiated multiple times in our application to connect to multiple different brokers. Obviously, the protocol provides that the identifier is bound to the client-broker pair, namely that it is unique for each connection to the broker. .Net Compact Framework 3 ...
The Platform Builder build system is quite complicated but at the same time extremely powerful. In order to save valuable time during the compilation of our operating system image, it is necessary to know it in details so that we can avoid unnecessary operations. In addition, there are a number of "tricks" that allow us to make it much faster. Among these, there is the possibility to leverage the compilation on more "core" of our CPU, whereas all modern PCs have now from 2 "core" up. The key of this possibility is the environment variable BUILD_MULTIPROCESSOR, whose meaning can be interpreted in the wrong way if you do not carefully read the documentation. Mistakenly, you might think that setting it to 0, the compilation on more "core" is disabled and vice versa activated by setting it to 1. It is not so! Referring to the documentation on MSDN,, if you set the value to 0 you will let the system to automatically detect the number of "core" of the CPU and use all for the compilation by creating an appropriate ...
After hearing about it for months, finally Windows Embedded Compact 2013 has arrived! The successor to Windows Embedded Compact 7 promises a number of improvements that I report below: General improvements related to the core; Improved performance of the file system (which in my opinion was one of the weaknesses of previous versions); Otimization of the boot which has a duration of a few seconds, possibly with a UI and a number of drivers that are already active; Built-in support for Wi-Fi, cellular and Bluetooth; Obviously, the operating system supports x86 and ARM architectures and the development environment is fully integrated with Visual Studio 2012, and is guaranteed to coexist side-by-side as an environment previously installed Visual Studio 2008 (WCE7) or Visual Studio 2005 (WCE6). In order to begin to enjoy the new features, you can download it at the following link and can be very useful to follow the two webinars by Douglas Boling on 18 and 25 June: Windows Embedded Comp ...
Today I have seen a Microsoft webcast held by Douglas Boling, author of numerous books on Windows CE, and the main topic of the new Windows Embedded Compact 2013, to be released on the market is imminent. There are a lot of news, especially in terms of performance of the operating system and available development tools. The basis of the system will be Windows CE 8 that has inherited the best of Windows Phone 8 and as always will be "modular" through his extensive catalog. The improvement in performance is closely linked to the file system that guarantees an increase in the speed of loading applications and a reduced read access time. In addition, it has been introduced its "snapshot boot" that guarantees a boot time very low in the case of cold start. As far as the development environment, Platform Builder 2013 "hosted" in Visual Studio 2012 with all the improvements arising therefrom; is interesting to observe that it is possible a side-by-side installation with Platform Builder 7. The development of nat ...
Finally some more news on the future of the Microsoft Windows Embedded products with its Road Map.
As far as Windows Embedded Compact to wait until Q2 of 2013 with new assets relating to integration in Visual Studio 2012, C + + 11 and. NET Compact Framework 3.9.
Core Connectivity is often used during development and not in the field, may be useful to avoid additional step needed to disable the safety mechanism...
After abandoning support for the development of smart devices with the. Net Compact Framework in Visual Studio 2010, Microsoft seems to be back on his feet. In fact, Visual Studio 2012 will return to support it, especially in view of the release of Windows Embedded Compact v.Next. In September, some news will be announced about the roadmap of the. Net Compact Framework. This information can be read on the Microsoft Connect site at the following link for an open request by a developer who wondered why in Visual Studio 2010 there wasn’t support for the development of Windows CE. Net Compact Framework. An official voice of the Microsoft responded well ... Hi folks, In the first quarter of 2013, we plan to provide tooling for Visual Studio 2012 to create apps for Windows Embedded Compact v.Next. We’ll be announcing more details in September, including the roadmap for .NET CF. You can find more details this Fall in the Windows Embedded Compact website at http://www.windowsembedded.com. thanks, ...