NET managed code that was intended to run as a service, which also allowed software rendering to run on the standard VGA driver.Īfter development of Longhorn was reset, the Desktop Window Manager utilized from the pre-reset builds were fully scrapped for a new, stabler native implementation that could now truly render the Aero theme as intended. It would be heavily rewritten for build 4088 to build 4093 in. The original composition engine would be overhauled throughout Milestone 7 of the Longhorn project, intended to now run the true Windows Aero theme when enabled, although the available builds in this milestone only had basic DCE effects which resembled that of Aero. The bug wasn't fixed until build 4038, which was the first M6 build to have a working render DCE window frames.ĭesktop Window Manager However, builds 4029 through 4033 have a bug in the DCE which causes it to not enable the Direct3D shaders (which DCE window frames rely on). Also during Milestone 5, the Desktop Compositing Engine was reworked to enable DCE window frames, which would be the forerunner to the Windows Aero theme. Despite these animations, other labs used only window transparency effects. Throughout Milestone 5, Lab06 builds such as build 4015 and build 4018 were known to have additional DCE effects, including graphical animations and flapping windows while dragging. Starting from build 3706 through build 4005, a new twirling effect when minimizing or closing windows is added, and a user interface was included to allow the user to enable DCE on boot or via dynamic control. The Desktop Compositing Engine is first present starting with build 3683, but in a buggy state that only renders window transparency. 2 Enabling the Desktop Compositing Engine.

Window manager dwm