• Fait : Shell scripting est une nécessité pour le tout sérieux IL admin contrôlant un serveur. D'automatiser les protections à vérifier des notations et à maintenir l'exécution de serveur et la charge dans le contrôle, scripting est a doit.
• Fait : Shell scripting sur Windows suce. Le Monad (puissance Shell de Microsoft) essaye de fixer cela, mais jusqu'ici les résultats sont mélangés.
• Fait : Shell scripting sur Linux et d'autres logiciels d'exploitation de *nix est puissant, bien documenté, et tout à fait straight-forward.

La plupart des personnes jettent un coup d'oeil à ces trois faits, et arrivent immédiatement à une conclusion. mal conclusion : vous ne pouvez pas correctement contrôler un serveur de Windows parce qu'il manque en soi dans le département scripting de coquille.

…

Mono est la version d'ouvrir-source du cadre du .NET de Microsoft. Il met en application la plupart des dispositifs principaux de cadre, mais malheureusement, des chutes plates sur son joli petit visage en essayant de montrer l'interface utilisateur - est qui au sujet de ce que les apps d'ordinateur de bureau sont tout.

Vin sur l'autre-main, est un port de Linux (les parties de) de la bibliothèque du Win32 de Microsoft - les dépendances de noyau des bibliothèques de développement de Windows, et d'une manière primordiale, les éléments de l'interface win32. Avec du vin, vous pouvez courir beaucoup d'executables traditionnels de C++ win32 sur Linux, avec certaines limitations.

Le plus grand bloc de trébuchement mono est les programmes de GUI et de .NET qui emploient P/Invoke pour appeler les dlls win32 non-contrôlés indigènes - mono est un environnement pur de .NET, et ne peut pas les manipuler. Mais de la description ci-dessus, c'est exactement 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

…

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.