.Net Micro Framework SDK 2.5 发布

简介:

3月6日,微软.Net Micro Framework SDK 2.5 在MSDN上提供了下载链接(http://www.microsoft.com/downloads/details.aspx?familyid=EB0EF2A6-03E2-402C-89A4-A636BD0080C5&displaylang=en)。

安装最新版本的SDK之前,需要卸载掉原来的老版本。

 

安装后,我初步看了一下,好像大的改动不多,以前我编写的MF程序都可以正常运行,至于新功能嘛,其发布文件上如是说:

===============================================================================
What new in V2.5?
===============================================================================
The V2.5 release includes a optionally installed beta release of the assemblies
for the .NET managed Devices Profile for Web Services (DPWS) stack.
 
Samples demonstrating how to create or use:  
 - hosted services on devices 
 - clients on the desktop and on devices 
 - Discovery and Eventing

The .NET Micro Framework DPWS stack requires TCP/IP (Sockets) to function.
 
Device firmware must be developed with the V2.5 version 
of the .NET Micro Framework Porting Kit in order to include 
the .NET Micro Framework TCP/IP network stack.


===============================================================================
Issues
===============================================================================

-------------------------------------------------------------------------------
Issue:

Calling SocketConnect on a second set of sockets causes an exception in the 
Emulator.

Resolution:
This is a known issue and will be fixed in a subsequent release.

-------------------------------------------------------------------------------
Issue:

If a DispatchTimer is declared on the stack of a method, and the method 
returns, the DispatchTimer object may be garbage collected, even though 
still enabled.

Resolution:
Declare DispatchTimer objects as globals.

-------------------------------------------------------------------------------
Issue:

The EnableDynamicDNS method of the 
Microsoft.SPOT.Net.NetworkInformation.NetworkInterface class is not 
implemented in the .NET Micro Framework TCP/IP stack, and will cause 
an exception if called from a managed application.

Resolution:
Dynamic DNS address assignment is accomplished by enabling DHCP after 
setting the static DNS address to 0.0.0.0.
 
For example, the following code will cause DHCP to assign the DNS addresses:
 
        // set DNS to 0 so DHCP DNS is used
        string[] dns = new string[] { "0.0.0.0", "0.0.0.0" };
        interfaces[0].EnableStaticDns(dns);
        // Enable DHCP
        interfaces[0].EnableDhcp();

When changing the network configuration in a managed application, it is 
necessary to follow these guidelines:
   1) When changing the network configuration from DHCP-enabled to static,
      it is necessary to update the static DNS addresses
   2) When changing the network configuration from static to DHCP-enabled, 
      it is necessary to change the two DNS addresses to 0.0.0.0 so that DHCP 
      will update the DNS addresses. If you want to then replace the 
      DNS addresses provided by DHCP, call EnableStaticDns with the two 
      replacement addresses.
 
-------------------------------------------------------------------------------
Issue:

DHCP behavior on the .NET Micro Framework differs from DHCP on the desktop.
The .NET Micro Framework makes three attempts within 7 seconds to obtain 
a DHCP lease at bootup. If the DHCP server is not found within this time frame,
the framework ceases searching for a DHCP server. This is the intended behavior 
that application developers should be aware of since it differs from all 
versions of the Windows operating system.

Because of the finite number of attempts to find the DHCP server, your device 
may not obtain a DHCP lease if it is not properly connected to the network at
boot time.
 
Resolution:
Connect the device to the network before booting.

-------------------------------------------------------------------------------
Issue:

Deploying multiple times to the iMXS platform in Visual Studio can cause 
deployment errors.

Resolution
A solution to this problem is being investigated for version 3.0. Currently, 
there are multiple workarounds available. Here are a few.
1.  Press F5.
2.  Restart the device.
3.  Check to see if you have multiple devices with the same name.
4.  Restart Visual Studio.

-------------------------------------------------------------------------------
Issue:

There is a known issue when debugging a .NET Micro Framework V2.0 SP1 
application running on the V2.5 firmware. This typically happens when loading 
a resource.  This issue will be resolved in a subsequent release.

Resolution
Use the V2.5 SDK for all application development.

-------------------------------------------------------------------------------
Issue:

Dns.GetHostEntry with an empty input string ("") will return the local 
IP address

Resolution:
This is by design and expected behavior.

-------------------------------------------------------------------------------
Issue:

After deploying an application from Visual Studio, the device is rebooted. In 
some cases, DHCP can cause Visual Studio to time out while waiting for a 
reconnect, preventing Visual Studio from debugging the device.

Resolution:
Add a registry key and value to increase the amount of time Visual Studio will 
wait for a reconnect. The default of 5 seconds may be extended by creating the 
following key and setting its timeout, retries, and override values:

HKCurrentUser\
  Software\
    Microsoft\
      .NetMicroFramework\
        NonVersionSpecific\
          Timing\
            AnyDevice

'timeout' (DWORD): milliseconds to wait before retrying 
    (constrained to 50 < timeout < 60000)
'retries' (DWORD): count of retries to attempt 
    (constrained to 1 < retries < 1000)
'override' (DWORD): if present and non-zero, ignore constraints above, 
    and attempt to apply any valid DWORD values.

If any one of the values provided is out of bounds or malformed, it is 
silently ignored and the default values remain in effect. However, the others 
that are valid are still be applied.

The default values are as in v2 SP1: timeout = 100 for platforms that support 
a soft reboot, 1000 otherwise; retries = 10.

-------------------------------------------------------------------------------
Issue:

Calling a NetworkInterface method that changes the IP address will invalidate
any bound sockets.

Resolution:
If running as a server, re-bind any open sockets after any IP address change.

进一步的详情,等我研究后在说。

 

 








本文转自yefanqiu51CTO博客,原文链接:http://blog.51cto.com/yfsoft/324284,如需转载请自行联系原作者

相关文章
|
Linux 开发工具 git
FreeSWITCH小白入门之freeswitch安装篇
技术小白,今天带领大家一起freeswitch源码编译安装。我的上一篇文章已经搭建好了运行环境(centos7-Minimal),有人会说fs官方不是说在debian8下运行最稳定吗?我只能说,我个人爱好而已!
3133 0
|
存储 网络协议 小程序
软考中级网络工程师备考分享
分享我参与2022年下半年软考网工的心得体会
1516 0
软考中级网络工程师备考分享
|
存储 数据中心 C++
光纤电缆类型:单模与多模光纤电缆
【7月更文挑战第24天】
840 1
光纤电缆类型:单模与多模光纤电缆
|
编解码
视频分辨率和帧率
视频分辨率和帧率
2622 1
|
程序员 编译器 C++
C++中的函数重载(Function Overloading)
C++中的函数重载(Function Overloading)
566 2
|
存储 缓存 监控
微信团队分享:微信后端海量数据查询从1000ms降到100ms的技术实践
针对大数据量带来的查询性能问题,微信团队对数据层查询接口进行了针对性的优化,将平均查询速度从1000ms+优化到了100ms级别。本文为各位分享优化过程,希望对你有用!
252 2
|
分布式计算 监控 数据处理
Spark Streaming的DStream与窗口操作
Spark Streaming的DStream与窗口操作
|
Java 关系型数据库 MySQL
新闻发布|基于JavaWeb实现新闻发布管理系统+论文+PPT(一)
新闻发布|基于JavaWeb实现新闻发布管理系统+论文+PPT
519 0
|
存储 缓存 监控
深入理解线程池:优化多线程任务管理与提升性能
深入理解线程池:优化多线程任务管理与提升性能
1096 0
|
存储 缓存 网络协议
如何“多快好省”地使用阿里云产品实现数据下载加速
阿里云CDN下载加速解决方案旨在通过全球调度中心智能化地将客户端的下载请求精准调度到分布于全球的最优CDN边缘节点,同时依托海量带宽储备及强大的CDN控制逻辑让企业省心省力地为用户带来极速下载体验,助力企业获得更大的市场回报。
1087 1
如何“多快好省”地使用阿里云产品实现数据下载加速