有一些这两个版本的.NET之间的运行时间差兼容code。

There are a number of run-time differences in compatible code between these two versions of .NET.

下面是一个差异列表至今：

Here is a list of differences so far:

Graphics.DrawRectangle - 相差1像素 Graphics.DrawString - 失去了自动换行，如果使用既StringAlignments设定为中央一的StringFormat 。 在大多数文件操作 - 紧凑型框架需要一个完整的路径 The一个插座BeginAccept 在状态 （在WinCE的5最少），你不能使用的插座与超时同步发送数据（没有是好的，但你的风险挂起） 位图（所有图片的派生类真的）行为不同其资源的清理。 - ctacke 的默认字体标签和树视图中的CF是大 - Darwyn 当标签在CF禁用它只是显示为灰色（完整的.NET framewark概述了另一种颜色的文本） - Darwyn 在大会路径从System.Reflection.Assembly.GetExecutingAssembly（）在桌面上的不同格式的GetName（）返回codeBase的 - 。Qwertie Graphics.DrawRectangle - differs by 1 pixel Graphics.DrawString - Loses the line wrap if used with a StringFormat with both StringAlignments set to Center. Most file operations - compact framework needs a full path The status of a socket after BeginAccept (In WinCE 5 at least) you cannot use a socket to send data synchronously with a timeout (without is okay but you risk hangs) Bitmaps (all Image-derived classes really) behave differently in how their resources are cleaned up. - ctacke The default font for labels and treeviews in the CF was larger - Darwyn When a label is disabled in CF it is just grayed out (the full .net framewark outlines the text with another color) - Darwyn Assembly paths are returned in a different format on the desktop from System.Reflection.Assembly.GetExecutingAssembly().GetName().CodeBase - Qwertie

难道我们也有更多的补充？

Do we also have any more to add?

推荐答案

根据你在找什么还有的的.NET Compact Framework和.NET框架 MSDN上的文章之间的差异。

Depending on what you are looking for there is a Differences between .NET Compact Framework and .NET Framework article on MSDN.