<?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>.NET Explored &#187; .NET</title>
	<atom:link href="http://ashishpal.com/dotnetexplored/category/net/feed/" rel="self" type="application/rss+xml" />
	<link>http://ashishpal.com/dotnetexplored</link>
	<description>Exploring the new features of .NET</description>
	<lastBuildDate>Mon, 21 Dec 2009 21:06:46 +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>Microsoft&#8217;s answer to Ruby on Rails &#8211; Dynamics Data</title>
		<link>http://ashishpal.com/dotnetexplored/2009/12/microsofts-answer-to-ruby-on-rails-dynamics-data/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/12/microsofts-answer-to-ruby-on-rails-dynamics-data/#comments</comments>
		<pubDate>Fri, 18 Dec 2009 19:36:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Entity Framework]]></category>
		<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[Dynamic Data]]></category>
		<category><![CDATA[Microsoft]]></category>
		<category><![CDATA[Ruby on Rails]]></category>

		<guid isPermaLink="false">http://ashishpal.com/dotnetexplored/?p=35</guid>
		<description><![CDATA[ASP.NET Dynamic Data brings major usability and RAD development changes to the existing ASP.NET data controls. RAD development is significantly increased by the use of a rich scaffolding framework. After you add a LINQ to SQL or Entity Framework data model to a project, you can simply register it with Dynamic Data. The result is ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/12/microsofts-answer-to-ruby-on-rails-dynamics-data/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>VB 6.0 Migration</title>
		<link>http://ashishpal.com/dotnetexplored/2009/12/vb-6-0-migration/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/12/vb-6-0-migration/#comments</comments>
		<pubDate>Thu, 10 Dec 2009 19:46:53 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Migration]]></category>

		<guid isPermaLink="false">http://ashishpal.com/dotnetexplored/?p=39</guid>
		<description><![CDATA[VB6 Migration Library
 
Visual Basic 6.0 runtime will be supported on Windows Server 2003 until June 2008 for Mainstream Support and June 2013 for Extended Support. The IDE will move out of extended support April 8, 2008.
 
Below are a series of links that relate to VB6 and VB6 Migration to VB.NET.

VBRun remains the best resource site for VB6 ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/12/vb-6-0-migration/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>.NET 1.1 to .NET 2.0 Migration FAQ</title>
		<link>http://ashishpal.com/dotnetexplored/2009/12/net-1-1-to-net-2-0-migration-faq/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/12/net-1-1-to-net-2-0-migration-faq/#comments</comments>
		<pubDate>Tue, 08 Dec 2009 20:20:58 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Migration]]></category>
		<category><![CDATA[.NET 1.1 to .NET 2.0 Migration]]></category>

		<guid isPermaLink="false">http://ashishpal.com/dotnetexplored/?p=50</guid>
		<description><![CDATA[NET 1.1 to .NET 2.0 Migration  FAQ
Q: “How much work will it take to move from 1.1 to 2.0 and how long will it take?” 
 A: The answer is “It depends”.  Some applications move over with the simple click of a button, and others take a little more work than that.
 
Q: “Do you need to migrate at ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/12/net-1-1-to-net-2-0-migration-faq/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>OAuth and .NET</title>
		<link>http://ashishpal.com/dotnetexplored/2009/11/oauth-and-net/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/11/oauth-and-net/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 17:37:06 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[OAuth]]></category>
		<category><![CDATA[Open source]]></category>
		<category><![CDATA[cloud computing]]></category>
		<category><![CDATA[Framework]]></category>
		<category><![CDATA[opensource]]></category>

		<guid isPermaLink="false">http://ashishpal.com/dotnetexplored/?p=28</guid>
		<description><![CDATA[OAuth is a new wave in the website security protocol or to be precise an API access delegation protocol’. OAuth allows a client application to obtain user consent (as access tokens) for executing operations over private resources on his behalf.
 OAuth allows you to share your private resources (photos, videos, contact list, bank accounts) stored on ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/11/oauth-and-net/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		</item>
		<item>
		<title>ORM in .NET</title>
		<link>http://ashishpal.com/dotnetexplored/2009/11/orm-in-net/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/11/orm-in-net/#comments</comments>
		<pubDate>Fri, 13 Nov 2009 15:39:13 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Entity Framework]]></category>
		<category><![CDATA[LINQ]]></category>
		<category><![CDATA[ORM]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://ashishpal.com/dotnetexplored/?p=25</guid>
		<description><![CDATA[ 

Introduction
ORM, or object-relational mapping, is one of the tougher things to accomplish in modern, object-oriented programming languages. It involves moving away from the traditional data store paradigm: there is no (or very little) dedicated, pre-compiled code involved in reading/writing an object to/from the database or other backing store. Instead, the logic involved in accessing the ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/11/orm-in-net/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>.NET goes open source and cross platform with Mono</title>
		<link>http://ashishpal.com/dotnetexplored/2009/11/net-goes-open-source-and-cross-platform-with-mono/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/11/net-goes-open-source-and-cross-platform-with-mono/#comments</comments>
		<pubDate>Wed, 11 Nov 2009 01:20:21 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Open source]]></category>
		<category><![CDATA[mono]]></category>
		<category><![CDATA[novell]]></category>
		<category><![CDATA[cross platform]]></category>
		<category><![CDATA[mono Framework]]></category>

		<guid isPermaLink="false">http://dotnetexplored.wordpress.com/?p=24</guid>
		<description><![CDATA[In the last blog i talked about MonoDevelop an open source cross platform IDE for .NET development. This cross platform .NET development was only possible due to the Mono Framework.
Mono is a software platform designed to allow developers to easily create cross platform applications. It is an open source implementation of Microsoft&#8217;s .Net Framework based ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/11/net-goes-open-source-and-cross-platform-with-mono/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>MonoDevelop opens up Mac for .NET development</title>
		<link>http://ashishpal.com/dotnetexplored/2009/11/monodevelop-opens-up-mac-for-net-development/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/11/monodevelop-opens-up-mac-for-net-development/#comments</comments>
		<pubDate>Sat, 07 Nov 2009 19:49:01 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[Open source]]></category>
		<category><![CDATA[Mac]]></category>
		<category><![CDATA[monodevelop]]></category>

		<guid isPermaLink="false">http://dotnetexplored.wordpress.com/?p=19</guid>
		<description><![CDATA[As I said that I am a technology evangelist. I like new technology in .NET as well as open source. Other thing which I liked was Mac. But before MonoDevelop both were two different worlds. You could not develop a .NET application on a Mac OS X. MonoDevelop has solved most of my problem or ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/11/monodevelop-opens-up-mac-for-net-development/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
		<item>
		<title>XMLDocument Vs LINQ to XML</title>
		<link>http://ashishpal.com/dotnetexplored/2009/11/xmldocument-vs-linq-to-xml/</link>
		<comments>http://ashishpal.com/dotnetexplored/2009/11/xmldocument-vs-linq-to-xml/#comments</comments>
		<pubDate>Sat, 07 Nov 2009 04:18:40 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[.NET]]></category>
		<category><![CDATA[LINQ]]></category>
		<category><![CDATA[XML]]></category>

		<guid isPermaLink="false">http://dotnetexplored.wordpress.com/?p=4</guid>
		<description><![CDATA[.NET as it had evolved has come up with different API to read and write XML data. If you are using .NET 3.0 and lower version you will have to use XMLDocument aka the classic DOM API. With .NET 3.0 Microsoft had launched Language Integrated Query(LINQ) and with this came one of the feature name ]]></description>
		<wfw:commentRss>http://ashishpal.com/dotnetexplored/2009/11/xmldocument-vs-linq-to-xml/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

