<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Model Xtractor</title>
	<atom:link href="http://model-xtractor.com/index.php/feed/" rel="self" type="application/rss+xml" />
	<link>http://model-xtractor.com</link>
	<description>Online Class Diagram Editor</description>
	<lastBuildDate>Fri, 04 Feb 2011 23:20:16 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>Object Model of a Windows Service Installer</title>
		<link>http://model-xtractor.com/index.php/2011/02/object-model-of-a-windows-service-installer/</link>
		<comments>http://model-xtractor.com/index.php/2011/02/object-model-of-a-windows-service-installer/#comments</comments>
		<pubDate>Fri, 04 Feb 2011 23:20:16 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1361</guid>
		<description><![CDATA[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.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2011/02/object-model-of-a-windows-service-installer/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Store Custom Information in Web.Config</title>
		<link>http://model-xtractor.com/index.php/2011/02/store-custom-information-in-web-config/</link>
		<comments>http://model-xtractor.com/index.php/2011/02/store-custom-information-in-web-config/#comments</comments>
		<pubDate>Fri, 04 Feb 2011 20:12:47 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1355</guid>
		<description><![CDATA[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.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2011/02/store-custom-information-in-web-config/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Class Diagrams from the ActionScript 3.0 API Poster</title>
		<link>http://model-xtractor.com/index.php/2010/11/class-diagrams-from-the-actionscript-3-0-api-poster/</link>
		<comments>http://model-xtractor.com/index.php/2010/11/class-diagrams-from-the-actionscript-3-0-api-poster/#comments</comments>
		<pubDate>Thu, 11 Nov 2010 22:36:56 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Posters]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1332</guid>
		<description><![CDATA[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.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/11/class-diagrams-from-the-actionscript-3-0-api-poster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Class Diagrams from the Flex 2 Framework Poster</title>
		<link>http://model-xtractor.com/index.php/2010/11/class-diagrams-flex-2-framework-poster/</link>
		<comments>http://model-xtractor.com/index.php/2010/11/class-diagrams-flex-2-framework-poster/#comments</comments>
		<pubDate>Thu, 11 Nov 2010 09:51:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Posters]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1279</guid>
		<description><![CDATA[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.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/11/class-diagrams-flex-2-framework-poster/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>AJAX XML/JSON Data Serialization</title>
		<link>http://model-xtractor.com/index.php/2010/11/ajax-xml-json-data-serialization/</link>
		<comments>http://model-xtractor.com/index.php/2010/11/ajax-xml-json-data-serialization/#comments</comments>
		<pubDate>Wed, 10 Nov 2010 07:46:22 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1271</guid>
		<description><![CDATA[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.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/11/ajax-xml-json-data-serialization/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>ASP.NET page with XML-HTTP JavaScript AJAX</title>
		<link>http://model-xtractor.com/index.php/2010/11/simple-asp-net-web-page-with-xml-http-javascript-ajax/</link>
		<comments>http://model-xtractor.com/index.php/2010/11/simple-asp-net-web-page-with-xml-http-javascript-ajax/#comments</comments>
		<pubDate>Wed, 10 Nov 2010 02:26:09 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1261</guid>
		<description><![CDATA[The following ASPX page implements on the client side the most simple JavaScript AJAX mechanism for both GET and POST requests, using the XML-HTTP browser-specific object. On the server side, it can respond to the AJAX requests by sending back the current date and time. Everything appears within a simple aspx file, with no code behind. The HTML shows one text entry field and two buttons: GET and POST. On any button action, an AJAX request is sent to the same page, which sends back the value entered in the text field, followed by the current server date and time, information which will be displayed below the form. The server-side script has the C# Page_Load method, which checks whether or not the page must answer to an AJAX request. The client-side script has the specific JavaScript function onSubmit, called on a button click, which issues a GET or POST AJAX request and waits for the response.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/11/simple-asp-net-web-page-with-xml-http-javascript-ajax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>LINQ to XML Practical Examples in C#</title>
		<link>http://model-xtractor.com/index.php/2010/11/linq-to-xml-practical-examples-in-c/</link>
		<comments>http://model-xtractor.com/index.php/2010/11/linq-to-xml-practical-examples-in-c/#comments</comments>
		<pubDate>Thu, 04 Nov 2010 21:11:04 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1251</guid>
		<description><![CDATA[LINQ to XML is a new .NET API to transform, construct, write and read XML data, without having to resort to using additional language syntax like XPath, XSLT, DOM or SAX. LINQ to XML supports writing Query Expressions (XQuery) and can be combined with any of the other LINQ technologies. LINQ to XML types are located within the System.Xml.Linq namespace, in the .NET framework assembly with the same name. Most popular types are XDocument, XElement and XAttribute. Their constructors can take a number of optional nested arguments, to build with the same functional construction a whole hierarchy of nested XML nodes.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/11/linq-to-xml-practical-examples-in-c/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Creating ASMX Web Services</title>
		<link>http://model-xtractor.com/index.php/2010/11/creating-asmx-web-services/</link>
		<comments>http://model-xtractor.com/index.php/2010/11/creating-asmx-web-services/#comments</comments>
		<pubDate>Tue, 02 Nov 2010 20:29:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1246</guid>
		<description><![CDATA[Web services are applications with the ability to exchange messages in a loosely coupled environment using standard protocols such as HTTP, XML, XSD, SOAP, and WSDL. XML Web services enable the building of modular applications within and across companies in heterogeneous environments making them interoperable with a broad variety of implementations, platforms and devices. The SOAP-based XML messages of these applications can have well-defined (structured and typed), or loosely defined parts (using arbitrary XML). The ability of the messages to evolve over time without breaking the protocol is fundamental to the flexibility and robustness of XML Web services as a building block for the future of the Web. The System.Web.Services namespace, from the assembly of the same name, has several classes to create such ASMX web services in ASP.NET.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/11/creating-asmx-web-services/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>.NET Acronyms, .NET Abbreviations</title>
		<link>http://model-xtractor.com/index.php/2010/10/net-acronyms-net-abbreviations/</link>
		<comments>http://model-xtractor.com/index.php/2010/10/net-acronyms-net-abbreviations/#comments</comments>
		<pubDate>Sun, 31 Oct 2010 21:23:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[General]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1242</guid>
		<description><![CDATA[Here are specific acronyms and abbreviations used in Microsoft's .NET, with their short definitions and descriptions. Most .NET acronyms and .NET abbreviations are used for Microsoft's .NET technologies, languages and specifications.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/10/net-acronyms-net-abbreviations/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Background Worker Pattern with BackgroundWorker class</title>
		<link>http://model-xtractor.com/index.php/2010/10/background-worker-pattern-with-backgroundworker-class/</link>
		<comments>http://model-xtractor.com/index.php/2010/10/background-worker-pattern-with-backgroundworker-class/#comments</comments>
		<pubDate>Fri, 29 Oct 2010 21:05:28 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Modeling]]></category>

		<guid isPermaLink="false">http://model-xtractor.com/?p=1237</guid>
		<description><![CDATA[The System.ComponentModel.BackgroundWorker class is offered to implement the background worker pattern. With multithreading operations, you want to be able to asynchronously start a working thread and be able to cancel a long-running task, be notified when the thread completes, and provide an update on the status of the operation. The BackgroundWorker class responds to all these three events: DoWork, RunWorkerCompleted, ProgressChanged.]]></description>
		<wfw:commentRss>http://model-xtractor.com/index.php/2010/10/background-worker-pattern-with-backgroundworker-class/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

