We are pleased to present below all posts archived in 'July 2012'. If you still can't find what you are looking for, try using the search box.
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...
Read the rest of entry »
It’s just released the .Net Micro Framework 4.2 developed as open source on CodePlex. Among the key changes : support for WinUSB driver; Analog Output; support for GCC compiler into Porting Kit; performance improvements for file system; wear leveling for FLASH memory; performance improvements for Microbooter and TouchScreen; Have also been solved a series of issues open on CodePlex: - Work Item: 1590 - Decrease boot time - Work Item: 1636 - File.Exists returns true for unexisting file - Work Item: 1656 - Problems with bad blocks handling in Wear Leveling Driver - Work Item: 1701 - StreamReader.cs – IndexOutOfRangeException - Work Item: 1109 - FAT32 File System issue with filenames - Work Item: 1721 - VolumeInfo.Format() locks volume. - Work Item: 1633 - SerialPort.Read's behaviour is different from .Net - Work Item: 1580 - Negative array index issue - Work Item: 1585 - Issue in Microbooter prevents usage in Cortex M3 STM32 port - Work Item: 15 ...
When we decide to develop an application, such as for WP7, using the MVVM pattern but without adopting an available framework (see MVVMLight, Caliburn Micro, ...) we can expect to have to solve some problems for guarantee decoupling between the UI and presentation and business logic. One of these problems can be for example the need to display a MessageBox, a component of the IU, starting from a method of ViewModel corresponding to the page in which we stand. This problem can be solved by implementing a service that will be "injected" into the ViewModel and that task will be to display the MessageBox on request. Because we must ensure that there isn’t strict dependence between the ViewModel and the implementation of the service, we must think in terms of interfaces. We can define an interface for that service in order to give the possibility to implement it from time to time in a different way, in our case we realize that the implementation will make use of the MessageBox from which we take a starting p ...
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, ...
View this page in another language:
