<?xml version="1.0" encoding="iso-8859-1"?>
<rss version="2.0">
  <channel>
    <title>DotNetKicks.com : Stories kicked by mywebblog79</title>
    <description>Stories kicked by mywebblog79</description>
    <link>http://www.dotnetkicks.com/</link>
    <language>en-us</language>
    <copyright>Atweb Publishing Ltd.</copyright>
    <docs>http://backend.userland.com/rss</docs>
    <generator>DotNetKicks.com - .NET links, community driven</generator>
    <ttl>30</ttl>
    <item>
      <title>Windows Installer Useful Advice</title>
      <description>VBScript Custom Actions are Not Windows Script Host
It's a common assumption that VBScript CAs can use WSH constructs based on the WScript object model. But you cannot use script code such as WScript.CreateObject or WScript.Quit or WScript.Echo. The WSH environment provides the WScript object model, just as VBScript in a Web page uses an IE object model. Windows Installer scripting supplies objects such as the Session object for interacting with the install. You don't need WScript.CreateObject anyway-VBScript has a CreateObject method that does the same thing. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fwindows-installer-useful-advice.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fwindows-installer-useful-advice.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/products/Windows_Installer_Useful_Advice</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/products/Windows_Installer_Useful_Advice</guid>
      <pubDate>Sat, 11 Oct 2008 22:58:25 GMT</pubDate>
    </item>
    <item>
      <title>Understanding Windows Server Core</title>
      <description>Windows server core is a "minimal" installation option for Windows Server 2008. What this means is that when you choose this option during setup (or when using unattended setup), Windows Server 2008 installs a minimum set of components on your machine that will allow you to run certain (but not all) server roles. In other words, selecting the Windows server core installation option installs only a subset of the binaries that are installed when you choose the full installation option for Windows Server 2008. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f10%2funderstanding-windows-server-core.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f10%2funderstanding-windows-server-core.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/products/Understanding_Windows_Server_Core</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/products/Understanding_Windows_Server_Core</guid>
      <pubDate>Wed, 08 Oct 2008 20:39:01 GMT</pubDate>
    </item>
    <item>
      <title>Visual Studio 2008 Task List Productivity Aids</title>
      <description>The Task List is essentially an integrated to-do list; it captures all the items that, for one reason or another, need attention and tracking. The Task List window then surfaces this list and allows you to interact with it. To show the window, select the View menu and choose the Task List entry illustrates the Task List window displaying a series of user tasks. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fvisual-studio-2008-task-list.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fvisual-studio-2008-task-list.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/visualstudio/Visual_Studio_2008_Task_List_Productivity_Aids</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/visualstudio/Visual_Studio_2008_Task_List_Productivity_Aids</guid>
      <pubDate>Sun, 05 Oct 2008 00:23:25 GMT</pubDate>
    </item>
    <item>
      <title>Sharing Information Using OLE in Windows Vista</title>
      <description>Object Linking and Embedding is far more flexible and can be far more complicated than cut-and-paste or drag-and-drop. OLE enables you to use all your software applications to create an integrated document. For instance, you might want to create an annual report that includes these components: &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f10%2fsharing-information-using-ole-in.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f10%2fsharing-information-using-ole-in.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/products/Sharing_Information_Using_OLE_in_Windows_Vista</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/products/Sharing_Information_Using_OLE_in_Windows_Vista</guid>
      <pubDate>Sun, 05 Oct 2008 00:18:07 GMT</pubDate>
    </item>
    <item>
      <title>Windows Vista Web Browser Security</title>
      <description>The web browser, an attacker can also get into your computer by using an exploit in a web browser by tricking you into installing a web component that has malicious code inside. Internet Explorer has many security settings built in that will help you keep safe. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f10%2fwindows-vista-web-browser-security.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f10%2fwindows-vista-web-browser-security.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/vista/Windows_Vista_Web_Browser_Security</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/vista/Windows_Vista_Web_Browser_Security</guid>
      <pubDate>Fri, 03 Oct 2008 23:34:55 GMT</pubDate>
    </item>
    <item>
      <title>Differences Between C# and C++</title>
      <description>C# is a strongly typed object-oriented language whose code visually resembles C++ (and Java). This decision by the C# language designers allows C++ developers to easily leverage their knowledge to quickly become productive in C#. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fdifferences-between-c-and-c.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fdifferences-between-c-and-c.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/csharp/Differences_Between_C_and_C</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/csharp/Differences_Between_C_and_C</guid>
      <pubDate>Fri, 03 Oct 2008 23:26:56 GMT</pubDate>
    </item>
    <item>
      <title>Single-File and Multifile .Net Assemblies</title>
      <description>In a great number of cases, there is a simple one-to-one correspondence between a .NET assembly and the binary file (*.dll or *.exe). Thus, if you are building a .NET *.dll, it is safe to consider that the binary and the assembly are one and the same. Likewise, if you are building an executable desktop application, the *.exe can simply be referred to as the assembly itself. However, this is not completely accurate. Technically speaking, if an assembly is composed of a single *.dll or *.exe module, you have a single-file assembly. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fsingle-file-and-multifile-net.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f10%2fsingle-file-and-multifile-net.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/Single_File_and_Multifile_Net_Assemblies</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/Single_File_and_Multifile_Net_Assemblies</guid>
      <pubDate>Wed, 01 Oct 2008 21:57:07 GMT</pubDate>
    </item>
    <item>
      <title>Publishing a Windows Vista Calendar on the Network</title>
      <description>Windows Calendar, a decent little program for managing your schedule. You can create appointments (both one-time and recurring), set up all-day events, schedule tasks, apply reminders to appointments and tasks, and view appointments by day, week, or month. This all works great for individuals, but a busy family needs to coordinate multiple schedules. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fpublishing-windows-vista-calendar-on.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fpublishing-windows-vista-calendar-on.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/vista/Publishing_a_Windows_Vista_Calendar_on_the_Network</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/vista/Publishing_a_Windows_Vista_Calendar_on_the_Network</guid>
      <pubDate>Wed, 01 Oct 2008 00:36:23 GMT</pubDate>
    </item>
    <item>
      <title>What's Inside an .Net Assembly?</title>
      <description>An assembly's EXE or DLL file is a standard "Portable Execution" (PE) file, the same file format used for non-.NET executables and code libraries (pretty much any Windows EXE or DLL file). &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fwhats-inside-net-assembly.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fwhats-inside-net-assembly.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/What_s_Inside_an_Net_Assembly</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/What_s_Inside_an_Net_Assembly</guid>
      <pubDate>Wed, 01 Oct 2008 00:28:05 GMT</pubDate>
    </item>
    <item>
      <title>Visual Basic 2008 Core Elements - Boxing</title>
      <description>Normally, when a conversion (implicit or explicit) occurs, the original value is read from its current memory location, and then the new value is assigned. For example, to convert a Short to a Long, the system reads the two bytes of Short data and writes them to the appropriate bytes for the Long variable. However, under Visual Basic, if a value type needs to be managed as an object, then the system performs an intermediate step. This intermediate step involves taking the value on the stack and copying it to the heap, a process referred to as boxing. As noted earlier, the Object class is implemented as a reference type, so the system needs to convert value types into reference types for them to be objects. This doesn't cause any problems or require any special programming, because boxing isn't something you declare or directly control, but it does affect performance. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fvisual-basic-2008-core-elements-boxing.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fvisual-basic-2008-core-elements-boxing.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/vbnet/Visual_Basic_2008_Core_Elements_Boxing</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/vbnet/Visual_Basic_2008_Core_Elements_Boxing</guid>
      <pubDate>Thu, 25 Sep 2008 00:02:24 GMT</pubDate>
    </item>
    <item>
      <title>IPv6 Terminology</title>
      <description>IPv6 common terms and concepts are defined as follows:
. Node Any device that runs an implementation of IPv6. This includes routers and hosts.

. Router A node that can forward IPv6 packets not explicitly addressed to itself. On an IPv6 network, a router also typically advertises its presence and host configuration information.

. Host A node that cannot forward IPv6 packets not explicitly addressed to itself (a nonrouter). A host is typically the source and a destination of IPv6 traffic, and it silently discards traffic received that is not explicitly addressed to itself.

... &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fipv6-terminology.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fipv6-terminology.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/IPv6_Terminology</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/IPv6_Terminology</guid>
      <pubDate>Wed, 24 Sep 2008 23:59:09 GMT</pubDate>
    </item>
    <item>
      <title>The .NET N-Tier Pattern</title>
      <description>Microsoft has been committed to n-tier development for a very long time. It was the heart of the now-deprecated Distributed interNet Architecture (DNA) introduced in 1999 &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fnet-n-tier-pattern.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fnet-n-tier-pattern.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/architecture/The_NET_N_Tier_Pattern</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/architecture/The_NET_N_Tier_Pattern</guid>
      <pubDate>Sun, 21 Sep 2008 16:32:54 GMT</pubDate>
    </item>
    <item>
      <title>About Wi-Fi</title>
      <description>Wireless networking is accomplished by sending a signal from one computer to another over radio waves. The most common form of wireless computing today uses the IEEE 802.11b standard. This popular standard, also called Wi-Fi or Wireless Fidelity, is now supported directly by newer laptops and PDAs, and most computer accessory manufacturers. It's so popular that "big box" electronics chain stores carry widely used wireless hardware and networking products. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fabout-wi-fi.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fabout-wi-fi.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/About_Wi_Fi</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/About_Wi_Fi</guid>
      <pubDate>Sun, 21 Sep 2008 16:25:52 GMT</pubDate>
    </item>
    <item>
      <title>Introducing the Building Blocks of the .NET Platform (the CLR, CTS, an</title>
      <description>Three key (and interrelated) entities that make it all possible: the CLR, CTS, and CLS. From a programmer's point of view, .NET can be understood as a runtime environment and a comprehensive base class library. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fintroducing-building-blocks-of-net.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fintroducing-building-blocks-of-net.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Introducing_the_Building_Blocks_of_the_NET_Platform_the_CLR_CTS_an</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Introducing_the_Building_Blocks_of_the_NET_Platform_the_CLR_CTS_an</guid>
      <pubDate>Fri, 19 Sep 2008 19:33:26 GMT</pubDate>
    </item>
    <item>
      <title>Windows Server 2008 Network Load-Balancing Clusters</title>
      <description>NLB in Windows Server 2008 is accomplished by a special network driver that works between the drivers for the physical network adapter and the TCP/IP stack. This driver communicates with the NLB program (called wlbs.exe, for the Windows Load Balancing Service) running at the application layer-the same layer in the OSI model as the application you are clustering. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fwindows-server-2008-network-load.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fwindows-server-2008-network-load.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/other/Windows_Server_2008_Network_Load_Balancing_Clusters</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/other/Windows_Server_2008_Network_Load_Balancing_Clusters</guid>
      <pubDate>Fri, 19 Sep 2008 19:04:12 GMT</pubDate>
    </item>
    <item>
      <title>Architecture of Windows Workflow Foundation</title>
      <description>WF itself is a programming model, along with an engine and a set of tools for building workflowenabled applications. The programming model is made up of exposed APIs that other programming languages can use to interact with the workflow engine. These APIs are encapsulated within a namespace called System.Workflow. That namespace will be part of the WinFX programming model, but can also be installed as an add-on to the existing .NET Framework 2.0. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2farchitecture-of-windows-workflow.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2farchitecture-of-windows-workflow.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/visualstudio/Architecture_of_Windows_Workflow_Foundation</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/visualstudio/Architecture_of_Windows_Workflow_Foundation</guid>
      <pubDate>Wed, 17 Sep 2008 23:22:38 GMT</pubDate>
    </item>
    <item>
      <title>Windows Server 2008 Windows Security - Security Identifiers</title>
      <description>Security principal is an entity that can have a security identifier (SID), SID is a (mostly) numeric representation of a security principal. The SID is actually what is used internally by the operating system. When you grant a user, a group, a service, or some other security principal permissions to an object, the operating system writes the SID and the permissions to the object's Access Control List (ACL). &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fwindows-server-2008-windows-security.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fwindows-server-2008-windows-security.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/security/Windows_Server_2008_Windows_Security_Security_Identifiers</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/security/Windows_Server_2008_Windows_Security_Security_Identifiers</guid>
      <pubDate>Wed, 17 Sep 2008 22:40:03 GMT</pubDate>
    </item>
    <item>
      <title>Pushing toward Windows Server 2008 Virtualization Envelope</title>
      <description>Windows Server 2008 is designed from the ground up to support virtualization. This means that you have the opportunity to change the way you manage servers and services. With the Windows Server 2008 hypervisor, Hyper-V, there is little difference between a machine running physically on a system and a machine running in a virtual instance. That's because the hypervisor does the same thing as a physical installation would by exposing hardware to VMs. The real difference between a physical installation and a VM running on the hypervisor is access to system resources. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fpushing-toward-windows-server-2008.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fcomputertechnos.blogspot.com%2f2008%2f09%2fpushing-toward-windows-server-2008.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/tipsandtricks/Pushing_toward_Windows_Server_2008_Virtualization_Envelope</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/tipsandtricks/Pushing_toward_Windows_Server_2008_Virtualization_Envelope</guid>
      <pubDate>Thu, 11 Sep 2008 00:40:03 GMT</pubDate>
    </item>
    <item>
      <title>The .NET System Management Services Requirements</title>
      <description>WMI is fully supported under Microsoft Windows 2000 and Windows XP. Although Windows NT 4.0, as well as Windows 95, 98, and ME provide only a limited support for WMI, most of the examples in this book will run just fine on these platforms. Hence, unless explicitly noted otherwise (there are a few code examples that depend on the software features that are available only under Windows 2000 or XP), you should feel free to compile and run the code on the platform of your choice. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fnet-system-management-services.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fnet-system-management-services.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/visualstudio/The_NET_System_Management_Services_Requirements</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/visualstudio/The_NET_System_Management_Services_Requirements</guid>
      <pubDate>Thu, 11 Sep 2008 00:35:39 GMT</pubDate>
    </item>
    <item>
      <title>Introduction to F#</title>
      <description>F# is a typed functional programming language for the .NET Framework. It combines the succinctness, expressivity, and compositionality of typed functional programming with the runtime support, libraries, interoperability, tools, and object model of .NET. &lt;br /&gt;&lt;br /&gt;&lt;br /&gt;&lt;a href="http://www.dotnetkicks.com/kick/?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fintroduction-to-f.html"&gt;&lt;img src="http://www.dotnetkicks.com/Services/Images/KickItImageGenerator.ashx?url=http%3a%2f%2fdevelopertechno.blogspot.com%2f2008%2f09%2fintroduction-to-f.html" border="0" alt="kick it on DotNetKicks.com" /&gt;&lt;/a&gt;
</description>
      <link>http://www.dotnetkicks.com/visualstudio/Introduction_to_F_1</link>
      <guid isPermaLink="true">http://www.dotnetkicks.com/visualstudio/Introduction_to_F_1</guid>
      <pubDate>Wed, 10 Sep 2008 13:54:52 GMT</pubDate>
    </item>
  </channel>
</rss>