Microsoft.NET BLOG(YunYang): 计算机与 Internet

security 4 ASP.NET -编写安全的ASP.NET应用

Thu, 04 Sep 2008 09:14:18 GMT

Hi,everybody:

I hav't written article for a long period until busy working.As my msn said:"My head grew heavy and my sight grew dim".

so I bring a new session about "security 4 ASP.NET",it will be a series subjects.

Today let me post the vol.1.

Event Log
The Windows event log is probably the most widely known logging facility, and its API is nicely
wrapped in the Microsoft .NET Framework. You simply call EventLog.WriteEntry and pass in the
event source (that is, the name of your application), a message, and an event type (warning, error,
or critical). This will write the event to the application log.
public static void LogToEventLog(string message,
EventLogEntryType type, int id)
{
EventLog.WriteEntry("Accounting Application",message, type, id);
}
An event source must be registered before it can be used. Only an administrator can create new
event sources; the ASP.NET worker process does not have the required privileges to do so. The
easiest solution is to write a simple console application that pre.creates the event source at
application installation time. Afterward, your least privilege daemon account can write to the event
log.
Creating an Event Source
static void Main(string[] args)
{
EventLog.CreateEventSource(args[0], "Application");
}
If you need more control, you can also create your own event log. Name the log after the
application, for example, Accounting Application, and register event sources such as Front End and
Data Access Component.
Creating a Custom Event Log
static void Main(string[] args)
{
string logName = "Accounting Application";
if (!EventLog.Exists(logName))
{
EventLog.CreateEventSource("Front End", logName);
EventLog.CreateEventSource("Data Access Component", logName);
EventLog.CreateEventSource("Financial Component", logName);
}
}
The code for writing to a custom event log changes only slightly.
Writing to a Custom Event Log
public static void LogToEventLog(string message,
EventLogEntryType type, int id)
{
EventLog evt =
new EventLog("Accounting Application", ".", "Front End");
evt.WriteEntry(message, type, id);
}

no end ,just waitting more!

This photo make me remember a lovely girl who give me reailty love,but I hurted her.Sorry!

IIS7管理工具包新特性

Wed, 26 Mar 2008 09:59:35 GMT

IIS要发布最新的管理包了。功能还算不错，添加了网管非常期待的站点初步流量统计功能，具体还是看Soctt的表达吧：

IIS 7 Admin Pack Preview 1 Released

Last week the IIS team shipped the first technical preview of some really cool administration modules that I think web developers will find super useful. This preview adds several new features to the IIS7 Admin Tool:

Database Manager: Built-in SQL Server database management, including the ability to create, delete, and edit tables and indexes, create/edit SPROCs and execute custom queries. Because it is integrated in the IIS administration tool it all works over HTTP/SSL - which means you can use the module to remotely manage your hosted applications (even with low-cost shared hosting accounts), without having to expose your database directly on the Internet.

Log Reports: Built-in report visualization with charting support for log files data. Full range selection and custom chart creation is supported, as well as the ability to print or save reports. Like the database manager you can use this module remotely over HTTP/SSL - which means it works in remote shared hosting scenarios.

Configuration Editor: This is a power module that provides complete control over editing all web.config settings within the admin tool. You can configure it to track the changes you make using the UI and have it auto-generate configuration change scripts that you can then save and tweak to re-run later in an automated way.

Request Filtering UI: This admin module provides more control over the new request filtering feature in IIS7. Check out Carlos' blog post here for details on how to use it.

.NET Authorization: This admin module provides a custom authorization rules editor which allows you to more easily manage the ASP.NET <authorization> configuration section.

FastCGI UI: This admin module provides more support for editing all the new <fastCGI> settings (for when you use FastCGI modules with IIS7 like PHP).

Below are some screen-shots and simple walkthroughs of the Log Reporting and Database Manager administration UI modules:

Log Reporting Admin Module

Have you ever deployed a web application onto a server and wondered how much load it is getting?, what the average response time from the server is?, or whether many server errors are occurring (and if so on what URLs)? All of these settings are carefully logged by IIS in a text based log file. Today most people use command-line tools like the IIS Log Parser utility to query and analyze these files.

The IIS 7 Admin Pack and the new "IIS Reports" admin module now enable you to also query and chart your reports graphically within the IIS admin tool:

Out of the box the "IIS Reports" admin module comes with a bunch of pre-built logparser-based reports that you can easily run on your sites and applications:

Below is a simple graphical report we could pull up that looks at the HTTP status codes being returned by my "TestSite" application (note how we are using the "bar graph" visualization option):

Reports can optionally be filtered using a date range. You can also push the print or save buttons within the report page to generate a printer or a local saved version of the report.

The IIS7 Admin Tool is a rich client application (built using WinForms) - but it does all of its remote access and work using HTTP based web-services that connect to the remote web-server. This means it will work through firewalls, and a hoster does not need to open up ports in their network in order to enable it.

Once a hoster installs the IIS 7 Admin Pack on their web-servers, remote customers managing their hosted sites using the IIS admin tool (which is built-into Vista and available as a download for Windows XP clients) will automatically be prompted to enable the IIS Reports admin module (the install of the client-side module is seamless). They'll then be able to use the reports module inside their admin tool to pull up reports for their remote hosted sites.

Note: hosters can optionally disable this feature if they want, or choose to restrict or customize the list of reports provided. Hopefully most hosters will chose to just make this a standard feature of all IIS and ASP.NET plans they offer.

Database Manager Module

Have you ever deployed your application and database to a remote hosting provider and wanted to make a quick change to the database (but your hosting provider didn't support accessing it using the SQL admin tool)? Using the new "database manager" module within the IIS admin tool you can now remotely access your database and make changes to it using HTTP/SSL through the web-server.

Just connect your IIS administration tool to your remote site and click the new "Database Manager" icon:

By default the Database Manager module will look at the <connectionStrings> section of your web application's web.config file, and allow you to easily access any of the databases your hosted application is using.

For example, below my TestSite application has a "NorthwindConnectionString" setting in the <connectionStrings> section of my web.config (which is why it shows up in my list of connection nodes). When I click it I can view and edit my SPROCs and Table Schema (including indexes):

We could right-click on any table to edit the row data within it, or alternatively perform a custom SQL query to retrieve a custom set of data:

What is nice is that a hoster can easily enable all of the above database admin features for both dedicated and shared hosting plans (even when there are hundreds or thousands of customers on a single server). Like all other modules in the admin tool, all communication between the rich client front-end and the backend at the hoster is done over HTTP/SSL based web-services (meaning it goes through firewalls and doesn't require the hoster to open any new ports - nor expose the SQL server directly on the Internet).

Hopefully this database administration module will just be a standard feature that all IIS hosters enable - which will make remote hosted data management much easier going forward.

Summary

Over time you'll see even more admin UI modules be shipped in the IIS 7 Admin Pack and many more features enabled (Carlos, who runs the dev team building the admin tool, is actively asking for suggestions on what you'd like to see via his blog - so drop him a comment if you have a suggestion or want to provide some encouragement).

You can download the first technical preview of IIS 7 Admin Pack release here as well as learn more about it via the online documentation here. The above modules work with both the IIS7 release in Vista SP1 as well as Windows Server 2008.

正式发布基于VS2008的AJAX模板包

Fri, 21 Dec 2007 02:20:38 GMT

Using VS2008 to Target .NET Framework 2.0 with ASP.NET AJAX

As I mentioned last month, VS 2008 fully supports building applications for .NET Framework 2.0... This is very important as it will take time for some hosters and IT organizations to fully deploy .NET Framework 3.5, but you don't want that to block you from taking full advantage of the cool features in VS 2008.

Today we released ASP.NET 2.0 AJAX Templates for VS2008. This release contains project templates for using Visual Studio 2008 or Visual Web Developer 2008 to create new web sites and web applications with ASP.NET AJAX Extensions features. The project templates contain specific references to assemblies in .NET Framework 2.0 and ASP.NET 2.0 AJAX Extensions 1.0.

Download the ASP.NET 2.0 AJAX Templates for VS2008!

To try these out, make sure you have ASP.NET AJAX Extensions installed, then install the ASP.NET AJAX Templates for Visual Studio 2008.

Then, go to File->New Project and select .NET Framework 2.0 as the target runtime. That will filter down the options and you should see "AJAX 1.0-Enabled ASP.NET 2.0 Web Application". Select it.

Notice the assembly reference in web.config is fixed up to be the 1.0 version number...

 <system.web>
    <pages>
      <controls>
        <add tagPrefix="asp" namespace="System.Web.UI" 
             assembly="System.Web.Extensions, Version=1.0.61025.0, ...
      </controls>
    </pages>

Now you are all set up to get the power of developing with VS 2008, but target .NET Framework 2.0.

关于动态数据的新功能-ASP.NET3.5

Fri, 14 Dec 2007 11:20:54 GMT

最近没时间自己写BLOG,特地转一篇来自ASP.NET之父SCOTT大帅哥的新文章：

New ASP.NET Dynamic Data Support

The ASP.NET 3.5 Extensions CTP we shipped this past weekend contains a bunch of great new features.

One of the cool new features is something we call "ASP.NET Dynamic Data Support". In a nutshell this enables you to really quickly build data driven web-sites that work against a LINQ to SQL (and in the future LINQ to Entities) object model - and optionally allows you to-do this without having to build any pages manually.

The best way to see this in action is to watch David Ebbo's awesome 17 minute screen-cast:

You can also follow the steps below to easily get started and use the dynamic data support:

Step 1: Create a ASP.NET Dynamic Data Site:

Once you have the ASP.NET 3.5 Extensions CTP release installed, you can use VS 2008 or the free Visual Web Developer 2008 Express to create a new Web Site or Web Application Project that has the ASP.NET dynamic data support enabled:

This will create a new web-site you can use that has some default template files in them, along with CSS style-sheets you can use to customize the look and feel of them:

Step 2: Add a LINQ to SQL Data Model to Your Site

LINQ to SQL is an O/RM (object relational mapper) that ships in .NET 3.5, and which allows you to model a relational database using .NET classes. You can then query the database using LINQ, as well as update/insert/delete data from it. LINQ to SQL fully supports transactions, views, and stored procedures. It also provides an easy way to integrate data validation and business logic rules into your data model.

The easiest way to get started with an ASP.NET Dynamic Data site is to add a new LINQ to SQL data model to your project (right-click->add new item->LINQ to SQL Classes item). This will bring up the LINQ to SQL class designer. Drag database tables from your server explorer to define a set of classes (with relationships) for your database schema:

Step 3: Enable Dynamic Templates in Your Project:

By default ASP.NET Dynamic Data projects provide built-in support for creating automatic "scaffolding" views of your LINQ to SQL and LINQ to Entities data models. Dynamic Data projects include template pages and user controls that can automatically create built-in data browsing/editing/selection/deleting UI that is dynamically constructed at runtime based on the LINQ to SQL or LINQ to Entities data model you've added to your project.

To enable this auto-scaffolding support, open the web.config file of your project, search for the "dynamicData" section within it, and set the "enableTemplates" attribute to "true":

Note: this auto-scaffolding feature is currently turned off by default for security reasons (we want you to be explicit about turning it on).

Note: as you can see above, the ASP.NET dynamic data section provides optional URL mapping support that allows you to customize the URLs for your dynamic scaffold pages to be in whatever URL format you want.

Step 4: Run Your Site

Hit F5 to run your project. You'll by default be taken to a default.aspx page that lists all of the table objects in your data model:

Note: the default.aspx home-page is in the project - if you don't like how it looks just open it up and edit it however you want.

Clicking on any of the table names in the list above will take you to a dynamic data page that lists the data within it:

The default data view pages automatically create functional data navigation UI that includes built-in data paging and editing support (and are ASP.NET AJAX enabled):

The data view pages automatically infer relationships between your related objects and provide automatic filtering support:

The data view pages also automatically show relationships between your objects and allow users to easily navigate amongst them. For example, notice how the Category column for products allows me to navigate to the category details for a specific product:

The data view pages also enable automatic selection, editing and delete support. Notice below how when in inline edit mode they automatically infer friendly foreign key names (allowing you to edit the "Category" and pick a name from a dropdownlist instead of having to specify a "CategoryID" integer):

All of this works without having to create a single custom .aspx page or write any custom code. All of the web UI is created dynamically off of your LINQ to SQL or LINQ to Entities data model.

Step 5: Customizing the Site Further

Having all of the above functionality work out of the box against your ORM data model is great for quickly getting your site up and running. Once you get the basic site experience working, you can optionally go in and fully customize it - both at the data validation/business logic level as well as at the UI layer.

You can add standard LINQ to SQL data model and business validation rules to your data model in order to enforce constraints. The dynamic data pages will automatically work off of this logic, and provide appropriate error messages and validation UI based on them.

You can also optionally go in and customize the UI of any of the data pages you want. Dynamic data projects allow you to customize the default look and feel of all data pages on the site, as well as customize the default look and feel of all column types used on the site. You can customize both of these via the default template files added under the "/App_Shared" folder when you create a new dynamic data project:

Simply edit any of the files above to customize the default data page views and/or default data column appearances.

You can also then optionally override the UI of specific data view pages by explicitly adding a .aspx page that maps to it in your project. For example, I could override the default ListDetails behavior for Products by adding a \Products\ListDetails.aspx page to my project:

You can then add any standard ASP.NET data control to the page. You can also use the new dynamic data aware ASP.NET data controls that ship in the ASP.NET 3.5 Extensions CTP to the page. These allow you to completely customize the look and feel of the UI - while still using the new dynamic meta-data provider to infer relationships and meta-data about your data model classes for default behavior.

Try Visual Studio 2008

Mon, 26 Nov 2007 09:19:44 GMT

Try Visual Studio 2008

Microsoft Visual Studio 2008 provides an industry-leading developer experience for Windows Vista, the 2007 Microsoft Office system, and the Web. In addition, it continues in the Microsoft tradition of development language innovation. To enable evaluation of Visual Studio 2008, this page provides links to trial versions of Visual Studio 2008. For more information, see Visual Studio 2008 Product Information.

90-Day Trial Downloads

Visual Studio 2008 Professional Edition (Coming Soon)
Visual Studio Team System 2008 Team Suite
Visual Studio Team System 2008 Team Foundation Server
Visual Studio Team System 2008 Test Load Agent

Current MSDN Professional and Premium Subscribers can download Visual Studio 2008 from MSDN Subscriber Downloads.

In addition, you can download the free Visual Studio 2008 Express Editions and Microsoft .NET Framework 3.5.

Upgrading your ZUNE 1(EST AM 2:30 USA)

Tue, 13 Nov 2007 12:48:33 GMT

For you Zune 30 owners out there, today(EST AM 2:30 USA) you'll be getting the firmware update (woot). Our buddy Jason at Zune Thoughts produced a video detailing the upgrade experience. Check it out:

嫦娥卫星的技术花絮

Tue, 06 Nov 2007 10:46:32 GMT

最近大家都关心嫦娥，今天粘贴点关于嫦娥卫星的技术信息。

FYI FROM YaoFei

对于地面使用的软件，特别是大家在电视上看到的每个人面前的监视终端，是一台运行在Windows2000上的普通PC机，监视软件也是普通的VC编写的，各个型号基本都差不多，在一套代码基础上按照每个型号的遥测处理格式和要求略有一些定制。
大部分软件体制还是脱胎于西安。真正的发指令和接收数据还是靠西安在干活。
型号研制单位自己的测试系统和软件不在此范围内，各种花样都有，运行在自己的总装总测场地。

至于星上的软件，仅对嫦娥而言，主要的数管和姿控导航两个分系统各自使用了一台基于欧洲ERC32处理器的计算机，主频不超过30MHz, 没有通常意义的操作系统，在RTEMS的基础上大幅度剪裁剩下一点点残渣作为底层的硬件和进程管理，上面跑自己的应用软件完成功能。编译器是erc32ccs, GCC的定制版本，支持SPARC V7处理器和RTEMS， ESA提供的，高兴了可以去免费下载玩玩. 有效载荷软件大部分都是基于MCS51的单片机系统，个别设备也许有DSP.
由于前段时间发生了用导弹摧毁FY-1C卫星的事情，国际上已经完全不相信中国所谓气象卫星是民用项目的幌子，给了各种本来就对中国存在敌意的国家和组织以口实，现在想继续买ERC32和欧洲生产的其他星载处理器已经几乎完全没有可能，美国就更不要说了。一些后续型号基本上面临无米下锅的难题。

一些IIS的小提示(针对1.0,1.1的用户)

Wed, 25 Jul 2007 02:34:54 GMT

IIS的修复

注意:此法只是针对1.0,1.1的用户.

一般IIS运行不了ASP.NET,试一下下面四种方法，99％有效：
1。.NET 安装的顺序应该是先装IIS，再装VS.NET，如果次序反了，或者IIS重装了，就需要使用aspnet_regiis.exe -i来重新安装IIS Mapping（主要用于aspx, asmx等文件的Extention的匹配）。在C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705目录下，运行下面的命令：aspnet_regiis.exe -i
2。重设ASPNET的密码，然后在下面的目录中找到Machine.config文件：%Systemroot%\Microsoft.NET\Framework\v1.0.3705\CONFIG （Systemroot是你的安装目录），在<processModel>标识中添加/修改：userName和password3。如果还不行，重装IIS，然后再按照方法1进行操作4。如果你的机器是域控制器，你可以参考Q315158：ASP.NET Does Not Work withASPNET Account on Domain Controller,大致讲一下操作的步骤：
1。在Administrative Tools->Active Directory Users and Computers中建立一个名为ASPUSER的用户，将该用户添加到用户组中（默认情况下已在User Group中）
2。在Administrative Tools->Local Security Settings－>Local Policy->UserRight Assignment中,双击右栏的Log on as a batch job项，在弹出的窗口中点击Add，选择或输入刚才建立的ASPUSER帐号，确定。（需要重启机器）
3。确保ASPUSER帐号有相应文件、目录的访问权限4。在下面的目录中找到Machine.config文件：%Systemroot%\Microsoft.NET\Framework\v1.0.3705\CONFIG （Systemroot是你的安装目录），在<processModel>标识中添加/修改：userName="DomainName\ASPUSER" password="ASPUSERpassword" 其中ASPUSERpassword是刚刚建立的ASPUSER的密码，DomainName是你的域名（重启机器）应该OK了！

ASP.NET 3.5(vs2008)之嵌套母板页

Thu, 12 Jul 2007 21:58:23 GMT

this article came from scottgu.

"Master Page" support was one of the most popular features introduced with ASP.NET 2.0, and is one of those features that almost every new ASP.NET project now uses to deliver consistent layout template support across a web site.One of the cooler scenarios that ASP.NET 2.0 supports is the ability to have "nested master pages" - where you can create a root master page for a site that defines a site's overall layout, and then create nested master pages that are based on the root master and further customize the layout (for example: you could create a SingleColumn.Master and TwoColumn.Master that defined 1 or 2 column layout structures based on the root master template). This nested master page feature is extremely flexible, and enables developers and designers to quickly and very cleanly make changes to the layout and organization of a site with minimal code changes and no content duplication. The one (big) catch, though, is that Visual Studio 2005 doesn't really support using nested master pages, and pages based on nested masters can't be edited within the VS 2005 WYSIWYG designer. The good news is that VS 2008 fully supports nested master pages, and makes using them super easy. Going forward I recommend that almost all ASP.NET projects should advantage of this feature - since it can add tremendous flexibility to the UI of your projects.

Using Nested Master Pages With VS 2008

One of the sites I recommend checking out is http://www.opensourcetemplates.org/. This is an online repository of free HTML site templates that you can browse, download and use. The templates on the site are pure HTML (meaning you can use them with any server-side programming technology), and are built using clean CSS and XHTML markup:

To help with this blog post, I picked one of the templates that I thought looked nice. You can browse it online here, and download it here.

Like most web-sites out there, this template has pages that utilize a few different layout approaches for displaying content. For example, it includes a page that uses multiple-columns to layout content:

It also has pages that use a single column approach that fills the entire width of the page with content:

Using the Above HTML/CSS Template with Nested Master Pages

Converting the above template to use ASP.NET and its nested Master Page support is really easy with VS 2008.

Step 1: Create a Site.Master template

To begin with we can create a new root master page file that we'll use to define the overall layout and structure for all pages on the site. We'll name this file "Site.Master" and copy/paste the "outer chrome" HTML from the template we downloaded into it. We'll then add a <asp:contentplaceholder> into the content section in the middle where we'll fill in page specific content. We'll name this <asp:contentplaceholder> control "MainContent":

Step 2: Create SingleColumn.Master Template

We used our Site.Master template above to define the "outer chrome template" of the site we are working on. We'll now want to create a few nested master pages that provide further templates that customize the layout of the "MainContent" section.

To do this we can right-click in the solution explorer and choose the "Add New Item" menu option. We'll create a new Master Page called "SingleColumn.Master" and will want to make sure that the checkbox indicating that we want to base this master page off a parent master page is selected:

VS 2008 will then allow us to pick the Site.Master template as the master page we want to base this new SingleColumn.master template on:

VS 2008 will then create a new SingleColumn.master file that looks like below:

Notice above how VS 2008 has picked up the fact that we defined a <asp:contentplaceholder> control in the root Site.Master file called "MainContent" - and automatically added a blank <asp:content> control within this nested master page so that we can override and customize that content region...

more details:

http://weblogs.asp.net/scottgu/archive/2007/07/09/vs-2008-nested-master-page-support.aspx

搞计算机该学习的基础

Wed, 27 Jun 2007 21:32:28 GMT

数据结构

操作系统
Ｃ＋＋算法
离散数学

软件工程

数据库

计算机网络

计算机组成原理

没有一项和具体的公司商业技术有关，从这点就说明何谓计算机科学。公司商业技术只是一种社会行为的结果。

隔夜茶

Fri, 04 May 2007 22:25:28 GMT

最近晚上为赶个文档,经常通宵.但喝的茶却是上一天白天所泡,我这种喝法到底算不算隔夜茶啊?隔夜茶有毒啊,我一直对这个问题很疑惑和郁闷..
上等铁观音啊...

另外帮人代招一个白盒测试职位(要求马上去美国)，感兴趣的可以给我邮件:要求如下:

Expert on C#/C++. 2 to 3+ years software developing experience.
Skillful with networking and Active Directory.
1 year experience working in a Windows client/server environment.
1 year development and/or database administration experience using a Microsoft product or Microsoft technologies.
Database programming experience i.e. SQL Server, Sybase.
Bachelor degree in Computer Science and some business/functional knowledge are helpful.
Familiarity with Windows Vista is a help

搞笑的VISTA安装

Sun, 15 Apr 2007 16:22:17 GMT

2006-2007第3次安装VISTA,这次与以往不同,使用VPC2007.出现的问题很搞笑,无法定义硬盘大小,只能采用它默认的64G.....

其实我只有8.7G的剩余空间,居然只能按照64G才能无出错安装!

这种大错误可能导致严重的数据丢失,文件目录索引混乱,存储边界不清,蓝屏等...

这次先凑合用,下次有时间必须重新安装一下.

上图:

深夜随笔(2)

Sat, 07 Apr 2007 19:53:22 GMT

没想到,没想到......今天居然为搞一个爬数据的机器人弄到现在!

起因:

某网站数据对我有至关重要的作用,经过分析其结构和漏洞决定编写一个爬数据的机器人.

BTW:我这个机器人很简陋,很粗鲁,很占用该网站服务器的资源.希望08年某个时候需要和我同时一起查看信息的朋友别怪我,我感觉有点愧疚

过程:

Coding.....

总结:

好久没写了,光动嘴了....感觉没以前猛了,有点发生了....

自我批评:明天一定早点睡觉,找回状态继续"扬短避长",我已经被兄弟给我的书压死了.....

再次感谢周兄的无私...敬礼!

ViewState(from dotnetbips)

Sun, 01 Apr 2007 07:50:26 GMT

Improve performance by compressing ViewState

Introduction

Developers often worry about performance of their web sites. Every developer wants that his web site be optimized for good performance. There are several factors affecting performance of your web site and one of them is ViewState. In this article I am going to show a way by which you can compress ViewState thus improving the performance.

What is ViewState?

Though this article is not intended to illustrate what ViewState is let's quickly discuss it. If you see HTML source of your web forms you will find a hidden form field named __VIEWSTATE. Clever ASP.NET persists control values in this hidden field helping you to preserve them across post backs. No doubt ViewState is helpful. However, at times ViewState can create performance issues. Since ViewState is transferred between browser and server with each request it adds to network bandwidth.

One way to reduce the ViewState data flowing over the wire is to turn ViewState off. All the web server controls have a property called EnableViewState. Setting this property to false will disable ViewState for that control. However, without ViewState all the job of state persistence comes on your shoulders and can be painful at times. Another option, which the theme of this article, is to compress the ViewState before serializing it on the network. This way the amount of data on the wire will be substantially less.

In ASP.NET 1.x people used this compression technique with custom code because there was no inbuilt way. The .NET 2.0, however, makes your life easy by providing System.IO.Compression namespace. The GZipStream class from System.IO.Compression comes handy in compressing and decompressing streams. Note that GZipStream works with only one stream at a time. The GZipStream class is not specifically designed for ViewState as such but we are going to harness its functionality for compressing and decompressing ViewState.

Creating ViewStateHelper

To begin with, create a new web site using Visual Studio. Then add a class called ViewStateHelper in its App_Code folder. At the top of the class import namespaces as shown below:

using System.IO;
using System.IO.Compression;

The System.IO namespace provides stream classes such as MemoryStream. The System.IO.Compression namespace provides GZipStream class that allows you to represent data in gzip format (RFC 1952).

Compressing data

Now add a method called Compress() as shown below:

public static byte[] Compress(byte[] data)
{
MemoryStream ms = new MemoryStream();
GZipStream stream = new GZipStream
(ms, CompressionMode.Compress);
stream.Write(data, 0, data.Length);
stream.Close();
return ms.ToArray();
}

The Compress() static method accepts a byte array to be compressed and returns compressed byte array. It creates an instance of MemoryStream class. The MemoryStream class represents a stream in memory. It then creates GZipStream object by passing MemoryStream and compression mode of Compress. Instead of MemoryStream you could have passed any type of stream. The compressed data is written to this stream. The Write() method of GZipStream class accepts a byte array, compresses it and writes it to the supplied stream (MEmoryStream in our case). After writing the data GZipStream is closed. Finally, ToArray() method of MemoryStream class converts the underlying stream data into byte array.

Decompressing data

In order to decompress data add another method called Decompress() and key in the following code in it:

public static byte[] Decompress(byte[] data)
{
MemoryStream ms = new MemoryStream();
ms.Write(data, 0, data.Length);
ms.Position = 0;
GZipStream stream = new GZipStream(ms, CompressionMode.Decompress);
MemoryStream temp = new MemoryStream();
byte[] buffer=new byte[1024];
while (true)
{
int read = stream.Read(buffer, 0, buffer.Length);
if (read <= 0)
{
break;
}
else
{
temp.Write(buffer, 0, buffer.Length);
}
}
stream.Close();
return temp.ToArray();
}

The Decompress() method accepts byte array of compressed data and returns its decompressed version. First, it creates a MemoryStream and writes compressed byte array to it. This stream is then supplied to GZipStream constructor. Notice that this time compression mode is Decompress. The decompressed data also needs to be stored somewhere. The code creates another MemoryStream for this purpose. A while loop reads decompressed data from GZipStream in the chunks of 1024 bytes at a time. This data is then written to the MemoryStream. Finally, GZipStream is closed and contents of decompressed MemoryStream are returned to the caller as byte array.

This completes the ViewStateHelper class. Now you need to put this class in use for compressing and decompressing ViewState.

Creating a web form

Now open the default web form and drag and drop one SQL Data Source control on it. Configure it to select all records from Customers table of Northwind database.

Drag and drop a GridView control and set its DataSourceID property to the ID of SQL Data Source control you just configured. Run the web form so as to ensure that it is working as expected. The following figure shows a sample run of the web form

Customizing ViewState serialization

Most of the times you don't interfere with ViewState serialization and deserialization mechanism at all. However, since you wish to compress the ViewState you need to customize the way ViewState is serialized and deserialized. The Page base class has two virtual methods viz. SavePageStateToPersistenceMedium() and LoadPageStateFromPersistenceMedium(). Together they allow you to customize ViewState serialization and deserialization respectively.

Go in the code behind of the web form and override SavePageStateToPersistenceMedium() method first. You will compress ViewState and store it in a hidden variable in this method. The following code shows this method.

protected override void 
SavePageStateToPersistenceMedium(object state)
{
LosFormatter formatter = new LosFormatter();
StringWriter writer = new StringWriter();
formatter.Serialize(writer, state);
string viewState = writer.ToString();
byte[] data = Convert.FromBase64String(viewState);
byte[] compressedData = ViewStateHelper.Compress(data);
string str = Convert.ToBase64String(compressedData);
ClientScript.RegisterHiddenField("__MYVIEWSTATE", str);
}

The SavePageStateToPersistenceMedium() method accepts an object that represents the ViewState data. Inside it creates LosFormatter object. The LosFormatter class allows you to serialize and deserialize data in ViewState compatible format. The Serialize() method of LosFormatter class accepts a stream where data is to be serialized and the state object. In our example we serialize the data into a StringWriter. The ToString() method of StringWriter returns a string that represents ViewState data in string form. This string data is in Base64 format (this how ASP.NET stores the ViewState)and need to be converted into a plain string. The FromBase64String() method of Convert class does this job. The return value of FromBase64String() method is a byte array which is then compressed using Compress() method of ViewStateHelper class. The compressed byte array is again converted into its Base64 representation using ToBase64String() method of Convert class. Finally, a hidden field named __MYVIEWSTATE is emitted using RegisterHiddenField() method of ClientScript member with its value set to the compressed Base64 string.

Compressing ViewState data is just one side of the coin. Equally important is to decompress it back so that ASP.NET can work with it further. This is done by overriding LoadPageStateFromPersistenceMedium() method as shown below:

protected override object 
LoadPageStateFromPersistenceMedium()
{
string viewstate = Request.Form["__MYVIEWSTATE"];
byte[] data = Convert.FromBase64String(viewstate);
byte[] uncompressedData = 
ViewStateHelper.Decompress(data);
string str = Convert.ToBase64String
(uncompressedData);
LosFormatter formatter = new LosFormatter();
return formatter.Deserialize(str);
}

The method retrieves __MYVIEWSTATE hidden field from Form collection. This field contains compressed version of the ViewState in Base64 format. In order to decompress it you need to convert it into a byte array first. This is done via FromBase64String() method of Convert class. Then Decompress() method of ViewStateHelper decompresses the data. The decompressed data is again converted into a Base64 string using ToBase64String() method of Convert class. Finally, LosFormatter instance deserializes the decompressed ViewState.

That's it! Your ViewState compression scheme is now ready. During my testing I observed that the uncompressed ViewState was 13,568 bytes whereas the compressed ViewState was 5,932 bytes. A great deal of saving. Isn't it?

Summary

In this article you learnt to improve performance of your web forms by compressing ViewState data. The new GZipStream class offers a ready made way to compress data in gzip format. The compressed ViewState needs to be saved by overriding SavePageStateToPersistenceMedium() method of Page base class. Similarly, LoadPageStateFromPersistenceMedium() needs to be overridden for decompressing and loading the ViewState back.

程序员与现实生活(原创)

Wed, 07 Mar 2007 03:12:34 GMT

程序员与现实生活(原创)

作者:杨云(YunYang)

转载请注明出处:http://aspnet.spaces.live.com

经常听很多人讨论普通软件开发人员吃青春饭干不到30岁就要转行的讨论,一些人觉得真实,一些人反对.

反对的人认为这是高技术行业,不是体力劳动,只要有技术可以干一辈子(这里叫反方).同意的人认为社会目前就是这个状况,过30就没人要.(这里叫正方).

我觉得他们都忽略了2点:

1.这里说的Coding或者软件开发一般商业性质的公司,商业行为.所使用的技术也都是依靠某个商业公司平台下的技术,比如Microsoft,Sun.

2.这里说的Coding或者软件开发不是在做基础研究,只是商业开发.

注意到没有,就凭借上面的2点,可以证明两方面都是有偏激的.真正没有这个天赋的人,一般在1年内甚至更短时间会被软件行业淘汰,不可能坚持那么长时间.

先说第一点,既然作为一个在公司以打工为生的程序员,就需要时刻保持技术的新鲜.听起来很容易,做起来是很痛苦的,除了工作外要把几乎所有的业余时间砸在上面.作为一个普通程序员加班是家常便饭,有时间可能连续数月.... 这就不简单是个人问题了,程序员也是人,也要有时间和人接触,特别是结婚的同志们就不用说了,你老婆能理解你天天对着PC,不理她吗? 如果是大龄程序员压力就更大了,还要面对年轻人的冲击,要继续混下去只能选择时刻保持先进性...和和.

如果你老婆或者女朋友理解你,支持你,只是默默的给你倒上一杯茶....恭喜你,你太有福了,你是幸运的,有家人的支持,你所向披靡!

按照我看到的,超过30岁的程序员无提升选择转行的,一般并不是因为没人要了,而是自己选择放弃.干不动了.....这个干不动有时也无奈,人精力有限的,高强度的工作性质加上要照顾家庭,甚至小孩,大部分人只能选择放弃....

说自己有技术就可以干一辈子的,我们可以走着瞧,,是不是这样的....和和..不要嘴硬...

再说第二点,说自己过了30就没人要的或者不符合条件的.先不说技术是否跟上了,先说心理上有为你从事的行业去奋斗的决心吗?有不怕寂寞,敢于挑战困难的决心吗?面对周围人的不理解,骂你无能,说你呆傻,没时间找老婆的处境等..你能坚持吗?

如果你能做到,我想不要说一个工作,就是做大师级的人物也只是时间问题.

特别是持正方观点的人,其实外界给他们大压力是很大的.

有谁见过机关公务员搞计算机的人说自己到30了,要转行了?有吗?我想没有,,,为何?道理很简单,没有太大压力,不管是自身还是来自单位都是.干的好干的坏一样拿工资吃饭.(就比如某单位的计算机处和网络检查处,,我几年前去实习过,我想读我文章的很多牛人的战斗力可以抵他们一个处的能力和工作量)

请问.社会打工可以这样吗?你如果坚持要做,我上面列出的问题就是你要去解决的..你做的到吗?

说了那么多,其实就是要告诉大家,要做这个行业就好好做,这个行业是注定与孤单,黑夜相伴的.不想做就趁早转行,不需要找那么多理由,这不丢人.凭劳动吃饭到哪里都是大写的"人".

ASP.NET2.0 Page lifecycle(MasterPages)

Wed, 14 Feb 2007 12:10:31 GMT

THIS DOCUMENT I PICK UP FROM CODEPROJECT,ITS IMPORTANT FOR .NET DEVELOPER.

SUMMARY:ASP.NET2.0 Page lifecycle,specially we use masterpage in our application.

Introduction

Understanding Page lifecycle is very crucial in order to develop ASP.NET applications. Most beginners tend to get confused while dealing with dynamic controls and face problems like losing values, state etc on postbacks. Since HTTP is stateless, the nature of web programming is inherently different from windows application development, and the Page lifecycle is one of the primary building blocks while learning ASP.NET. The sequence of events, especially while working with MasterPages in ASP.NET 2.0, has become slightly more complex and this article is aims to shed some light on these events by explaining the order and importance of each event.

Background

Whenever the user requests a particular .aspx page in an application, a lot of interesting things happen on the web server where the application is hosted. Understanding this sequence of events will help us to program and respond to events properly and also clear any confusion which generally arises due to the stateless nature of web programming.

Basics: The New Compilation Model and the Partial Classes

Each web form in an ASP.NET application derives directly or indirectly from a System.Web.UI.Page class. A web form has two components: a code behind file (WebForm.aspx.cs) which contains the code for the events and other methods related to a Page, and the designer ASPX file, which contains HTML control declarations and events (in the Visual Studio 2005 Web Application project model, we have a designer class named WebForm.aspx.designer.cs).

In ASP.NET 2.0, we do not need to define the control variables as well as there event handlers in the code behind, thanks to Partial classes. In ASP.NET 1.x, all this code was auto generated and placed in the code behind file under InitializeComponent() section. But in version 2.0, the runtime will create a partial class dynamically from the ASPX page containing all this info and merge it with the code behind partial class. This will help in making the actual code behind class a lot cleaner and more manageable.

Also, this would eliminate the name change related issues which were common in VS 2003 (if we change any control's ID, it had to be changed everywhere and VS used to modify the code many times). All control related events are defined in the ASPX markup code. So having a single place for controls names and event handlers is cleaner and flexible, whereas the previous VS 2003 model was more "brittle".

Real Thing: The Page life cycle

It is very important to know that for each request, the Page class is instantiated everytime from “scratch”. Which means that any values or whatever state it had previously will get lost unless we use one of the various state maintainance mechanisms provided by ASP.NET like Application, Session, Cache variables or Cookies.

Side Note: View state in ASP.NET 2.0 has changed and now comprises of two parts: Control State and View state. Refer this article for details:

http://msdn2.microsoft.com/en-us/library/1whwt1k7(VS.80).aspx

Below is the sequence of events which fire up sequentially with explanation on the relative importance with respect to web programming in code behind:

Important Note: All events except the Init() and Unload() are fired from outermost to the innermost control. For e.g., a user control’s init event would fire before the Page_Init() event of its parent Page class.

1. PreInit()

In this Page level event, all controls created during design time are initialized with their default values. For e.g., if you have a TextBox control with Text property = “Hello”, it would be set by now. We can create dynamic controls here.

This event occurs only for the Page class and UserControls/MasterPages do not have this method to override.

Sample code where you can override this method and add your custom code:


protected override void OnPreInit(EventArgs e)
        
{
            //custom code            
           base.OnPreInit(e);
 }

Note that PreInit() is the only event where we can set themes programmatically.

Special Case with MasterPages

It is important to note that Master Page is treated like a control in the Content Pages.
So if a Page has a Master Page associated with it, then the controls on the page will not be initialized and would be null in this stage. Only after the Init() event starts, you can access these controls directly from the page class. Why?

The reason being that all controls placed in the Content Page are within a ContentPlaceholder which is a child control of a MasterPage. Now Master Page is merged and treated like a control in the Content Pages. As I mentioned earlier, all events except the Init() and Unload() are fired from outermost to the innermost control. So PreInit() in the Page is the first event to fire but User Controls or MasterPage (which is itself a Usercontrol) do not have any PreInit event . Therefore in the Page_PreInit() method, neither the MasterPage nor any user control has been initialized and only the controls inside the Page class are set to their default values. Only after the Page_PreInit() event the Init() events of other controls fire up.

See the diagram below showing control hierarchy after the Page_Init() event:

2. OnInit()

In this event, we can read the controls properties (set at design time). We cannot read control values changed by the user because that changed value will get loaded after LoadPostData() event fires. But we can access control values from the forms POST data as:


string selectedValue = Request.Form[controlID].ToString();

3. LoadViewState

This will only fire if the Page has posted back (IsPostBack == true). Here the runtime de-serializes the view state data from the hidden form element and loads all controls who have view state enabled.

4. LoadPostBackData

Again, this method will only fire if the Page has posted back.
In this event the controls which implement IPostBackDataHandler interface gets loaded by the values from the HTTP POST data. Note that a textbox control does not gets its value from the view state but from the post data in the form in this event. So even if you disable view state for a particular control, it can get its value from the HTTP POST data if it implements IPostBackDataHandler interface.

Also, an important point to note is that if we have a DropDownList control and we have dynamically added some items to it, the runtime cannot load those values unless the view state is enabled (even if the control derives from IPostBackDataHandler). The reason being that HTTP Post data has only one value per control, and the entire value collection is not maintained in the PostData but in view state.

5. Page_Load

This is the most popular method and the first one for all beginner developers to put their code. Beginners may also think that this is the first method which fires for a Page class. This can lead to a lot of confusion which makes understanding the Page lifecycle all the more important.

Note: If the page has any user control, then it's Load method will fire after the Page class's Load method. The reason as explained earlier is the fact that all method except the Init() are fired from the outermost control to the innermost. So after Page_Load(), load methods of all other controls are fired recursively.

6. Control Event Handlers

These are basically event handlers (like Button1_Click()) which are defined for controls in the ASPX markup. Another source of confusion arises when the developer thinks that an event handler like Button_Click() should fire independently (like in windows apps) as soon as he clicks a Button on the web form, forgetting that Page_Load will fire first before any event handlers.

7. PreRender

This event is again recursively fired for each child controls in the Page. If we want to make any changes to control values, this is the last event we have

to peform the same.

8. SaveViewState

Here, the ViewState of the controls gets saved in the form's hidden control.

9. Render

In this method all controls are rendered recursively (i.e. Render method of each control is called).

10. Unload

Here you can have the page and controls perform clean-up operations. This event has no relevance besides clean up operations because the Page has already rendered.

Dynamic Controls

Now we have seen the important events in the Page lifecycle, let's focus on how to create and maintain state of dynamically generated controls. Many times we need to generate controls dynamically for specific business use cases. For example, I was managing a famous hotel reservation website project and one of my team members was facing an issue in handling the Reservation screen. There was a TextBox where the user enters the number of
rooms, and based on that value, dynamic usercontrols having a room's detailed info were created at runtime.

The developer complained that although he was able to generate user controls as runtime in a for loop, but was unable to save their state. When I looked into the code, I noticed that the code to generate controls was written in a Button's Click event handler. Now as we dicussed above, event handlers like Button_Click() fire much later than LoadViewState() and LoadPostData(), where the control values get loaded from the view state and form's Post data.

So unless he recreates the controls in the Page_Init() or Pre_Init() methods (which occur before LoadViewState and LoadPostData), the control values modified by the user won't get reloaded next time.

Now, when he put the code in the Page_Init() event, he was unable to get the number of rooms entered by the user in the TextBox (which was a static control). The reason being that in Page_Init(), control values are initilized to their design time default values, and do not reflect the user entered values unless they are loaded from the POST data or the view state, a process which occurs later.

So the only way to access the user entered value in the control is to get the value from the form's POST data. Here is the code:


protected override void OnInit(EventArgs e)
    
{
          //get value of the TextBox from HTTP POST data
        
 string selectedValue ; 
         if(Request.Form["txtNoOfRooms"] != null)
               selectedValue = Request.Form["txtNoOfRooms"].ToString();
           

          //code to create controls dynamically...
     ...............
          
base.OnInit(e);
    }

Note: Thanks to Mike Banavige of ASP.NET forums, I added this section. If you create a dynamic control in the Page_Load event, and add it to a PlaceHolder or Panel (with view state turned on), then this dynamic control will maintain its state even though it was not created in the Page_Init(). Why?

The reason is the fact that once a control is added to the control tree of the page, TrackViewState() method is responsible for tracking the state. This method gets fired automatically whenever the control is added to the control tree. Due to this reason, any modifications to the control (like adding items etc) should be done *only after* the dynamic control has been added to the control tree of the Page class, else the state would be lost. See the code below:

protected void Page_Load(object sender, EventArgs e)
{
  //create a dynamic dropdown

DropDownList d = new DropDownList();

PlaceHolder1.Controls.Add(d); // TrackViewState() gets fired for our dropdown, so state is maintained

if (!IsPostBack)

{

d.Items.Add("test1");
d.Items.Add("test2");

}

}

This will not work:

protected void Page_Load(object sender, EventArgs e)
{
//create a dynamic dropdown
DropDownList d = new DropDownList();
if (!IsPostBack)
{
d.Items.Add("test1");
d.Items.Add("test2");
}
PlaceHolder1.Controls.Add(d); //"test1" and "test2" values are lost
}

As a beginner

Mon, 12 Feb 2007 15:51:18 GMT

guys:

This post wrote for beginner.

1.As a beginner,if u like to simulate from the others or samples project,i think u should go on.Its a nice action for beginner.

2.As a beginner,I think u should be do more practices.Everyday or a period,I sugguest u to assume a new theme and develop it as soon as possible.

But this theme should be suitable for yourself and be prone to implement.

ps:keep going at everyday

3.As a beginner,maybe u be good at coding or deisgn,but u must be know waht is the most important for a company.u should be master the spirit of team.

Maybe u are working at a small company,hmmmm.Dont worry about that,who can say this is forever for u?

4.As a beginner,if u can get a chance into big company,u should grasp it.dont worry about treatment,become u can learn more new ways ,technology ,management and so on.

ps:more requests and more money come from pile.

5.As a beginner,U should be use sample way to solve problem.such as write cleanly codes is important than magnify methods.

6.As a beginner,dont use pattern&design in anywhere and anytime.

YunYang

Bill Gates说工作方式

Sat, 10 Feb 2007 09:29:25 GMT

最近看Bill Gates探究工作方式.其中提到关于技术研发人员Desktop部分.提到在Coding时拥有两台LCD的员工工作效率要提高5%,拥有3LCD的提高9%.可谓是立竿见影的办法,但很多中小公司由于财力,认识度等等原因不能做到.

由于显示面积增加了一倍，我们可以方便的穿梭于不同的窗口，完成不同的工作，而不会再像从前那样总被不同的窗口遮挡住。

我个人倒觉得如果我是管理层一定会立即推行.因为这些的效率提高是非常明显的,一次投资终生收益.

弱依赖智能家庭之设备篇一

Thu, 08 Feb 2007 03:00:04 GMT

弱依赖智能家庭之设备篇一

密码智能门锁固名思义，只要按下用户原来设好的密码，就可以打开房门，操作简单安全.

型号：M1313

主要功能：
01、通道功能:可用密码将门锁设置为通道状态
02、密码最多可以为9位数字---密码为0-9数字任意组合
03、欠压提示：自动提示用户更换电池
04、应急开锁：可利用机械钥匙进行开锁
05、密码保险：连续按错密码3次，报警1分钟，在该段时间内各键自动停止功能

太阳能发电机组:

太阳能发电机系统实际的负载是150瓦，用一个电视机和两个灯可以点4-5小时。机器尺寸22*14.5*43 cm 10公斤太阳能板和机器分开的板的尺寸是 80*54*3cm，板的瓦数是50瓦。

100W
1. 太阳能电池板 100W, 2. 300W 控制逆变器一台 3. 需自配 12V/100AH 蓄电池一个
日照一天可储电 29A , 可供 100W 电器使用 5 小时

太阳能发电机组按照电视机功率110W看,4小时没问题

...等续

Webpart 数据库的迁移

Tue, 26 Dec 2006 09:34:33 GMT

和和...到埃塞俄比亚去支援非洲兄弟的老童依然在战火纷飞的时间不忘开发,果然让我敬佩,特此POST他的血肉贴...老童要坚强...哈哈哈

Webpart是asp.net 2.0中一项非常出色的功能，但是非常遗憾的是，默认是使用sql express 2005作为后台数据库。而且很多初学者在本机写完程序迁移到服务器上以后才如梦初醒，原来还要后台数据库的，甚至WROX出的《Professional ASP.NET 2.0》在讲webpart这节时都不曾提及后台数据库的事，真是让人失望之极（起码我没看到）。而目前主流的网站都是用MS SQLServer 2000或是Access作为数据库，如何才能把Webpart的数据库从SQL Express 2005迁移到SQLServer 2000和Access呢？

迁移到SQLServer 2000

微软提供了一个数据库配置程序，可以方便的在SQLServer2000和SQLServer2005上进行webpart的数据库配置。

1.首先运行SQLServer

2.然后运行C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe 会出现一个图形化的操作界面，根据提示便可自动生成一个名为aspnetdb的库。

3.打开vs.net 2005，新建一个网站，往页面上拖一个webpartmanager,运行一下,出错。因为你还没有配web.config呀，而且vs.net2005与vs.net2003有所不同，默认是没有web.config文件的,需要我们自己增加，(当然你也可以直接修改C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG下默认的web.config，但是我不推荐)。

4.在新加的web.config中把 <connectionStrings/>一行修改成如下

<add name="LocalSqlServer" connectionString="Data Source=localhost;Initial Catalog=aspnetdb;Persist Security Info=True;User ID=sa;Password="

providerName="System.Data.SqlClient" />

</connectionStrings>

完成后的web.config为

<?xml version="1.0" encoding="utf-8"?>

<!--

注意: 除了手动编辑此文件以外，您还可以使用

Web 管理工具来配置应用程序的设置。可以使用 Visual Studio 中的

“网站”->“Asp.Net 配置”选项。

设置和注释的完整列表在

machine.config.comments 中，该文件通常位于

\Windows\Microsoft.Net\Framework\v2.x\Config 中

-->

<system.web>

<!--

设置 compilation debug="true" 将调试符号插入

已编译的页面中。但由于这会

影响性能，因此只在开发过程中将此值

设置为 true。

-->

<!--

通过 <authentication> 节可以配置 ASP.NET 使用的

安全身份验证模式，

以标识传入的用户。

-->

<!--

如果在执行请求的过程中出现未处理的错误，

则通过 <customErrors> 节可以配置相应的处理步骤。具体说来，

开发人员通过该节可以配置

要显示的 html 错误页

以代替错误堆栈跟踪。

</customErrors>

-->

</system.web>

</configuration>

迁移到Access

将webpart的数据库迁移到sqlserver是一件非常方便的事，但是对于很多小型网站来说,access才是最佳选择。但是要将数据库迁移到Access却是一件非常的复杂的事情, 而且网上也没有查到这方面现成的中文资料,之前在微软英文asp.net新闻组发了个贴子也没人回答，有些英文资料也是语焉不详,不成系统。

下面我来说一下详细的过程。

首先你需要一个access的Provider以及相对应的数据库。之前我曾经从网上找了一个access的provider，并尝试把SQLServer版的表导出成Access，结果发现这条路是行不通的,因为不匹配。

目前在英文google里能找到两个access的Provide

一个是AccessPersonalizationProvider，下载地址是

http://www.kowitz.net/files/AccessPersonalizationProvider.zip

命名空间为MarkItUp.SingleUserBlog.Web.WebParts.AccessProviders 虽然在源代码注释里也写着copyright是微软的,但是下载时没有对应的数据库。

另外一个是微软官方网站上的以前Beta1时出的 SampleAccessProviders,解压后自带一个access数据库，而且还有web.config的样例。下载地址是

http://msdn.microsoft.com/vstudio/eula.aspx?id=96713a8e-b8d4-4d6e-bb8f-027e6c8e15d8

我用的是后者。

下载后，名字是SampleAccessProviders.vsi，解压缩后可以在C:\Documents and Settings\Administrator\My Documents\Visual Studio 2005\Templates\ProjectTemplates\Visual Web Developer\Starter Kits\ASP.NET Access Providers 找到。

你可以用vs.net2005打开Access.csproj编译出dll,名字为SampleAccessProviders.dll，然后把ASPNetDB.mdb复制到App_Data目录，然后在自己的网站中引用SampleAccessProviders.dll，并参考那个web.config修改自己的配置文件。

关于其他数据库

由于SampleAccessProviders是开放源代码的，所以参照着自己扩展Provider。目前网上可以找到XmlFilePersonalizationProvider。对于Oracle,mysql等数据库可以自己写扩展Provider，但是目前我们已有了access这种数据库独立的方式，所以可以通过混用来实现更为方便。