<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://www.dotnetzone.gr:443/cs/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Creating a Data Access Layer in ASP.Net applications for inserting,selecting,deleting and updating data</title><link>https://www.dotnetzone.gr:443/cs/blogs/dotnetrules/archive/2011/01/23/creating-a-data-access-layer-in-asp-net-applications-for-inserting-selecting-deleting-and-updating-data.aspx</link><description>In this post I will be continuing my series of posts regarding data access methodologies/technologies that as I call them are pro ORM . I will be demonstrating how to use the connected and the disconnected data access models to retrieve,insert,update...(</description><dc:language>el</dc:language><generator>CommunityServer 2.1 SP3 (Build: 20423.1)</generator></channel></rss>