• Tatsache: Shell, das scripting ist, ist ein Muß für irgendein ernst ES admin, der einen Bediener handhabt. Vom Automatisieren der Unterstützungen zur überprüfung der Maschinenbordbücher und zum Halten von Bedienerleistung und der Last in der überprüfung, ist das Scripting a muß.
• Tatsache: Shell, das auf Windows scripting ist, saugt. Monad (Microsoft Energie Shell) versucht, den, aber bis jetzt die Resultate zu regeln werden gemischt.
• Tatsache: Shell, das auf Linux und anderen *nix Betriebssystemen scripting ist, ist leistungsfähig ziemlich Geradeaus, gut dokumentiert, und.

Die meisten Leute nehmen einen Blick an diesen drei Tatsachen und kommen sofort zu einer Zusammenfassung. Unrecht Zusammenfassung: Sie können nicht einen Windows Bediener richtig handhaben, weil er in sich selbst in der scripting Abteilung des Oberteils ermangelt.

Mono ist die Öffnenquellenversion des Rahmens .NET Microsofts. Über es führt die meisten Hinterrahmeneigenschaften, aber leider ein, die Fälle, die auf seinem hübschen kleinen Gesicht beim Versuchen, die Benutzerschnittstelle flach sind anzuzeigen - die ist, was desktop apps ganz sind.

Wein auf der Anderhand ist ein Linux Tor (größte Teile von) der Bibliothek Win32 Microsofts - die Kernabhängigkeiten der Windows Entwicklung Bibliotheken und wichtiger, die Schnittstelle win32 Elemente. Mit Wein können Sie viele traditionelle C++ win32 executables auf Linux, mit bestimmten Beschränkungen laufen lassen.

Größtes monohindernis ist die GUI und .NET Programme, die P/Invoke verwenden, um die gebürtigen nicht-gehandhabten Mono dlls zu benennen win32 - ist ein reines .NET Klima und kann nicht sie anfassen. Aber von der Beschreibung oben, ist das genau 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.