.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,如需转载请自行联系原作者

相关文章
|
API 开发工具 C#
一套基于 .NET Core 开发的支付SDK集 - paylink
一套基于 .NET Core 开发的支付SDK集 - paylink
133 1
|
网络协议 开发工具
.Net Micro Framework SDK 2.5 发布
安装后,我初步看了一下,好像大的改动不多,以前我编写的MF程序都可以正常运行
700 0
.NET Micro Framework V4.2 QFE2新版本简介
.NET Micro Framework V4.2 QFE2最新版改变
782 0
|
Windows 物联网 芯片
.NET Micro Framework常见问题问答
.NET Micro Framework常见问题问答
809 0
.NET Micro Framework 用户程序升级说明
【STM32 .Net MF开发板学习-26】以前的文章示例都是采用VS2008开发的,所以示例要想在新的.NET Micro Framework V4.1开发板上运行,必须用VS2010转换后才可以。
659 0
|
物联网 Windows 内存技术
.Net Micro Framework 快速入门
2009年并入.NET产品组,Digi、Atmel、飞思卡尔等半导体公司都先后为其推出了开发板,该技术可以应用到远程控制、智能家电、教育类机器、医疗电子、零售终端、Sideshow以及汽车电子等行业应用场景
1094 0
|
网络协议
.Net Micro Framework V4.1 beta 发布
新的版本增加了对VS2010开发环境支持,开源TCP/IP协议栈(lwIP),此外还支持OPenSSL及几款SH2/A系列的处理器。
688 0
|
物联网
.NET Micro Framework简介
.NET Micro Framework简介
744 0
|
开发工具 .NET 开发框架