|
|
| 第 42 行： |
第 42 行： |
| SideShow 是 Microsoft Research 的一个项目，构建了后来的 [[Windows 边栏]]，很快就被合并到 Longhorn 项目中，Microsoft 打算将其用作基于 WinFX 构建的新应用程序平台，作为资源管理器进程的一部分托管。 | | SideShow 是 Microsoft Research 的一个项目，构建了后来的 [[Windows 边栏]]，很快就被合并到 Longhorn 项目中，Microsoft 打算将其用作基于 WinFX 构建的新应用程序平台，作为资源管理器进程的一部分托管。 |
|
| |
|
| Many features slated for Blackcomb became part of Longhorn, and employees jumped ship from other parts of the company, turning into a major version rather than the minor version it was initially planned as. After an initially quiet development cycle, the first build to leak publicly was [[Windows Longhorn build 3683|build 3683]], which contained a new theme called [[Plex]], as well as the foundations for Avalon and WinFS.
| | 许多原计划用于 Blackcomb 的功能成为 Longhorn 的一部分，并且员工从公司的其他部门跳槽，变成了主要版本，而不是最初计划的次要版本。在最初平静的开发周期之后，首个公开泄露的版本是 [[Windows Longhorn Build 3683.0.Lab06_N.020923-1821|Build 3683]]，其中包含一个名为 [[Plex]] 的新主题，以及 Avalon 和 WinFS 的基础。 |
|
| |
|
| Starting with build 4000, Microsoft employed a new image-based deployment mechanism for Longhorn, known as WIM, designed to make installs (run from a Windows PE environment) far faster than the CAB-based installs of before. WIM would later be deployed not only for Longhorn and subsequent versions of Windows, but also for special embedded versions of Windows XP including Windows FLP and Windows Embedded POSReady 2009.
| | 从 Build 4000 开始，Microsoft 为 Longhorn 采用了一种新的基于映像的部署机制，称为 WIM，旨在使安装（从 Windows PE 环境运行）比以前基于 CAB 的安装快得多。WIM 后来不仅部署在 Longhorn 和后续版本的 Windows 中，还部署在 Windows XP 的特殊嵌入式版本（包括 Windows FLP 和 Windows Embedded POSReady 2009）中。 |
|
| |
|
| As development slowly progressed, the Longhorn project ended up becoming a largely bloated and unstable piece of vaporware, with team members and high-ranking executives describing the project as a literal "pig"<ref name="fortin_perf">Fortin, Michael. [https://archive.org/details/LHPreReset-PerfChallenges_2004 Longhorn Performance Challenges and Direction], ''Longhorn Kernel Team''. 10 February 2004.</ref><ref name="quentin_winfs">Clark, Quentin. [https://archive.org/download/WalkingCatVideoSlides/RN18499%20WinFS%20Overview%2C%20Customer%20View%20and%20Roadmap%20-%20Quentin%20Clark%20-%202004.pdf WinFS Overview: Customer View and Roadmap], ''Microsoft ECS Talks - WinFS''. 10 February 2004.</ref><ref name="allchin_pig">United States District Court for Iowa. [http://iowa.gotthefacts.org/010807/PLEX_7264.pdf Plaintiff's Exhibit #7264], ''Comes v. Microsoft''. 8 January 2007.</ref> and release dates constantly being pushed back on multiple occasions. Stability issues (e.g.: [[w:memory leak|memory leak]]s and [[Blue screen of death|system crashes]]), organizational management problems (such as lack of team morale<ref name="allchin_pig"/> and an [[Build lab#Whistler and pre-reset Longhorn|unworkable build lab system]]) and [[w:feature creep|feature creep]], additionally compounded by the significant lack of work done to optimize the operating system and the use of relatively new or otherwise unfinished technologies - many system components of which were extended by the .NET Framework, Avalon and [[w:Managed C++|Managed C++]] - increasingly became issues as development progressed, and the project eventually entered [[w:development hell|development hell]].
| | 随着开发的缓慢进行，Longhorn 项目最终成为一个非常臃肿且不稳定的雾件（vaporware），团队成员和高级管理人员将此项目描述为字面意义上的“pig，猪”<ref name="fortin_perf">Fortin, Michael. [https://archive.org/details/LHPreReset-PerfChallenges_2004 Longhorn Performance Challenges and Direction], ''Longhorn Kernel Team''. 10 February 2004.</ref><ref name="quentin_winfs">Clark, Quentin. [https://archive.org/download/WalkingCatVideoSlides/RN18499%20WinFS%20Overview%2C%20Customer%20View%20and%20Roadmap%20-%20Quentin%20Clark%20-%202004.pdf WinFS Overview: Customer View and Roadmap], ''Microsoft ECS Talks - WinFS''. 10 February 2004.</ref><ref name="allchin_pig">United States District Court for Iowa. [http://iowa.gotthefacts.org/010807/PLEX_7264.pdf Plaintiff's Exhibit #7264], ''Comes v. Microsoft''. 8 January 2007.</ref>，发布日期多次被推迟。稳定性问题（例如：内存泄漏和[[蓝屏死机|系统崩溃]]）、组织管理问题（例如缺乏团队士气<ref name="allchin_pig"/>和不可行的[[内部版本实验室#Whistler 和 Longhorn 重置前|内部版本实验室体系]]）以及功能蠕变，此外，由于严重缺乏优化操作系统的工作以及使用相对较新或其他未完成的技术（早熟技术）而变得更加复杂（其中许多系统组件由 .NET Framework 扩展）。Avalon 和 Managed C++ —— 随着开发的进展，问题越来越多，此项目最终进入了开发地狱。 |
|
| |
|
| Due to these problems, only two preview releases were publicly distributed at conferences and to developers: builds [[Windows Longhorn build 4051|4051]] and [[Windows Longhorn build 4074|4074]], released during [[w:Professional Developers Conference|PDC 2003]] and [[w:Windows Hardware Engineering Conference|WinHEC 2004]] (at which point the new Longhorn Display Driver Model was announced) respectively. Around the time of PDC 2003, Win32 was said to be in "maintenance mode" where it was being kept around solely for compatibility with few new APIs exposed to developers; the Longhorn Developer Previews focused solely on managed APIs.
| | 由于这些问题，只有两个预览版本在会议上公开分发给开发人员：Build [[Windows Longhorn Build 4051.0.idx02.031001-1340|4051]] 和 [[Windows Longhorn Build 4074.0.idx02.040425-1535|4074]]，分别在 PDC 2003 和 WinHEC 2004 期间发布（此时宣布了新的 Longhorn 显示驱动程序模型）。在 PDC 2003 左右，传闻 Win32 处于“维护模式”，它被保留下来只是为了与向开发人员公开的少数新 API 兼容；Longhorn Developer Preview 仅专注于托管 API。 |
|
| |
|
| {{multiple image | | {{multiple image |
| 第 61 行： |
第 61 行： |
| }} | | }} |
|
| |
|
| As a last resort, Microsoft started work on refactoring the operating system into a set of components (something which had been planned early on but Microsoft had not made serious progress on), hoping to contain the feature creep in the process. However, the componentization effort derailed the project even more. The last confirmed build prior to the development reset is [[Windows Longhorn build 4093 (main)|build 4093 (main)]], compiled on 19 August 2004, though based on version numbers and build dates from scattered components, it's likely that some build labs and teams continued building parts of the scrapped Longhorn source tree after this time, and some components (such as DWM, which shares a dependency on MIL with Avalon) are likely to have survived the reset unscathed.
| | 作为最后的手段，Microsoft 开始将操作系统重构为一组组件（这很早就计划好了，但 Microsoft 并没有取得重大进展），希望在此过程中遏制功能蠕变。然而，组件化工作使项目更加脱轨。在开发重置之前，最后一次确认的版本是 [[Windows Longhorn Build 4093.0.main.040819-1215|Build 4093.main]]，编译于 2004 年 8 月 19 日，但根据零散组件的版本号和版本编译日期，一些内部版本实验室和团队很可能在此之后继续构建废弃的 Longhorn 源代码树的一部分，并且一些组件（例如 DWM，它与 Avalon 共享对 MIL 的依赖）可能在重置中毫发无损。 |
|
| |
|
| === Development reset === | | === Development reset === |