When you create an installer for a .NET Windows Service project, a custom class derived from System.Configuration.Install.Installer will be created. This class, when instantiated, will add to its list of Installers two aggregate instances: a System.ServiceProcess.ServiceProcessInstaller and a System.ServiceProcess.ServiceInstaller. Both inherit also from Installer, through the System.Configuration.Install.ComponentInstaller intermediate base class. Here below is the whole code of the custom class, in a simplified view.

Assume you created some widgets as Web Controls for your ASP.NET application, and you want to store information about their name and path somewhere in the Web.config file, to dynamically load them by LoadControl at runtime. Web.config files organize a map to such groups of information in sections and section groups. Under the root configuration node, look for a configSections node. If none is already created, add one. configSections contains a hierarchy of sectionGroup and section nodes. sectionGroup nodes can contain section nodes or other embedded sectionGroup nodes. These nodes must be handled in your program by custom classes derived from ConfigurationSectionGroup and ConfigurationSection, all accessible through the current Configuration file. The main .NET namespace you have to look at and include as reference in your source file is System.Configuration.

The guys from Adobe Systems created one large poster with class diagrams for the ActionScript 3.0 API. While some people may find it difficult to print, we offer here below smaller Model Xtractor class diagrams reflecting those found in the original poster. Our ActionScript class diagrams are also interactive: click on the thumbnail to go to the diagram page, from which you can customize it in the online editor, view it at its original size or get a smaller PDF to print it. For all these diagrams we chose a simple monochrome theme, with no shape icons and no category folders for the shape items. Of course, you can change all this in the diagram editor. You can even clone each of the diagrams below and expand shape items to expose more associations between the ActionScript classes.

The guys from Adobe Systems created one large poster with class diagrams for the Flex 2 Framework API. While some people may find it difficult to print, we offer here below smaller Model Xtractor class diagrams reflecting those found in the original poster. Our Flex class diagrams are also interactive: click on the thumbnail to go to the diagram page, from which you can customize it in the online editor, view it at its original size or get a smaller PDF to print it. For all these diagrams we chose a simple monochrome theme, with no shape icons and no category folders for the shape items. Of course, you can change all this in the diagram editor. You can even clone each of the diagrams below and expand shape items to expose more associations between the Flex classes.

It’s well known that most AJAX web services using either XML or JSON have the ability to send actual data with chunks of metadata, as XML tags, XML attribute names, or property names. This article shows the impact of sending back large amounts of data with metadata, and what can be done to avoid doubling or tripling the transfer bandwidth at the end of the month. We created an ASMX web service with three methods: one returning a dataset as an XML string, the second using JSON, and finally the optimal solution, with JSON as well, but without any metadata. The client side is a simple HTML page, that asynchronously starts three AJAX requests to our web service, using MooTools. Received raw data is shown, with the number of transferred bytes.