[ Thu Jun 26, 07:17:53 PM | ccBoy Henry | new2001@msn.com ]

The CLR and COM versioning rules differ enough to create a huge pile of problems with System.EnterpriseServices (the .NET programming model for COM+). Here's my CLR-flavored update of a number of well-known COM rules that should help staying out of trouble on both ends. From the list one may be able to tell that I am really not a big fan of "automatic" upgrades a la MDAC ... 

Staying sane in a hybrid world: Using Enterprise Services
Clemens' System.EnterpriseServices rules: (a) Interfaces

1. Interfaces are immutable. They cannot change shape, semantics or identity, ever, across space and time. You don't fix interfaces, you create new ones and discard the old ones.
2. Automatic class interfaces (System.Runtime.InteropServices.ClassInterfaceType.AutoXXX) are a great convenience feature. Never use them. 
3. You must use [System.Runtime.InteropServices.GuidAttribute("....")] on every interface declaration you'll ever may want use with System.EnterpriseServices. No exceptions.
4. Managed types draw their identity from their name, namespace and the assembly they are implemented in. An interface's identity may never change, therefore the assembly identity may never change. => Assemblies containing metadata defining interfaces may never change. No version changes, revision numbers, no build-number increments, nothing. They never change.
5. Place interface declarations in metadata-only assemblies that only contain interfaces and lock away the source code in a remote place and forget that place. Compile them once and never recompile.
6. If you want to create derivative interfaces, reference the assembly containing the base interfaces, inherit from the bases and follow #1 - #5
7.-10. Start creating the prototypes for your Enterprise Services interfaces using XML Schema, WSDL and wsdl.exe now and store Schema and WSDL with your project. You will need them later, believe me.

Clemens' System.EnterpriseServices rules: (b) Components

1. Every ServicedComponent must expose all public methods and properties through well-defined interfaces. Period.
2. ServicedComponents are versioned. Managed types are versioned with an assembly-level granularity. If the assembly version changes, the component version changes and that means that for all COM/Interop purposes (and, hence, Enterprise Services) it must get a new Class ID. Rule: Never use [System.Runtime.InteropServices.GuidAttribute("....")] on any ServicedComponent definition. The runtime will keep CLSIDs stable across recompiles (and across machines) as long as the assembly version and the full name of the ServicedComponent (including the namespace) doesn't change and it will change CLSIDs if any of the two change: That's what you want.

Clemens' System.EnterpriseServices rules: (c) Applications

1. Applications are immutable. An Enterprise Services application (Name and AppID) is a well-defined composition of well-known ServicedComponents defined in well-known assemblies.
2. If you have a new version of a ServicedComponent assembly, it's placed into a new application. Unchanged ServicedComponents in the same application (must be from other assemblies) must be aliased into the new application. To make this easier:
3. If multiple assemblies share the same application, their versioning will always be synchronized. If the version of one changes, all others will change versions, too. 
4. Never use lazy registration except when developing. Always install using something like regsvcs.exe /appname:"MyAppName v.1.0.x.x" or the equivalent programmatic tasks using RegistrationHelper.
5. The attributes [assembly:ApplicationIDAttribute(...)] and [assembly:ApplicationNameAttribute(...)] are fantastic for lazy registration. Use them with "#if DEBUG" only or just don't use them.
6. Tell all your buddies that for big apps, "xcopy deployment" isn't cool.
　

[ Thu Jun 26, 06:44:42 PM | ccBoy Henry | new2001@msn.com ]

测试一下 Blogger.com已经很久没有正常的可以WebLog了，非常的愤怒，但是也没有办法，所以只能测试一下了。
另外今天安装了Microsoft 拼音2003，虽然是测试版本，但是非常的稳定和准确，我已经准备卸载我的紫光拼音了。

另外今天看到Blogger已经变了样子非常的漂亮，最重要的是现在开始支持中文了，这对我来说非常的重要：）
但就目前来看，我还没有办法知道如果进行修改这个设置，使它支持我的WebLog界面，另外几乎所有的WebLog客户端工具都不能正常地访问和运行在这个新的Blogger.com上
　

[ Mon Jun 23, 07:39:40 PM | ccBoy Henry | new2001@msn.com ]

http://www.tripleasp.net/bytes.aspx

Processing Large Files with BizTalk Server 2002
This paper and its accompanying sample provide an example of how to process files over 20 megabytes (MB) with Microsoft BizTalk Server 2002.
http://download.microsoft.com/download/3/8/4/384dc9fa-684d-4f3f-bc05-bdc10c4e9043/BTSLFile.exe

http://scottgu.com/
This talk covers what is new and has changed between ASP.NET V1.0 and ASP.NET V1.1.
　

[ Sun Jun 15, 02:48:41 AM | ccBoy Henry | new2001@msn.com ]

IIS 6 resources
Thanks Jeff.

IIS 6.0 Resource Kit Tools
http://microsoft.com/downloads/details.aspx?FamilyId=56FC92EE-A71A-4C73-B628-ADE629C89499&displaylang=en

Whitepapers

IIS 6.0 Feature List
http://www.microsoft.com/windowsserver2003/iis/evaluation/features/default.mspx

IIS 6.0 Technical Overview
http://www.microsoft.com/windowsserver2003/techinfo/overview/iis.mspx

IIS 6.0 Deployment Guide
http://microsoft.com/downloads/details.aspx?FamilyId=F31A5FD5-03DB-46D2-9F34-596EDD039EB9&displaylang=en

IIS 6.0 Features for Server Consolidation

Technical Overview of Windows Server 2003 Application Services http://www.microsoft.com/windowsserver2003/techinfo/serverroles/appserver/appserv.mspx

IIS 6.0 Documentation
http://www.microsoft.com/technet/treeview/default.asp?url=/technet/prodtechnol/windowsserver2003/proddocs/standard/iiswelcome.asp

Webcasts

The Rebuilding of IIS, Version 6.0
http://www.microsoft.com/usa/webcasts/ondemand/1901.asp

Migration to IIS 6 from IIS 4, IIS 5, and Apache 1.3x http://www.microsoft.com/usa/webcasts/ondemand/1722.asp
Isolating and Securing Web applications in IIS 6.0 http://www.microsoft.com/usa/webcasts/ondemand/1721.asp

IIS 6.0 Deployment Overview
http://www.microsoft.com/usa/webcasts/ondemand/1720.asp
　

[ Wed Jun 11, 02:05:33 PM | ccBoy Henry | new2001@msn.com]

Over the years I’ve often said that one of the most effective techniques for increasing a server’s performance is to add memory. Although adding memory typically gets you the most performance bang for your buck, there comes a point when Windows doesn’t use all of the memory that your server has available. Consequently, if Windows hasn’t been configured to use the available memory, then not all of the server’s memory is available to server applications such as SharePoint or Exchange.

By default, Windows 2000 Server will recognize up to 2 GB of memory. If your machine uses an IA32 processor, then you can have way more than 2 GB of memory, but you’re going to have to get Windows to recognize the memory space above 2 GB before you can really use it.

If your server has greater than 2 GB, but less than 4 GB of RAM, then the easiest way of making Windows recognize the new memory is to modify the BOOT.INI file. The BOOT.INI file is a hidden, read only, system file located in the root directory. To modify this file, you must remove the hidden, read only, and system attributes from the file. The easiest way of doing so is to open a Command Prompt window and enter the following command:

ATTRIB C:\BOOT.INI ?CS ?CH ?CR

Once the attributes have been removed, you can use Notepad to edit the BOOT.INI file. When the BOOT.INI file is open, locate the line that loads Windows. The line will look something like:

Multi(0)disk(0)rdisk(0)partition(1)\WINNT=”Microsoft Windows 2000 Server” /fastdetect

At the end of the line add the switch /3GB. This will make the upper memory space available to Windows. When you’re done, the line should look something like this:

Multi(0)disk(0)rdisk(0)partition(1)\WINNT=”Microsoft Windows 2000 Server” /fastdetect /3gb

Now, save your changes and close the BOOT.INI file. At this point, return to the Command Prompt window and enter this command to reset the attributes:

ATTRIB C:\BOOT.INI +S +H +R

Once the attributes have been reset, reboot the server and your upper memory space will be available to Windows. This technique works great if your server has less than 4 GB of RAM. However, if you need for your server to recognize above 4 GB, then there’s a slightly different technique that you must use.

First, keep in mind that only Windows 2000 Advanced Server and Windows 2000 Datacenter Server support above 4 GB of RAM. If you’re using the standard Windows 2000 Server, then 4 GB is the limit.

To make Windows recognize memory above 4 GB, you must use the technique that I presented you with earlier, but rather than using the /3GB switch, you’ll use the /PAE switch. For example, your loader line in the BOOT.INI file would look something like this:

Multi(0)disk(0)rdisk(0)partition(1)\WINNT=”Microsoft Windows 2000 Server” /fastdetect /pae

Just be careful not to use the /3GB and the /PAE switches together. Doing so limits the amount of memory that the operating system uses to 16 GB. While 16 GB is certainly a respectable amount of memory, the /3GB and /PAE switches used together cause any memory above 16 GB to be ignored by Windows.
　

[ Thu Jun 05, 11:54:25 AM | ccBoy Henry | new2001@msn.com ]

Download 巨型文件最佳实践

These articles have upload code that works:
323245 HOW TO: Upload a File to a Web Server in ASP.NET by Using Visual Basic
http://support.microsoft.com/?id=323245

323246 HOW TO: Upload a File to a Web Server in ASP.NET by Using Visual C# .NET
http://support.microsoft.com/?id=323246

For files > 4MB, see this article
295626 PRB: Cannot Upload Large Files When You Use the HtmlInputFile Server
http://support.microsoft.com/?id=295626
　

[ Wed Jun 04, 03:10:39 PM | ccBoy Henry | new2001@msn.com]

我想你不会拒绝这款.NET HTML编辑器
http://www.revjon.com/ftb/Default.aspx
FreeTextBox
A free ASP.NET control written in C# implimenting MSHTML in Internet Explorer. It can be validated using standard ASP.NET validators and has many options for customization. Please purchase one of the following fine products if you will need support (RichTextBox, soEditor, HTML TextBox, ActivEdit, Rich Content Editor. Please see this page for a complete list of other editors).

另外这里还有更多的供你选择:)
http://www.bris.ac.uk/is/projects/cms/ttw/ttw.html


小气的神
2003.06.04
　

[ Thu May 29, 08:36:08 PM | ccBoy Henry | new2001@msn.com ]

htmlArea - Turn any %textarea% into a WYSIWYG editor

http://www.interactivetools.com/products/htmlarea/download.cgi

第一步：到interactivetools下载HtmlArea（目前可供下载版本为2.03，只支持IE5.5以上，3.0版本正在测试）。

第二步：解压后FTP上传到主页空间。

第三步：编辑tmpl/cms目录下的edit_entry.tmpl文档（QinYu说是在tmpl目录下，可能安装的版本不同？），在之间插入如下代码：


注意上面蓝色部分，如果你上传得HTMLAREA不是在/htmlarea那么，请修改_editor_url="你的htmlarea的目录"（注意，这里必须以/结束。）


第四步：同样在之间插入如下代码：


上面蓝色部分的fieldname，请修改为你要改变的textarea（文本输入框的name）。在这里，如果你要改动的是Entry Body，那么，用text替代fieldname，如果是Extended Entry，用text_more替代。

如果两个文本输入框textarea都要修改，那么，请将上面提到的脚本代码在复制一次插入。注意要修改fieldname。

第五步：保存修改后上传。好了，现在进入MT的文本编辑界面，嗯，是不是改变了。不过，尺寸不对。还需要作进一步的修改。


第六步：如果要改动尺寸，那么，在第四步中要加入的脚本应该是如下的：


修改好后上传，好了，现在就可以用了。

HtmlArea可以做更多的自由设定，如果需要自己修改其中的功能，请参看HtmlArea中的readme.html帮助文档。

http://www.cnblog.org/blog/

[ Thu May 29, 08:00:54 PM | ccBoy Henry | new2001@msn.com ]

Evaluate Microsoft Office System 2003 Pre-Release Program
**Do not reply as this email is being sent to you from an un-monitored account. The hyperlink(s) contained in this email may not automatically open your browser. If you experience any difficulty, please copy the link and paste into your browser. **

Email: new2001@msn.com
BetaID: 469267

Hello ?C While we are in the process of getting ready for the upcoming Beta 2 Technical Refresh (more details will be forthcoming soon) we would like to gather feedback about your experiences with the Office System 2003 pre-release program.

Please take a few minutes to complete the Evaluate Office Pre-Release Program Survey listed in the survey link (upper left hand corner) on the BetaPlace website (http://www.betaplace.com).

Your timely response to this survey will help us in planning for the Beta 2 Technical Refresh as well as future Office pre-release programs.

Thank you for your participation in the Microsoft Office System 2003 pre-release program!

The Microsoft Office Team

　

[ Wed May 28, 08:30:44 PM | ccBoy Henry | new2001@msn.com ]

根据微软人士透露，新捆绑型的服务器软件代号为Jupiter，即将在六月底前进入客户测试阶段。这些软件包括了微软专为客户建立商业应用的服务器产品，这可以说是微软在高成长的整合软件市场中的一项里程碑。

　　微软的策略里，至少将三款服务器应用软件捆绑为一套。Jupiter内含了BizTalk Server整合软件，储存与呈现企业文件的Content Management Server(内容管理服务器)，以及建立电子商务网站用的Commerce Server。

　　例如，公司企业可以利用Jupiter软件来将保单的理赔处理流程自动化，自动从后端的各个系统里找出资料，并把文件分送到不同的人那里进行签核。

　　Jupiter将会是微软的重要利器，与.Net网络服务软件一起打入大型企业系统的市场，分析师指出，这块市场过去都是由Java产品的厂商所把持。网络服务是一种标准与程序方法，可以让软件应用更容易交换资料。

　　微软希望(在三年之后)未来所建立的网络服务够坚定可靠，足以处理大规模的运算工作。

　　微软打算利用网络服务来推它的服务器产品与开发工具的销售，Directions on Microsoft的研究总监Rob Helm表示，“除非网络服务可以做到与既有在使用中的技术相当的安全与可靠性，否则大家不会有太高的投入意愿。”

　　微软电子商务服务器的群组产品经理Dave Wascha表示，软件商希望能够达到紧密的整合，以及吸引人的产品价格。同时，微软也希望这项策略能够符合买主在可靠性与容易管理等方面的需求。

　　微软的最大优势之一在于，拥有随时准备妥当的一贯性架构，一贯的开发模组与软件。Forrester Research分析师Ted Schadler表示，Java世界里就没有办法。

　　后来居上

　　在15亿美元产值的整合软件市场里，微软进入相对较晚，这一块领域也将会是软件业里的兵家必争之地。整合软件市场里的一些既有专业厂商，也感受到来自IBM、Oracle，以及BEA等大厂的强大竞争压力。

　　根据Gartner Dataquest的2002年报告显示，IBM在整合中介软件市场里居领导地位，其次则是WebMethods及Tibco两家公司。

　　Schadler表示，Java的中介软件公司通常提供较聪明的软件，让客户用来处理一些较复杂与必要性的运算工作。“但是，现在大家在寻找更好的技术，同时微软也赶搭了这波浪潮。”Schadler表示，“对微软来说，这是个快乐的结合。”

　　根据Gartner的报告显示，虽然IT预算不断在紧缩，但是整合软件是中介软件中成长最快的一块市场，这是因为对IT经理来说，各个应用程序之间的资料分享仍是个让人头大的问题。

　　而微软的网络服务软件的销售，主要都与Visual Studio .Net开发工具密不可分。Jupiter与Visual Studio .Net的结合，可以刺激其服务器软件的销售，因为捆绑在一起之后有助于把.Net应用连结到现有的商业系统上。

　　Jupiter策略的第一阶段里，将导入重新发表的BizTalk软件，这款软件是公司跨部门或是不同的事业伙伴之间，文件与资料的资料发送之用。

　　根据微软的高层指出，全新的BizTalk预计在今年底时可完成，将会是微软服务器软件捆绑策略的基础。即将推出的BizTalk所整合的元件包括有工作流程、管理，以及安全，这些元件也将内建到微软的Commerce Server，以及Content Management Server，藉此可以改进这三种产品之间的关联。而全套捆绑的套装软件将在明年上半年上市。

　　新版的BizTalk将导入以WSBPEL(Web Services Business Process Execution Language，网络服务商业流程执行语言)为基础的企业流程软件，并整合具有更佳的稳定传讯与安全支援的网络服务标准。

　　第二回合

　　Jupiter并不是微软第一次以套装软件方式来卖服务器产品。1990年代早期，微软建立了BackOffice，捆绑了SQL Server资料库、Exchange传讯服务器、应用管理工具，以及其他的软件。但遭到批评指出，个人应用整合不够，而且少有公司想要买整套的BackOffice应用。微软最后在2001年取消了BackOffice的捆绑。

　　微软在次把捆绑策略用在Jupiter上，分析师表示，这一次这些应用的结合已经成熟。公司往往是整合软件、门户网站，以及交易软件分开采购，但是，企业流程可若能够把这些工具结合在一起就会更加顺畅。

　　微软此举将会让专业的整合软件公司(只卖整合产品的公司)面临生死交关问题。例如，曾经享有高成长的Vitria就面临了获利能力的重大压力。去年以来，股价掉到1美元以下了。同时Gartner发现到，Java中介软件公司(对整合软件市场来说还算是新进者)，从去年就开始抢走了专业公司的市场占有率。

　　随然微软没有什么真正的竞争对手，但是微软仍然不可掉以轻心。它在Windows常用的捆绑策略，并非原创的。IBM、BEA、甲骨文等公司都已经建立起“应用平台套装软件”。这些Java服务器软件捆绑了Java 2企业版(J2EE)应用服务器，同时整合了公司门户网站软件以及整合的“中介工具”。

　　微软的服务器软件还缺乏了长久的记录，特别是对那些最必要性的运算工作来说，例如复杂的财务系统或大量的交易网站。相较之下，其他厂商的Java中介软件与专业的整合软件，例如WebMethods与Tibco，都打算要在多操作系统上处理高阶的整合计画。

　　WebMethods认为，Jupiter对于有多种操作系统以及采用不同的程序模式来写应用的公司企业来说，缺乏吸引力。Jupiter对于那些决定百分之百采用Windows产品的中小型企业比较有吸引力，WebMethods商业开发资深副总裁Scott Opitz表示。

　　此外，微软可能还要解决一些棘手的套装软件问题，Wascha表示，公司还在考虑到底今年里要不要先在Jupiter发表之前推出独立版的BizTalk。公司也还没决定是否要内含Host Integration Server，这款软件可从大型主机里拉取资料。

　　Jupiter的售价也未决定，这对微软也是个头痛的问题，ZapThink分析师Ron Schmelzer表示。虽然采购一套服务器产品可能很方便，但是客户可能如果只用到里面的一小部份，可能就会犹疑到底要不要掏腰包。这也是微软当初BackOffice出师不利的因素。

　　不过分析师认为，在微软推出全套的Jupiter套装软件之前，新版的BizTalk也已经够成熟可以让既有整合大厂感受到竞争威胁。微软可利用逐渐成熟的Windows Server 2003操作系统SQLServer 2000企业版本资料库，大幅改善Windows应用的稳定性。

　　借力使力

　　微软在服务器软件竞争中最大的优势之一，在于它在台式机市场里的统治力量，分析师指出。微软的台式机软件力量绝对可以帮助他建立产业级的服务器软件。例如，Visio图表工具将产生其他多步骤商业流程的设计来的BPEL相容程序码。

　　Jupiter还会内含一款所谓的企业活动监视工具，可让使用者利用Excel工作表来观看进行中的商业流程的进度。例如，客服中心经理可以查询工作流程引擎，看看那里进来的电话延迟时间最久。

　　Wascha表示，Jupiter服务器软件将与InfoPath有紧密的结合，这是微软在Office 2003里所加入的软件，可以建立由XLM文件所定义的表格。将此一表格加入Jupiter的XML流程引擎中，用户即可建立一套简易订购商业流程的审核步骤。

　　“微软藉着它在台式机市场的核心优势逐步向上扩展是服务器市场，”Schemizer表示。“这种事情只有微软办得到。”
　

[ Sun May 25, 12:15:07 AM | ccBoy Henry | new2001@msn.com ]

新安装了w.bloggar V3.01 发现它不能很好的支持中文。然后进行了一下修改
先Download http://www.dotnettools.org/download/RICHTX32.OCX
然后去你系统的安装目录
cd \windows\system32
regsvr32 /u richtx32.ocx
copy richtx32.ocx richtx32.ocx.en.bak
copy c:\download\RICHTX32.ocx
regsvr32 Richtx32.ocx

再试一下我想就是支持中文了，这个richtx32.ocx 是我从VS6 中文版SP5中获得的版本.
去这里Download http://wbloggar.com/download/ 这个Blogger工具还不错:)
　

[ Sun May 25, 12:01:20 AM | ccBoy Henry | new2001@msn.com]

HOW TO: Create Keys by Using Visual C# .NET for Use in Forms Authentication
http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b312906

Management (WMI) Extensions for Visual Studio .NET 2003 Server Explorer
http://download.microsoft.com/download/8/9/f/89f0a507-9adc-4217-b465-e565c56e8de9/SESetup.msi

Project: Logging framework for .NET
http://sourceforge.net/projects/log4net
The .NET implementation of the popular log4j Java API providing flexible and arbitrarily granular control over log management and configuration. See http://jakarta.apache.org/log4j/ for more info on log4j.

一段中文测试 w.bloggar V3.01 适合不知道中文

[ Sat May 24, 11:28:41 PM | ccBoy Henry | new2001@msn.com ]

Microsoft F# FAQ
http://research.microsoft.com/projects/ilx/fsharp.htm
http://research.microsoft.com/research/downloads/

香港大学研究人员：果子狸身上找到沙斯病毒
(香港综合电)香港大学研究人员昨天说，追溯沙斯(SARS)病毒的研究取得重大突破，他们已经在野生动物果子狸（civet cat)身上找到了导致沙斯肺炎的冠状病毒。
　香港政府发表的声明说，香港大学研究人员和中国疾病预防控制中心合作研究，“已经成功地从果子狸身上获得了能够引起沙斯的冠状病毒。”
　　声明还说：“这个发现对控制沙斯传染病的蔓延具有非常重要的意义。”
　　沙斯最早于去年11月在中国南方的广东省出现，据知当地的一些野味餐馆甚至提供用稀有或濒危动物烹制的菜肴。
袁国勇说，引发沙斯的冠状病毒比较容易进行基因重组，并从其他冠状病毒获取新的基因组合形式，这就使病毒能够迅速变异，其杀伤力很高。这种病毒很容易发生异变，且极易和猫、狗等动物的过滤性病毒结合重组。
　　袁国勇说，果子狸煮熟后，就不会有病毒。他怀疑病毒是在处理果子狸的过程中传给人的。
实际上，一般的猫身上确实有冠状病毒，但这个冠状病毒只会造成猫感染腹膜炎，不属于沙斯病毒，也不会传染给人类。
　　他说，公众必须清楚认识这一点，因为目前没有人确定家猫或本地的猫感染了导致沙斯的冠状病毒，也没有人确定带菌的猫会把病毒散播开来。
http://www.zaobao.com/gj/zg003_240503.html

Generics for C# and .NET CLR
http://research.microsoft.com/projects/clrgen/
Gyro 1.0 (May 01, 2003) NEW!

Gyro is a set of files that convert an existing installation of the Microsoft Shared Source CLI 1.0 to support generic type definitions and generic methods. Gyro extends the CLI, ILAsm assembler, and C# compiler. It also includes several samples, documentation (in the form of specifications) and some new tests. It does not support generics in the JScript? compiler.

Internet Protocol Version 6 Source code
http://research.microsoft.com/msripv6/
http://research.microsoft.com/msripv6/msripv6.htm

MSN Messener 6.0 Build 0250
ftp://ftp.cableinet.net/store1/incoming/MSN_ieXbeta/MsnMsgs6.rar
http://www.windowsxpstuff.net/msmg6.exe
http://www.iexbeta.com/~abid/files/MSN6.0/build025/MSN.Messenger.6.AdsRemover.XP-vortex.zip
http://www.osbetas.com/forums/index.php?s=7dfc979a1f5a22ebf78d972b608b22db&act=Attach&type=post&id=20550
http://www.ilovemessenger.com/

根据全球点击率最高的网站之一：Google发布的2003年4月的操作系统（OS）使用结果显示，前8位的排名次序依次是Windows 98、Windows XP、Windows 2000、Windows NT、Windows 95、Mac、Linux以及其他的操作系统。
其中，Windows 98的使用人数每月稳步下降1%，而Windows XP的却以同幅度增长。同时，Mac操作系统的使用人数也有下降趋势，从3月份的4%下降到4月份的3%。Linux则稳定保持在1%左右。其他的操作系统，包括微软的操作系统，如Windows ME等，继续保持在4%。


Extending ASP.NET with HttpHandlers and HttpModules - By Bipin Joshi
http://www.devx.com/dotnet/Article/6962/0/page/1

Apache HTTP Server Version 1.3 -- Module mod_rewrite, a URL Rewriting Engine
http://httpd.apache.org/docs/mod/mod_rewrite.html

Apache 1.3 URL Rewriting Guide
http://httpd.apache.org/docs/misc/rewriteguide.html

element at MSDN
http://msdn.microsoft.com/library/en-us/cpgenref/html/gngrfconfigsectionselementcontainertag.asp

Declaring and Accessing Custom Configuration Sections
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpguide/html/cpcondeclaringcustomconfigurationsections.asp

Declaring and Accessing Section Groups
http://msdn.microsoft.com/library/en-us/cpguide/html/cpcondeclaringsectiongroups.asp

Regular Expressions Usage in C#
http://www.c-sharpcorner.com/3/RegExpPSD.asp

Regular Expression Library
http://regxlib.com/

.NET Framework Class Library's Regex.Replace Method (String, String, String)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cpref/html/frlrfSystemTextRegularExpressionsRegexClassReplaceTopic6.asp

Rewrite.NET -- A URL Rewriting Engine for .NET
http://www.15seconds.com/issue/030522.htm
http://www.15seconds.com/files/030520.zip

Project: PurpleSharp
Purple# is one of the first full blown game engines for .NET concentrating on flexibility, programming efficiency and quality using the newest technology. Keywords: DirectX, Scripting, Sound, Cg, CgFx, vertex and pixel shader, 3d
http://sourceforge.net/projects/purplesharp/

Project: HTML Tidy
Dave Raggett's excellent HTML Tidy has found a new home! We're collecting all the bugs and patches posted to html-tidy@w3.org and refactoring Tidy into a free-standing C library.
http://sourceforge.net/projects/tidy

Project: SqlBuddy
SqlBuddy is a tool for use with Microsoft SQL Server and MSDE, written in DotNet (.NET), to facilitate SQL script writing and execution. It is serves a slightly different purpose that of Query Analyser, in that it is aimed to *help* the user write SQL.
http://sourceforge.net/projects/sqlbuddy