﻿<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/"><channel><title>博客园-Teddy's Knowledge Base-随笔分类-Tech. Thinking</title><link>http://teddyma.cnblogs.com/category/40980.html</link><description /><language>zh-cn</language><lastBuildDate>Sat, 06 Jun 2009 18:22:21 GMT</lastBuildDate><pubDate>Sat, 06 Jun 2009 18:22:21 GMT</pubDate><ttl>60</ttl><item><title>AdoNet vs LinqToSql vs NIntegrateQuery查询性能测试</title><link>http://www.cnblogs.com/teddyma/archive/2009/06/07/1497903.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Sat, 06 Jun 2009 17:45:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2009/06/07/1497903.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/1497903.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2009/06/07/1497903.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/1497903.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/1497903.html</trackback:ping><description><![CDATA[摘要: AdoNet vs LinqToSql vs NIntegrateQuery查询性能测试.

先上测试结果:

AdoNetTest: 267ms
AdoNetCachedCommandTest: 182ms
LinqToSqlTest: 3191ms
LinqToSqlCompiledQueryTest: 386ms
NIntegrateQueryTest: 266ms &nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2009/06/07/1497903.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/1497903.html?type=1" width = "1" height = "1" />]]></description></item><item><title>提前发布4/25上海俱乐部活动演讲&amp;ldquo;集中化WCF服务配置管理&amp;rdquo;示例程序</title><link>http://www.cnblogs.com/teddyma/archive/2009/04/21/1440086.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Mon, 20 Apr 2009 16:45:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2009/04/21/1440086.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/1440086.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2009/04/21/1440086.html#Feedback</comments><slash:comments>5</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/1440086.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/1440086.html</trackback:ping><description><![CDATA[摘要: 本示例程序具体演示如下内容：
1) 基于SQL Server数据库的集中化WCF服务配置管理;
2) 集中化ConnectingString管理;
3) 集中化AppVariable管理;
4) 基于集中化配置管理的WCF ServiceHostFactory和WCF ServiceLocator;
5) 基于集中化配置管理的跨WCF的LINQ Style分页、排序查询及DataSource控件的使用;
6) 整合本地ServiceLocator的WCF服务发布和消费;&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2009/04/21/1440086.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/1440086.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Apply SOA Design Patterns with WCF (5) WCF Based ASP.NET DataSouce Control (基于WCF的数据源控件)</title><link>http://www.cnblogs.com/teddyma/archive/2009/03/30/1424710.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Sun, 29 Mar 2009 16:03:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2009/03/30/1424710.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/1424710.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2009/03/30/1424710.html#Feedback</comments><slash:comments>3</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/1424710.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/1424710.html</trackback:ping><description><![CDATA[摘要: 本文介绍如何实现一个基于WCF的ASP.NET数据源控件,从而使得跨WCF通信的数据库CRUD,尤其是复杂的分页排序更简单。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2009/03/30/1424710.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/1424710.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Apply SOA Design Patterns with WCF (4) WCF Database Paging &amp; Sorting (数据库端分页和排序)</title><link>http://www.cnblogs.com/teddyma/archive/2009/03/28/1423780.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Fri, 27 Mar 2009 16:24:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2009/03/28/1423780.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/1423780.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2009/03/28/1423780.html#Feedback</comments><slash:comments>14</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/1423780.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/1423780.html</trackback:ping><description><![CDATA[摘要: 本文提供一种支持跨WCF通讯的数据库端分页和排序(以及更多超过你预期的功能)方案。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2009/03/28/1423780.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/1423780.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Apply SOA Design Patterns with WCF (3) Automatic Service Locating (自动化服务定位)</title><link>http://www.cnblogs.com/teddyma/archive/2009/03/26/1422776.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Thu, 26 Mar 2009 15:57:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2009/03/26/1422776.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/1422776.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2009/03/26/1422776.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/1422776.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/1422776.html</trackback:ping><description><![CDATA[摘要: 本文提供一种在WCF服务消费应用程序中通过与服务提供应用程序共享WCF服务契约接口来自动化定位WCF服务实现的方案。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2009/03/26/1422776.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/1422776.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Apply SOA Design Patterns with WCF (2) WCF Automatic Deployment (自动化部署)</title><link>http://www.cnblogs.com/teddyma/archive/2009/03/25/1421892.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 25 Mar 2009 15:14:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2009/03/25/1421892.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/1421892.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2009/03/25/1421892.html#Feedback</comments><slash:comments>1</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/1421892.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/1421892.html</trackback:ping><description><![CDATA[摘要: 本文提供一种简化在多服务器和服务器群上自动化部署WCF服务的方案。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2009/03/25/1421892.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/1421892.html?type=1" width = "1" height = "1" />]]></description></item><item><title>一种高性能Hierarchical RBAC实现方案</title><link>http://www.cnblogs.com/teddyma/archive/2008/01/23/1050627.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 23 Jan 2008 13:29:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2008/01/23/1050627.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/1050627.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2008/01/23/1050627.html#Feedback</comments><slash:comments>24</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/1050627.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/1050627.html</trackback:ping><description><![CDATA[摘要: 背景&nbsp;框图上图中，Role和被设置Permission的Resource都是可以有任意层级继承关系的。&nbsp;举例&nbsp;举一个网站的例子来说：&...&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2008/01/23/1050627.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/1050627.html?type=1" width = "1" height = "1" />]]></description></item><item><title>基于CodeGenerator的Emit代码生成辅助类源码及演示</title><link>http://www.cnblogs.com/teddyma/archive/2007/10/10/919449.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 10 Oct 2007 03:56:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2007/10/10/919449.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/919449.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2007/10/10/919449.html#Feedback</comments><slash:comments>14</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/919449.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/919449.html</trackback:ping><description><![CDATA[摘要: 本文介绍一组NBearV4中的基于Emit动态生成代码的辅助类，部分概念在本人的blog之前的文章中或多或少都有介绍，这里包含最新的更新及演示、测试。主要是两个类：CodeGenerator和DynamicMethodFactory。前者提供了一种经过封装的，简化Emit方法（包括Emit DynamicMethod，Constructor，Method，get、set Method of Property）的方案；后者基于前者，实现了一种访问指定类（可以是第三方程序集的internal类）的方法或成员变量，实例化第三方程序集中的internal类型，高性能的以非泛型语法访问泛型方法的机制（通过DynamicMethod和Delegate实现）。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2007/10/10/919449.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/919449.html?type=1" width = "1" height = "1" />]]></description></item><item><title>扩展Kevin McFarlane的C#版DesignByContract Framework</title><link>http://www.cnblogs.com/teddyma/archive/2007/10/05/914656.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Fri, 05 Oct 2007 07:01:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2007/10/05/914656.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/914656.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2007/10/05/914656.html#Feedback</comments><slash:comments>7</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/914656.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/914656.html</trackback:ping><description><![CDATA[摘要: Kevin McFarlane的C#版DesignByContract Framework实现从02年在CodeProject发布至今，几乎成为C#开发中大多数朋友使用的事实标准。本文结合对该框架的使用经验，在Kevin的原始版本的基础上，使用Strategy Pattern对其进行进一步的扩展，对最常用的检查语义进行封装简化。本文改进的源码以Public Domain协议发布，也就是说，完全没有任何限制。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2007/10/05/914656.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/914656.html?type=1" width = "1" height = "1" />]]></description></item><item><title>发布NBearLite中文版完全参考手册 + NBearLite 10分钟入门教程 + NBearLite v1.0.0.7 beta</title><link>http://www.cnblogs.com/teddyma/archive/2007/07/29/835412.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Sun, 29 Jul 2007 07:12:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2007/07/29/835412.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/835412.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2007/07/29/835412.html#Feedback</comments><slash:comments>22</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/835412.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/835412.html</trackback:ping><description><![CDATA[摘要: NBearLite是一个.NET 2.0开源(BSD协议)通用数据访问组件，支持SQL Server、Oracle、MS Access，MySQL，SQLite，PostgreSQL等多种数据库的透明切换（改变数据库类型时无需修改具体的查询代码）。NBearLite实现了一套类似LINQ的强类型数据库查询语法(支持从简单的CRUD查询到GroupBy、InnerJoin，Paging，SubQuery等常用复杂查询)。NBearLite提供的代码生成工具还可以为您自动生成所有的存储过程调用包装代码，可以让您像使用一个.NET类的方法一样访问存储过程（支持SQL Server，Oracle，MySQL，PostgreSQL数据库）。

NBearLite不是一个ORM工具，它不涉及实体类，NBearLite的所有查询返回Scalar/DataSet/IDataReader等ADO.NET原生数据类型。

推荐在使用NBearLite的同时结合使用NBearMapping进行IDataReader/DataRow数据类型和自定义.NET类(如：实体类或业务类&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2007/07/29/835412.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/835412.html?type=1" width = "1" height = "1" />]]></description></item><item><title>再续NBear性能测试:ADO.NET, NBearV3, NHibernateV1, NBearLite, NBearLite+NBearMapping性能比较[2008/1/3修订：NBearLite更新至v1.0.1.0整合NBearMapping版地测试结果]</title><link>http://www.cnblogs.com/teddyma/archive/2007/07/26/831646.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Thu, 26 Jul 2007 00:15:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2007/07/26/831646.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/831646.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2007/07/26/831646.html#Feedback</comments><slash:comments>27</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/831646.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/831646.html</trackback:ping><description><![CDATA[摘要: 本测试对ADO.NET, NBearV3, NHibernateV1, NBearLite, NBearLite+NBearMapping进行了常见的读写测试。本测试同时证实，NBearLite及NBearLite+NBearMapping的ORM方案，平均性能有很大改善。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2007/07/26/831646.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/831646.html?type=1" width = "1" height = "1" />]]></description></item><item><title>NbearV3.7新增强类型查询功能演示教程</title><link>http://www.cnblogs.com/teddyma/archive/2007/04/24/725570.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Tue, 24 Apr 2007 09:11:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2007/04/24/725570.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/725570.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2007/04/24/725570.html#Feedback</comments><slash:comments>42</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/725570.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/725570.html</trackback:ping><description><![CDATA[摘要: 本教程演示了NBear中典型的的各种查询功能。包括：join，group by，paging等的支持。<br>下载地址：http://nbear.org/Modules/Articles/Detail.aspx?i=59&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2007/04/24/725570.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/725570.html?type=1" width = "1" height = "1" />]]></description></item><item><title>源码发布 - DynamicMethodProxyFactory组件</title><link>http://www.cnblogs.com/teddyma/archive/2007/03/28/690946.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 28 Mar 2007 03:10:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2007/03/28/690946.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/690946.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2007/03/28/690946.html#Feedback</comments><slash:comments>24</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/690946.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/690946.html</trackback:ping><description><![CDATA[摘要: 在前面的文章改进的“以非泛型方式调用泛型方法”之基于DynamicMethod的实现中，提到了一种通过DynamicMethod以非泛型方法代理访问泛型方法的较佳方法（无额外代码定义需要，执行时间大约相当于直接调用泛型方法的3-4倍）。本文介绍的组件在前文思路的基础上，进行进一步的扩展，封装成一个较通用的DynamicMethodProxyFactory组件。除了可以较高性能访问任意的静态或非静态、泛型或非泛行方法之外，利用DynamicMethod可将代码插入内存中已载入的Module的能力，提供了在程序集外实例化指定Module中的internal类型，在程序集外调用internal类型的方法和public类型的internal方法的支持。<br><br>该组件实现如下功能：<br>1、以通用的非泛行方法Delegate访问任意方法（泛型或非泛型，静态或非静态）；<br>2、支持在程序集外调用指定Module中的internal类型的任意属性（属性本质上可以通过它的get/set方法以方法的形式访问）和方法和public类型的internal方法；<br>3、支持创建并返&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2007/03/28/690946.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/690946.html?type=1" width = "1" height = "1" />]]></description></item><item><title>改进的“以非泛型方式调用泛型方法”之基于DynamicMethod的实现</title><link>http://www.cnblogs.com/teddyma/archive/2007/03/22/684306.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Thu, 22 Mar 2007 09:06:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2007/03/22/684306.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/684306.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2007/03/22/684306.html#Feedback</comments><slash:comments>10</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/684306.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/684306.html</trackback:ping><description><![CDATA[摘要: 本文针对双鱼座同志的以非泛型方式调用泛型方法一文，提出一种更通用的以非泛型方式调用泛型方法的实现——基于DynamicMethod的实现。<br>基于DynamicMethod的实现的优点是，执行性能和双鱼座的文中实现的第5种方案——动态生成的非泛型接口包装相当（因为都是基于Emit的），但是，避免了原文实现中必须额外定义接口、Delegate的需要，从而，非常通用，应该是解决相同问题的前提下目前所能想到最佳实现。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2007/03/22/684306.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/684306.html?type=1" width = "1" height = "1" />]]></description></item><item><title>重新设计NBearV3中的实体关联设计语言，实现数据库完整性约束和级联更新</title><link>http://www.cnblogs.com/teddyma/archive/2006/11/12/558609.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Sun, 12 Nov 2006 14:09:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/11/12/558609.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/558609.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/11/12/558609.html#Feedback</comments><slash:comments>14</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/558609.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/558609.html</trackback:ping><description><![CDATA[摘要: 闭关一个周末，重写了NBearV3的实体关联设计语言。新的语法能够更清晰明了的表述所有常见实体关联关系。新的实现版本同时实现了数据库完整性约束检测和自动级联更新。所有NBearV3教程已经更新以反映最...&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/11/12/558609.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/558609.html?type=1" width = "1" height = "1" />]]></description></item><item><title>NBearV3——ORM实体关系设计速查手册</title><link>http://www.cnblogs.com/teddyma/archive/2006/11/09/554823.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Thu, 09 Nov 2006 00:05:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/11/09/554823.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/554823.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/11/09/554823.html#Feedback</comments><slash:comments>24</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/554823.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/554823.html</trackback:ping><description><![CDATA[摘要: 本手册演示NBearV3支持的所有实体关系设计的完全参考。包括1对1，1对多，多对多关联以及自关联的正向、反向引用时的所有情况的设计方法。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/11/09/554823.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/554823.html?type=1" width = "1" height = "1" />]]></description></item><item><title>NBearV3.0.0 Preview发布 - 全新ORM实现！[11/1 更新：全面支持实体属性级联更新]</title><link>http://www.cnblogs.com/teddyma/archive/2006/11/01/545885.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 01 Nov 2006 04:40:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/11/01/545885.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/545885.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/11/01/545885.html#Feedback</comments><slash:comments>81</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/545885.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/545885.html</trackback:ping><description><![CDATA[摘要: 11/1 更新：全面支持实体属性级联更新，详见下面的案例的Entity Usage UnitTests代码。<br><br>NBearV3新增/修改功能列表：<br>1、完全重新设计的ORM实现，支持实体继承，实体间复杂关联（一对一、一对多、多对多）及透明的级联插入、更新、删除，LazyLoad等。<br>2、提供用于整个开发过程的更易使用的代码生成工具，支持：实体设计代码、实体代码、实体配置文件和数据库创建脚本生成。<br>3、精简优化了底层数据访问代码，进行了更细致的单线程/多线程性能测试。<br>4、实体及关联关系可以使用任意标准的.Net Framework支持的语言，使用interface、Attribute、接口继承等语言的自然元素作为实体设计元数据，并使用VS.NET2005的类设计器进行设计。<br>5、自动生成的实体类是标准的class，避免了V2中基于Emit生成代码的性能损失和可能的内存泄露，集成用于强类型查询的查询代码到每个实体类，并支持标准的各种系统序列化（XML，Binary，WebService SOAP）。生成的实体类代码不&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/11/01/545885.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/545885.html?type=1" width = "1" height = "1" />]]></description></item><item><title>实例解析继承体系重构及ORM映射</title><link>http://www.cnblogs.com/teddyma/archive/2006/08/16/478427.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 16 Aug 2006 08:16:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/08/16/478427.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/478427.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/08/16/478427.html#Feedback</comments><slash:comments>15</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/478427.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/478427.html</trackback:ping><description><![CDATA[摘要: 本文以双鱼座同学的再说继承关系一文中提到的一组三元继承关联关系为基础。<br><br>首先，分别实现本人的ORM中的继承关系映射全解一文中提到的三种实体继承体系到关系数据库的映射方案实例。<br><br>接着，使用接口分离以上继承体系中的实体类中的相同概念，对该继承体系进行重构，并同样给出对重构后的继承体系的三种到关系数据库的映射方案实例。<br><br>全部实例代码基于NBear的接口式实体定义方式实现。<br>&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/08/16/478427.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/478427.html?type=1" width = "1" height = "1" />]]></description></item><item><title>ORM中的继承关系映射全解——单表继承体系、一实体一具体表、一实体一扩展表、接口映射</title><link>http://www.cnblogs.com/teddyma/archive/2006/08/14/InheritenceMappingInORM.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Mon, 14 Aug 2006 03:08:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/08/14/InheritenceMappingInORM.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/476195.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/08/14/InheritenceMappingInORM.html#Feedback</comments><slash:comments>2</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/476195.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/476195.html</trackback:ping><description><![CDATA[摘要: 实体继承是基于OO和关系型数据库软件系统设计中的一个重要主题。本文通过基于NBear的实例解析ORM中的实体继承体系映射的方方面面。<br><br>本文涉及的内容包括：<br><br>1. 单表继承体系<br>2. 一实体一具体表<br>3. 一实体一扩展表<br>4. 接口实现映射vs基类继承映射&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/08/14/InheritenceMappingInORM.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/476195.html?type=1" width = "1" height = "1" />]]></description></item><item><title>NBearV2.1.0，新增Oracle和MySql Db Provider，诚征测试</title><link>http://www.cnblogs.com/teddyma/archive/2006/08/07/470099.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Mon, 07 Aug 2006 08:54:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/08/07/470099.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/470099.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/08/07/470099.html#Feedback</comments><slash:comments>3</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/470099.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/470099.html</trackback:ping><description><![CDATA[摘要: 将NBear升级到V2.1.0，主要更新如下：<br>1）新增Oracle和MySql Db Provider，使得NBear目前已经支持Oracle和My Sql数据库；<br>2）修复Lukiya之前遇到的以不同的参数列表调用相同的存储过程时（虽然这样的情形不太常见）的command缓存问题；<br>3）修复command参数名称包含数字或下划线时的参数值自动填充问题；<br><br>旧版本用户手册链接已更新至对应于V2.1.0的新版本V1.1。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/08/07/470099.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/470099.html?type=1" width = "1" height = "1" />]]></description></item><item><title>JST+JSON+AJAX——使用客户端js模版代替服务端数据绑定</title><link>http://www.cnblogs.com/teddyma/archive/2006/07/28/462314.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Fri, 28 Jul 2006 09:11:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/07/28/462314.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/462314.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/07/28/462314.html#Feedback</comments><slash:comments>7</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/462314.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/462314.html</trackback:ping><description><![CDATA[摘要: 本文给出一个通过组合使用JST，JSON和AJAX技术，使用客户端js模版代替服务端数据绑定的范例。很显然的，使用客户端数据绑定代替服务端数据绑定能够大大减少服务端的内存和CPU消耗，在硬件不变的情况下，大大提升服务器负载能力。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/07/28/462314.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/462314.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Web Application Architectures: Simple 2 Layer, Standard 3 Layer and Distributed 3 Layer</title><link>http://www.cnblogs.com/teddyma/archive/2006/07/19/WebApplicationArchitectures.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 19 Jul 2006 06:54:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/07/19/WebApplicationArchitectures.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/454656.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/07/19/WebApplicationArchitectures.html#Feedback</comments><slash:comments>43</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/454656.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/454656.html</trackback:ping><description><![CDATA[摘要: Abstract:<br><br>This article discusses three common web application architectures: Simple 2 Layer, Standard 3 Layer and Distributed 3 Layer. For each architecture, it gives an ASP.NET 2.0 sample implementaion with NBear framework.<br><br>Table of Contents:<br><br>1. Simple 2 Layer<br>2. Standard 3 Layer<br>3. Distributed 3 Layer<br>4. More about NBear<br>5. Get Source Code of NBear and All Samples<br>6. Summary&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/07/19/WebApplicationArchitectures.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/454656.html?type=1" width = "1" height = "1" />]]></description></item><item><title>使用NBear.MQ分布式服务消息队列模块开发分布式系统</title><link>http://www.cnblogs.com/teddyma/archive/2006/05/31/414059.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Wed, 31 May 2006 07:56:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/05/31/414059.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/414059.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/05/31/414059.html#Feedback</comments><slash:comments>6</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/414059.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/414059.html</trackback:ping><description><![CDATA[摘要: NBear.MQ是NBear Framework中新增的分布式消息队列模块，作为NBear Framework的新成员，NBear.MQ秉承NBear一贯的易于使用和零配置需要的特点，大大改善开发基于消息队列的分布式系统的效率。本文通过介绍一个基于NBear.MQ的Sample - TestServiceMQ，演示基于NBear.MQ开发分布式系统的基本方法。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/05/31/414059.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/414059.html?type=1" width = "1" height = "1" />]]></description></item><item><title>基于NBear的Domain层设计</title><link>http://www.cnblogs.com/teddyma/archive/2006/05/07/393057.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Sun, 07 May 2006 02:39:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/05/07/393057.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/393057.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/05/07/393057.html#Feedback</comments><slash:comments>17</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/393057.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/393057.html</trackback:ping><description><![CDATA[摘要: NBear是Teddy开发的快速开发框架，在之前的5个示例中，主要演示了主要的框架功能和业务领域模型不太复杂情形下忽略领域层的应用范例。但是，当业务模型相对复杂，单纯基于简单实体的强类型数据访问接口，可能就会使得太多的业务逻辑被分散到service或facade层，此时，我们就最好加一层独立的业务领域模型层来封装实体和强类型接口的使用。本文为您演示基于NBear v1.6.0中新增的NBear.Domain的领域模型设计示例。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/05/07/393057.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/393057.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Call  Back Callback - 整合AjaxHepler到NBear</title><link>http://www.cnblogs.com/teddyma/archive/2006/04/27/386985.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Thu, 27 Apr 2006 14:30:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/04/27/386985.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/386985.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/04/27/386985.html#Feedback</comments><slash:comments>10</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/386985.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/386985.html</trackback:ping><description><![CDATA[摘要: 今天将NBear升级到v1.5.5，主要的升级一是新增了三个类EntitySerializer, OneToManyEntitySerializer, OneToOneEntitySerializer用于简化用户对序列化子件的使用，您不必再对着SerializerHelper提供给您的大堆序列化方法无所适从了。另一个重要的更新是集成了AjaxHelper - Teddy以前的Ajax实现到NBear。AjaxHelper原来的实现基于Prototype1.3.1，从Atlas beta出来起，Teddy已经很久没有更新了，因为我一直在思考AjaxHelper存在的必要性，如果存在，该突出什么。这次不是简单的Copy到NBear的目录，而是完整的集成，Ajax的实现核心也改用ASP.NET2.0内置的Callback代替prototype，主要的使用方式不变，请运行并参见下载后的源码的NBear.WebTest project的TestAjaxHelper.aspx，该页面包含了使用范例和简单说明。因为大致的使用方式没变，关于AjaxHelper的更多以前的AjaxHelper相关文章。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/04/27/386985.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/386985.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Ilungasoft Framework 正式更名为 NBear</title><link>http://www.cnblogs.com/teddyma/archive/2006/04/25/384787.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Tue, 25 Apr 2006 09:35:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/04/25/384787.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/384787.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/04/25/384787.html#Feedback</comments><slash:comments>27</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/384787.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/384787.html</trackback:ping><description><![CDATA[摘要: NBear原名Ilungasoft Framework，是主要有Teddy开发的一个基于.Net 2.0 (C# 2.0, ASP.NET 2.0)的快速开发框架，她将使您基于.Net 2.0的web/winform开发变得异常高效、性能卓越。<br><br>名称NBear的由来：<br><br>N代表.Net，也代表No；Bear既可以翻译成熊，也有忍受之意。<br><br>Bear虽然是那种看起来憨憨的可爱动物，但是攻击时身手“敏捷”，因此.Net Bear代表了NBear是一个基于.Net2.0、为敏捷开发而生的快速开发框架。<br><br>我们大多数项目的开发需要Bear（忍受）太多的不必要的重复和繁琐的配置。如数据持久化、对象池、Web开发中的URL重定向、输入验证、客户端脚本等等，为了简化许多常用组件充用，NBear为您提供了许多灵活的工具和组件；为了简化繁琐的配置（尤其是如NHibernate这类ORM组件的繁琐的配置文件格式、高高的学习曲线和噩梦般的需求变更时的维护更新），NBear向您提供零配置需要的数据访问（持久化）接口和可充用组件。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/04/25/384787.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/384787.html?type=1" width = "1" height = "1" />]]></description></item><item><title>.Net 2.0: Entity as DTO vs Dataset as DTO / Xml Serialization vs JSON Serialization</title><link>http://www.cnblogs.com/teddyma/archive/2006/04/18/376067.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Tue, 18 Apr 2006 08:23:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/04/18/376067.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/376067.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/04/18/376067.html#Feedback</comments><slash:comments>15</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/376067.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/376067.html</trackback:ping><description><![CDATA[摘要: 本文以一组Entity vs Dataset的性能测试数据为基础，比较以Entity作为DTO和Dataset作为DTO的性能差异。测试可能不一定严密，但是一定程度上能够比较出优劣。希望能为您选择 .Net下不同的数据承载方式、序列化方式、DTO的选择，多一点参考。在本测试中，每个执行过程，对于Entity，我们将先用DataReader读出数据，使用索引将数据填充到Entity，序列化，再反序列化；对于Dataset，将先读取所有数据到Dataset，序列化，再反序列化，最后通过索引填充Dataset中的数据到Entity。也就是说，无论对Entity还是Dataset，我们都尽可能的取其最佳性能的执行方式，从而将性能瓶颈留在了序列化和反序列化方式上。您可以注意到，Dataset的序列化和反序列化性能是非常突出的，但是，我们基于Entity的自定义序列化方式的综合性能，超越了Dataset。<br><br>04/18补充：新增.NET JSON序列化对照。关于JSON的更多介绍请参见：http://www.json.org/。不过值得一提的是，官方提供的.Net实现写得那个烂得简&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/04/18/376067.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/376067.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Ilungasoft Framework: 使用视图处理继承关系、Tree结构实体关系映射示例[源码]</title><link>http://www.cnblogs.com/teddyma/archive/2006/04/10/370971.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Mon, 10 Apr 2006 03:16:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/04/10/370971.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/370971.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/04/10/370971.html#Feedback</comments><slash:comments>0</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/370971.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/370971.html</trackback:ping><description><![CDATA[摘要: 本示例演示基于Ilungasoft Framework实现继承关系和Tree结构的实体。前面的文章已经介绍过，基于Ilungasoft Framework的开发模型使用可调试的视图（Views）代替传统ORM中不可调试的Configuration（例如：XML等各式的配置文件）。前面的Sample2已经介绍了如何使用视图处理一般的OneToMany、ManyToMany关系，本文演示的Sample4，将演示更为复杂的继承和tree结构，具体演示内容包括：<br><br>1、继承映射（采用一实体一表，不冗余父表字段方式映射）；<br>2、两种Tree结构映射方式（方式一：单表行冗余，采用用户事务维护tree关系；方式二：单表无冗余，Inner Join + Union）；<br>3、演示Ilungasoft Framework中的一个新的用于简化处理关联实体的类OneToMany的使用。 &nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/04/10/370971.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/370971.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Ilungasoft Framework: 由Emit带来的序列化问题——IEntity的序列化支持范例[源码][04/08修正]</title><link>http://www.cnblogs.com/teddyma/archive/2006/04/08/369404.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Sat, 08 Apr 2006 08:57:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/04/08/369404.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/369404.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/04/08/369404.html#Feedback</comments><slash:comments>4</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/369404.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/369404.html</trackback:ping><description><![CDATA[摘要: 本文主要探讨关于Ilungasoft Framework中动态Entity的序列化问题。如果您之前也关注过Ilungasoft Framework，您一定会被其Entity定义格式的简单所吸引，用户只需要定义实体类的接口（框架提供生成工具）。这里，Teddy将基于一个新的Sample，讨论使用.Net框架提供的默认序列化类序列化基于本框架的Entity的多种情形。关于Ilungasoft Framework的更多文章索引及版本更新，您可以访问：Ilungasoft Framework官方首页。<br><br>更正：本文最初的论述有一些错误，在双鱼座的指点下，只需将emit动态生成的程序集加载到AppDomain就能使Sample3中所有的序列化和反序列化正确运行！请注意下文中划去的文字和红色的更正文字。&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/04/08/369404.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/369404.html?type=1" width = "1" height = "1" />]]></description></item><item><title>Ilungasoft Framework中处理有关联关系的实体</title><link>http://www.cnblogs.com/teddyma/archive/2006/04/04/366350.html</link><dc:creator>Teddy's Knowledge Base</dc:creator><author>Teddy's Knowledge Base</author><pubDate>Tue, 04 Apr 2006 02:51:00 GMT</pubDate><guid>http://www.cnblogs.com/teddyma/archive/2006/04/04/366350.html</guid><wfw:comment>http://www.cnblogs.com/teddyma/comments/366350.html</wfw:comment><comments>http://www.cnblogs.com/teddyma/archive/2006/04/04/366350.html#Feedback</comments><slash:comments>9</slash:comments><wfw:commentRss>http://www.cnblogs.com/teddyma/comments/commentRss/366350.html</wfw:commentRss><trackback:ping>http://www.cnblogs.com/teddyma/services/trackbacks/366350.html</trackback:ping><description><![CDATA[摘要: Ilungaosft Framework是Teddy近期发布的开源Web快速开发框架，包括持久层及一系列方便Web开发的组件。本文将在一个新的Sample的基础上，说明基于Ilungasoft Framework开发是如何处理有关联关系的实体。我要再次说明的是，Ilungasoft Framework的设计出发点不是要完全透明的进行ORM，因此，不会自动映射实体关系，以此换来的好处是其完全不需要配置，拥有极大的灵活性和易用性。但是这并不表示，基于Ilungasoft Framework处理实体关系就不方便。本示例就演示了一个非常常见的用户和组、消息的关联关系，涵盖了一对多、多对多的关联情形。<br>&nbsp;&nbsp;<a href='http://www.cnblogs.com/teddyma/archive/2006/04/04/366350.html'>阅读全文</a><img src ="http://www.cnblogs.com/teddyma/aggbug/366350.html?type=1" width = "1" height = "1" />]]></description></item></channel></rss>