• 事實： 殼寫電影腳本是當務之急為任何嚴肅它處理服務器的admin。 從自動化備份對檢查日誌和保留服務器表現和裝載在檢查，寫電影腳本是a必須。
• 事實： 寫電影腳本在窗口的殼吮。 Monad (微軟力量殼)試圖固定那，但到目前為止結果是混雜的。
• 事實： 寫電影腳本在Linux和其他*nix操作系統的殼是強有力，有大量文件證明和相當直接的。

多數人看一看在這三個事實和立即得出結論。 錯誤 結論： 因為它固有地在殼寫電影腳本的部門，缺乏您不可能適當地處理窗口服務器。

…

單音 是微軟的.NET框架的打開來源版本。 它實施大多後端框架特點，但不幸地，秋天平在它的相當少許面孔，當試圖顯示是的用戶界面時-什麼桌面apps是所有關於。

酒 在其他手，更加重要地(大部分)微軟的Win32圖書館Linux口岸-窗口發展圖書館的核心附庸，和， win32接口元素。 與酒，您在Linux能跑許多傳統C++ win32 executables，以某些局限。

單音最大的絆腳石是使用P/Invoke叫當地非被處理的win32 dlls -的GUI和.NET節目單音是一個純淨的.NET環境，并且不可能處理他們。 但從上面描述，那是 確切地 what WINE excel at… So can’t we use WINE + Mono to make just about any .NET program run on Linux fresh out of the .NET compiler?

Unfortunately, the answer is no. Back when the Mono project was first starting out, the Mono development team considered using WINE to implement the System.Windows.Forms namespace of the .NET Framework (which is practically 100% native C++ unmanaged win32 code in .NET wrappers). But they made the right choice in deciding to not take the easy way and go that route, leaving the integrity of the Mono project intact and focusing on true cross-platform user interface libraries instead (the GTK# is now the UI Library of choice for cross-platform .NET applications).

…

In this episode of “The Never-Ending Quest for Better Server Performance,” we follow our heroes’ journey through the dangerous and murky woods of PHP opcode caching engines, where they aren’t content with just installing an opcode caching engine, but <gasp> becoming one with it too!

Yep, you heard that right. We’ve just released two new plugins for the WordPress users out there, that take opcode caching to the next level. If you haven’t already installed an opcode caching engine like XCache (our favorite!), eAccelerator, Turck MMcache, Memcached, APC, or PHPA then you really need to do that right now before even continuing this article. Really, what were you waiting for!?

…

For all the Windows-bound PHP users out there, consider yourselves warned: even if you’re running the (supposedly) thread-safe PHP Win32 binary redistribution, you’re still susceptible to PHP Access Violation Errors, race problems, heap corruption, and much worse if you use the popular eAccelerator opcode-caching extension.

We did our testing with the binaries compiled by SiteBuddy using the latest versions of both PHP and eAccelerator. Almost immediately after initiating a stress test on our test servers we experienced the dreaded “PHP Access Violation” error - which brings down the entire IIS Worker Process to its heels.

…

Overview

In my earlier post, I showed how to create a Shell Namespace Extension using the default IShellView implementation (also known as DefView). One thing you might have noticed from the sample is that the Commands Module is void of even the default items such as “Organize” and “Views”.

If you are developing your own Namespace and want to include the default buttons and/or add your own elements to the Commands Module as well, how do you accomplish this? The answer: you must implement the IExplorerCommand, IExplorerCommandProvider and IEnumExplorerCommand interfaces.

Below I describe what each of the interfaces is used for and what you need to do to properly implement them in your code.

IExplorerCommandProvider

After your Namespace is loaded, the Shell will ask your Namespace for an instance of an IExplorerCommandProvider. This interface exposes two methods: GetCommand and GetCommands. The Shell calls the GetCommand method to retrieve a specific IExplorerCommand object that matches the supplied GUID (Each command is identified by a GUID). The GetCommands method is called to retrieve an IEnumExplorerCommand instance. This object enumerates all the IExplorerCommand instances for the namespace.

You Namespace is queried for its implementation of IExplorerCommandProvider via its IShellFolder's implementation of CreateViewObject. The REFIID passed to CreateViewObject will be IID_IExplorerCommandProvider. The Shell will then use this interface

I have recently worked on Windows Sidebar Styler and version 2.0.6 is now available.

Among the improvements is instant application of styles as well as the resizable Windows Sidebar feature. The latter is especially useful when Windows Sidebar is docked on the left. Added are more localizations and Alky for Applications is supported for use in Windows XP or Server 2003.

The new version can be downloaded here.

If you are interested in localizing Windows Sidebar Styler in your native language, or just want to suggest a feature for the next version, please do not hesitate to contact me.