Thu, 15 Jan 2009 15:08:00 GMThttp://blog.csdn.net/HeavensDoor/http://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789430.aspxhttp://blog.csdn.net/HeavensDoor/comments/3789430.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3789430.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3789430如何优化SQL Server数据库查询<img src ="http://blog.csdn.net/HeavensDoor/aggbug/3789430.aspx" width = "1" height = "1" />Thu, 15 Jan 2009 23:08:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789430.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789430.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789430.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847539/5485902http://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789383.aspxhttp://blog.csdn.net/HeavensDoor/comments/3789383.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3789383.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3789383SQL Server 2005：你应知道的13件事<img src ="http://blog.csdn.net/HeavensDoor/aggbug/3789383.aspx" width = "1" height = "1" />Thu, 15 Jan 2009 23:01:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789383.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789383.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789383.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847540/5485902http://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789369.aspxhttp://blog.csdn.net/HeavensDoor/comments/3789369.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3789369.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3789369SQL服务器面临的危险和补救.读[十种方法]后感<img src ="http://blog.csdn.net/HeavensDoor/aggbug/3789369.aspx" width = "1" height = "1" />Thu, 15 Jan 2009 22:59:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789369.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789369.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789369.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847541/5485902http://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789239.aspxhttp://blog.csdn.net/HeavensDoor/comments/3789239.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3789239.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3789239SQL Server中未公布的扩展存储过程注入<img src ="http://blog.csdn.net/HeavensDoor/aggbug/3789239.aspx" width = "1" height = "1" />Thu, 15 Jan 2009 22:41:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789239.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789239.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2009/01/15/3789239.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847542/5485902http://blog.csdn.net/HeavensDoor/archive/2008/12/30/3647228.aspxhttp://blog.csdn.net/HeavensDoor/comments/3647228.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3647228.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3647228研究了很多微软调用COM 对象或者ActiveX控件的范例，都很少有用到Marshal.ReleaseComObject 方法。因此，对超图范例频繁使用该方法的原因产生了好奇。所以花2天时间集中研究了一下。<img src ="http://blog.csdn.net/HeavensDoor/aggbug/3647228.aspx" width = "1" height = "1" />Tue, 30 Dec 2008 22:35:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3647228.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3647228.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3647228.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847543/5485902http://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644882.aspxhttp://blog.csdn.net/HeavensDoor/comments/3644882.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3644882.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3644882com interop看上去象是介乎于com和.net之间的一条纽带，一座桥梁。为了保持向后兼容，com interop能使得.net程式在不修改原有com组件的前提下方便的访问com组件。这一点是非常重要的。事实上，全球的com组件的代码量估计可能有数十亿行，拥有这些com组件的公司不可能重写这些组件，所以com interop的存在为有此需求的研发者提供了非常好的解决方案。 <img src ="http://blog.csdn.net/HeavensDoor/aggbug/3644882.aspx" width = "1" height = "1" />Tue, 30 Dec 2008 17:55:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644882.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644882.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644882.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847544/5485902http://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644842.aspxhttp://blog.csdn.net/HeavensDoor/comments/3644842.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3644842.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3644842<br />这篇文章讨论如何在C＃中实现三层架构，使用MS Access数据库存储数据。在此，我在3层架构中实现一个小型的可复用的组件保存客户数据。并提供添加，更新，查找客户数据的功能。<br /><br />背景<br /><br />首先，我介绍一些3层架构的理论知识。简单说明：什么是3层架构？3层架构的优点是什么？<br /><br />什么是三层架构？<br /><br />3层架构是一种“客户端－服务器”架构，在此架构中用户接口，商业逻辑，数据保存以及数据访问被设计为独立的模块。主要有3个层面，第一层（表现层，GUI层），第二层（商业对象，商业逻辑层），第三层（数据访问层）。这些层可以单独开发，单独测试。<br /><br />为什么要把程序代码分为3层。把用户接口层，<img src ="http://blog.csdn.net/HeavensDoor/aggbug/3644842.aspx" width = "1" height = "1" />Tue, 30 Dec 2008 17:50:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644842.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644842.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644842.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847545/5485902http://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644848.aspxhttp://blog.csdn.net/HeavensDoor/comments/3644848.aspx0http://blog.csdn.net/HeavensDoor/comments/commentRss/3644848.aspxhttp://tb.blog.csdn.net/TrackBack.aspx?PostId=3644848从具体上来说，.NET元数据机制的设计，既方便了反射等强大特性的实现，又同时给代码安全及程序运行时安全带来了巨大的隐患。迄今为止，还未发现比较有效元数据可见性控制方法。当然，这不在本文的讨论范围之内。我还是更愿意在这篇文章在针对.NET的内存分配机制讨论一个更具体的问题：如何保护在内存中存储的敏感数据？<img src ="http://blog.csdn.net/HeavensDoor/aggbug/3644848.aspx" width = "1" height = "1" />Tue, 30 Dec 2008 17:50:00 +0800HeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644848.aspx#Feedbackhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644848.aspxHeavensDoorhttp://blog.csdn.net/HeavensDoor/archive/2008/12/30/3644848.aspxhttp://blog.csdn.net/HeavensDoor/feed.aspxcsdn.net/HeavensDoor/~7376385/207847546/5485902