.NET Framework正式版已知Bug列表

Release Information for the Microsoft .NET Framework SDK

列表-魔域2.0正式版bug">
-+Additional Resources

  • Release Information for the Microsoft .NET Framework SDK

Legal Information
Unless otherwise noted, the example companies, organizations, products, people and events depicted herein are fictitious and no association with any real company, organization, product, person or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. 1999 - 2001 Microsoft Corporation. All rights reserved.
Access 2000, Active Accessibility, Active Directory, ActiveX, Authenticode, BizTalk, ClearType, CodeView, DataTips, DirectDraw, DirectMusic, DirectX, Exchange Server, FrontPage, IntelliMirror, IntelliMouse Explorer, IntelliSense, Internet Explorer, Microsoft, Microsoft Press, Money, MSDN Library, MS-DOS, MSN, MSN Hotmail, Natural, OpenType, Outlook, PowerPoint, SQL Server, Systems Management Server, Visual Basic, Visual Basic .NET, Visual Basic Scripting Edition (VBScript), Visual C# .NET, Visual C++ .NET, Visual FoxPro, Visual InterDev, Visual Studio, Visual Studio .NET, WebTV, Where do you want to go today?, Win32, Win32s, Windows, Windows 95, Windows 98, Windows 2000, Windows Millennium Edition, Windows .NET server family, Windows NT, and Windows XP are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.

Release Information for the Microsoft .NET Framework SDKThis document includes release information for the Microsoft .NET Framework SDK.   
NOTE: For the most up-to-date information on setup issues, check the Online Readme.
Contents of this document:

  • Release Ship Vehicles
  • System Requirements
  • Getting Started with the .NET Framework SDK
  • Installation Instructions
  • Setup Known Issues
  • Localization Information
  • Product Feedback
  • Security Guidelines
  • Known Issues

Release Ship Vehicles
This release of the .NET Framework and .NET Framework SDK is provided in Microsoft Visual Studio. NET and is also available for Web download from here.
System RequirementsThe .NET Framework SDK is supported on the following platforms with a minimum of Microsoft Internet Explorer 5.01 (Internet Explorer 6.0 is available on the installation CD):

  • Microsoft Windows 2000 with the latest Windows service pack and critical updates available from http://www.microsoft.com/security
  • Microsoft Windows XP
  • Microsoft Windows NT 4.0
  • Microsoft Windows Millennium Edition (Windows Me) and Windows 98.
    These platforms are only supported during run time. Although the SDK will not run on these platforms, you can build applications with the .NET Framework that will run on these platforms.

The .NET Framework has the following minimum system requirements:

  • Client
    • Processor: Intel Pentium class, 90 MHz or higher
    • RAM: 32 MB (96 MB or higher recommended)
    • Hard disk space required for install: 160MB
    • Hard disk space required: 70MB
    • Video: 800x600, 256 colors  
  • Server
    • Processor: Intel Pentium class, 133 MHz or higher
    • RAM: 128 MB (256 MB or higher recommended)
    • Hard disk space required to install: 600 MB
    • Hard disk space required: 370 MB
    • Video: 800x600, 256 colors  

Platform-specific pre-installation requirements are as follows:

  • Windows 2000 and Windows XP
    • Internet Information Services (IIS)
      To access the features of ASP.NET, IIS with the latest security updates must be installed prior to installing the .NET Framework and .NET Framework SDK. If IIS is not present on the computer when the .NET Framework is installed, ASP.NET will fail to register correctly and ASP.NET applications will not run. If IIS is installed after the .NET Framework, you must manually register the Aspnet_isapi.dll file using Regsvr32.exe.
  • Windows NT 4.0
    • Service Pack 6a

Getting Started with the .NET Framework SDK
The introductory page for the .NET Framework SDK is called Starthere.htm and is available in the root directory of the installed SDK. This page includes links to technical programming information, sample code, development tools, utilities, and everything you need to develop applications using the Microsoft .NET Framework.
For Knowledge Base articles and other supplementary information, including information about new .NET Framework classes and members that are not listed in the .NET Framework SDK documentation, see the .NET Framework Addendum.
Installation Instructions
Before installing the .NET Framework SDK, take the following steps:

  • Review the setup issues detailed below and always check the .NET Framework Security Web site for the latest information and updates.
  • Uninstall any previous versions of the .NET Framework SDK. A file listing the API changes from Beta 2 to the version 1 release, called APIChangesBeta2toRTM.htm, is available for users of the Beta 2 release of the SDK. This file is located here.
  • Applications created with any previous version of either the .NET Framework or Visual Studio .NET must be recompiled with this release.
  • All Platforms:
    • Make sure that Microsoft Internet Explorer 5.01 or later is installed prior to running the .NET Framework SDK setup. (Internet Explorer 6.0 is available on the installation CD.) Click here for the latest version of Internet Explorer.
    • Make sure that MDAC is installed prior to running the .NET Framework SDK setup. MDAC 2.6 is required, but MDAC 2.7 is recommended. (MDAC 2.7 is available on the installation CD.)

Setup Known IssuesRepairing the .NET Framework after operating system upgrade
ISSUE:
Upgrading the operating system after installing the .NET Framework requires the .NET Framework to be repaired for performance.
WORKAROUND:
In Control Panel, double-click Add or Remove Programs. Click Microsoft .NET Framework SDK and choose the Click here for support information link. This is a link to repair.htm, which is installed in the version directory for the .NET Framework.
Repair information is incorrectly described for the .NET Framework SDK
ISSUE:
The repair.htm pointed to by the SDK refers to the redist executable and not the .NET Framework SDK setup executable.
WORKAROUND:
To repair the SDK, use the following command line:
n:\\setup.exe /t:%temp% /c:"msiexec.exe /fvecms %temp%\netfxsdk.msi"
Internal Error 1935 during install when Beta 2 was previously on the machine
ISSUE:
After uninstalling the Beta 2 release, if mscoree.dll was not removed, a 1935 error will occur during the install of the version 1 build.
WORKAROUND:

  1. Click Run on the Start menu.
  2. Type the following and click OK:
    %windir%\system32
  3. Delete the file mscoree.dll from the System32 directory.

Installing the .NET Framework on Windows .NET Server Beta 3 systems breaks the version installed with the operating system
ISSUE:
Windows .NET Server Beta 3 includes version v1.0.3215 of the .NET Framework. Installing a later version of the .NET Framework breaks the version that was installed with the operating system. You can run and use the later version that was installed, but do not try to use the v1.0.3215 version, even after uninstalling the later version.
Locales not supported in version 1 of the .NET Framework
ISSUE:
Version 1 of the .NET Framework has known issues for the Turkish and Azeri locales. Locale-aware comparisons are performed in locations where locale-insensitive comparisons are more appropriate. For example, using the Turkish locale, the file name “win.ini” does not compare as equal to “WIN.INI”, due to Turkish-specific rules for comparison. In contrast, using an invariant locale for comparing file names enables “win.ini” to equal “WIN.INI”. This affects basic operations such as file comparisons, path comparisons, running ASP.NET applications, and the evaluation of error messages.
Given these issues, version 1 of .NET Framework is not supported on Turkish and Azeri locales. This means:

  1. When running .NET Framework applications, Thread.CurrentThread.CurrentCulture should not be set to these locales.
  2. If an application does not explicitly set ThreadCulture, the thread’s CurrentCulture is set by default to the locale specified in Control Panel/Regional Options. (On some systems, this option is called Regional and Language Options.) Consequently, applications without an explicitly set locale should not be run on machines with the locale set to Turkish or Azeri.

WORKAROUND:
Locale-aware comparisons in these affected locales are still supported. To achieve this, take the following steps:

  1. Set the application’s main locale to invariant, using either of the following techniques:
    1. For Windows Forms or console applications:
      1. In an application with full or high trust, add the following line of code:
           Thread.CurrentThread.CurrentCulture = CultureInfo.InvariantCulture
      2. Or, set the locale in Control Panel/Regional Options to en-US. (On some systems, this option is English (United States).)
    2. For an ASP.NET or Web Services application, set the server’s system account locale to en-US.
  2. Pass the preferred locale as part of an API call. For example, in a Windows Forms application using C#:
       DateTime dt = DateTime.Now ;
       CultureInfo ci ;
       ci = new CultureInfo("tr-TR") ;
       this.textBox1.Text= dt.ToString("D", ci) ;
    The text box provides the long date format appropriate for the Turkish locale.

Updates: If there is updated information on this issue, it will be posted to http://go.microsoft.com/fwlink/?LinkId=5263.
Process and request identity in ASP.NET
ISSUE:
In its default installation on Windows 2000 and Windows XP, ASP.NET runs Web application code in a worker process. The identity of this process defaults to an unprivileged local account called the ASPNET account.
In Beta releases of ASP.NET, the process identity was System, a powerful administrative account with many privileges on the machine. To provide a less privileged default installation, the weaker account is now used and is suitable for use in many Web applications.
However, in some cases, ASP.NET applications developed with Beta versions of ASP.NET may require changes to work with the new process identity. For more details regarding this change, please review the ASP.NET documentation on http://go.microsoft.com/fwlink/?LinkId=5828.

Localization Information
The .NET Framework will be available in English, German, Japanese, French, Spanish, Italian, Simplified Chinese, Traditional Chinese, and Korean. These versions are all available through Visual Studio installations. Language versions of the .NET Framework will also be downloadable from http://www.microsoft.com/downloads.
Note: The difference between the English and localized versions is the translation of localizable resources, such as UI and error messages. Core functionality is the same in each version and all language versions can be used to develop international applications.
Product Feedback

Newsgroups

Please use the Microsoft .NET Framework newsgroups for technical questions about the Microsoft .NET Framework SDK.

Product Support

Getting Help from Microsoft Product Support Services
For information about contacting Microsoft technical support for the .NET Framework SDK, click here.

Microsoft Product Support Services
For more information and resources, see Microsoft Product Support Services.

Providing Feedback

Product Feedback
Your feedback on the .NET Framework SDK is valuable to us. We appreciate your opinions and suggestions on the software, tools, samples, and documentation. We are working hard to make sure that the .NET Framework technologies and the SDK enable you to build great applications. Please send us your comments and suggestions(netfwsdk@microsoft.com?subject=.NET Framework SDK Feedback).
Documentation Feedback
To provide feedback about the documentation, send e-mail to netfwsdk@microsoft.com(netfwsdk@microsoft.com?subject=Documentation and Samples Feedback). There is a link to this e-mail address on each page of the .NET Framework SDK documentation. The e-mail address should be used only for documentation issues.

时间: 2024-12-11 12:28:05

.NET Framework正式版已知Bug列表的相关文章

iOS9.1 Beta1更新了什么 iOS9.1 Beta1已知Bug介绍

iOS9.1 Beta1更新了什么? 1.全新emoji表情 这应该是iOS9.1给用户带来的能够感受到的最大变化了,由于已经支持Unicode8,iOS9.1带来了超过80多个全新的emoji表情符号,包括邪恶的"竖中指"符号,这在Win10中已经早就有了,除此之外新增的表情符号包括墨西哥taco(鸡肉卷).玉米煎饼.奶酪块.热狗等. 2.全新的3D Touch.Live Photos API 虽然该功能的添加主要是针对开发者的,用户暂时感受不到新3D Touch.Live Phot

iOS 8.1.1已知BUG汇总:WiFi浏览器续航纷纷中招

苹果公司一年一更新系统的习惯对于果粉来说已经是习以为常了.每年当苹果发布全新的设备时,苹果的iOS系统也会随之更新,而今年苹果发布了全新的iPhone 6和iPhone 6 Plus,iOS系统也来到了最新的iOS 8(目前最新的版本是iOS 8.1.1),但是全新的iOS 8系统对用户升级来说却存在一些令人苦恼的问题.iOS 8系统已知BUG汇总首先就是升级所需的空间,一般来说iOS系统在升级时会提示更新文件的大小,此次iOS 8系统同样提示用户更新的容量大小在1GB左右,但实际上却需要用户的

iOS 8.1已知BUG汇总 体验新版本需谨慎

苹果公司一年一更新系统的习惯对于果粉来说已经是习以为常了.每年当苹果发布全新的设备时,苹果的iOS系统也会随之更新,而今年苹果发布了全新的 iPhone 6和iPhone 6 Plus,iOS系统也来到了最新的iOS 8(目前最新的版本是iOS 8.1.1),但是全新的iOS 8系统对用户升级来说却存在一些令人苦恼的问题.iOS 8系统已知BUG汇总首先就是升级所需的空间,一般来说iOS系统在升级时会提示更新文件的大小,此次iOS 8系统同样提示用户更新的容量大小在1GB左右,但实际上却需要用户

程序员的常见“谎话”:对,这是一个已知 Bug

简评:面对程序员,特别是当你是以测试人员或者产品经理的身份面对程序员时,他们往往会在出现问题的时候找一些小借口,其实大家都是一样,最容易原谅的就是自己,程序员也是的,所以你下次如果和程序员同学沟通时听到下面的这些话一定不要拆穿他们咯,给点面子,让程序员生活更美好,笑哭ing. 00. 我以后再给代码写注释和文档.(绝对是最大的谎言) 01. 这只是个临时方案,不会用在实际版本中. 02. 搞定了!只剩一些小事要处理. 03. 那个简单,几天就搞定了. 04. TODO 05. 就改一行代码,不会

iOS8系统Bug_iOS8已知Bug整理与bug解决方法

1.App Store开启速度慢 升级之后,身边的很多朋友都反映App Store开启速度慢了很多,打开就显示一片空白,甚至有一部分人根本打不开.可是我们使用的应用大部分都要从App Store中下载,这也给给用户带来了不小的麻烦. App Store无法开启 解决方法并不难,打开设置-无线局域网-DNS,接着将DNS码改为8.8.8.8即可恢复正常.成功之后再将DNS码换回去就大功告成了,如 果您忘记保存原始的DNS码也没关系,只要在设置中选择重置网络就能自动恢复初始状态,只不过之前记录的Wi

Windows7未上市正式版已惨遭破解

7月30日消息,据国外媒体报道,尽管Windows 7尚未面向公众发售,但日前已经惨遭破解. 该激活方式为OEM模拟激活,激活文件来自联想OEM DVD .ISO里面的文件,包括slic.证书和序列号.已经有Windows爱好者将破解过程做成CMD脚本, 一键安装,完美激活. 对于微软而言,这并不是一件小事,它表明了像微软这样的大企业在开发新产品时所担负的巨大风险.当然,Windows被破解几乎是不可避免的.有趣的是,产品尚未正式推出就惨遭破解. 微软7月22日宣布,Windows 7 RTM已

.Net正式版中的一些Bug及其解决方案

解决 .Net正式版中的一些Bug及其解决方案 (原创) 作者: 飞刀     (1)Session的问题 问题: 在我的Windows.Net 3604 + .Net Framework正式版的编程环境中,.Net下的Session总是有问题,比如我在A程序下设置了一个Session字典,这个Session将会在B程序下读取,现在的情况就是我在B程序读取这个Session时,第一次能够正常读取,但一旦页面被提交(这在Asp.Net编程中是常有的事情),Session就会马上消失,错误报告"Ob

IE8正式版下动易后台编辑器无效的解决方法

微软的IE8正式版已于2009年3月20日正式发布了,也有不少的动易用户升级了自己的浏览器,但在升级后都发现动易的后台编辑器无法使用了,症状就是点击任何功能图标都没有弹出设置窗口,经过GG搜索了一下,终于找到了解决IE8下无法使用编辑器的方法.具体修改方法如下:打开根目录下的editor.asp,找到以下代码if (element.YUSERONCLICK) eval(element.YUSERONCLICK + 'anonymous()');修改为if(navigator.appVersion

WCF技术剖析之十三:序列化过程中的已知类型(Known Type)

DataContractSerializer承载着所有数据契约对象的序列化和反序列化操作.在上面一篇文章(<数据契约(Data Contract)和数据契约序列化器(DataContractSerializer)>)中,我们谈到DataContractSerializer基本的序列化规则:如何控制DataContractSerializer序列化或者反序列化对象的数量:以及如何在序列化后的XML中保存被序列化对象的对象引用结构.在这篇文章中,我们会详细讨论WCF序列化中一个重要的话题:已知类型