史考特部落格園地 - ASP.NET

要學C#或VB.NET

scooter.tw@gmail.com(admin) — Wed,01 Nov 2006 16:00:18 +0800

學習 .NET 的人裡面,有不少人是想寫 Win Form 或 Web Form , 如果您也是這類的初學者或許您不知道該學 VB.NET 或 C#, 我的意見是學習 C#, 原因如下:

1.我以前是學Basic, VBA, VB6, VBScript(ASP), 看的書都是這類的, 別類語言的書籍並不會去看, 但其實有些書是用 Java, C, C++等語言做範例,但對程式開發都極為有用(例如資料結構,物件導向,設計模式,泛型,軟體開發理論), 如果您懂C#, 看這類書就比較沒有困難了(因為語法有些相似,所以閱讀上沒什麼問題)

2.VB.NET, C# 能寫出來的程式,理論上是差不多的, 如果您是Java, C++高手, 相信買本VB.NET入門語法書,熟悉語法及.NET Framework 就可以用VB.NET寫出相當好的系統了, 但如果您跟我相同都只會Basic,或者根本是初學者, 那麼只看市面上的VB.NET 入門書並無法讓您程度有所提升, 但C#入門書裡,不少書籍都對類別,介面,繼承等語法做了較深入的說明, 因此入門者學習C#反而有機會學得比較好, 等到比較熟悉物件的基本用法,再去買上述第一點提的書,能力便比較容易提升

3.當您學習C#,VB.NET語法,並且對於物件,繼承,介面,封裝等知識有了了解之後,之後在學習.NET Frameowrk時都會有不小的幫助,但我個人認為入門者學習C#,才比較有機會打好這個基礎, 您不妨也仔細觀察身邊的朋友,看看有多少人是在沒學好 C,C++或Java之一,而他在只學會VB.NET後,能力居然很好的,我想這種人比例應該是不高的

4.如果您不小心考上了資訊科系,老師也只教VB.NET,為了交份期末作業,那麼您可以直接學VB.NET, 如果您想投入職場,而且不想永遠只是被指派寫點簡單的小程式, 我建議您利用學習C#來打好基礎, 等基礎打好了,即使公司規定只能寫VB.NET,我相信您屆時再多花1,2星期熟悉一下VB.NET 語法後, 寫出來的程式就會很優秀了

5.如果您想學習.NET只是為了開發Win Form, Web Form,我個人建議您的學習方法應該是
A.學習C# 或 VB.NET的基本語法(如果您現在才要學,初學者請不要直接買ASP.NET入門書來學,很容易變成VB.NET/C# 語法不熟的半吊子, 應該去買整本只專門介紹 VB.NET / C# 語法的書)
B.學會如何用C#,VB.NET撰寫簡單的function, class, method, property(這也是 .net 語法入門書要教的內容)
C.學習.NET Framewrok中常用到的class,例如存取資料庫,存取檔案,操控XML,ArrayList, Hashtable等物件(這也是 .net 語法入門書要教的內容)
D.接下來,才是學習Win Form 或Web Form內建控制項的用法(此時,才需要去買ASP.NET的書,學習各控制項如何使用,有些書偏重超級入門,會介紹各控制項如何用,什麼叫Session,Request; 有些書則為了服務1.1升級到2.0的讀者,直接略過這些入門介紹,只介紹2.0新增功能並直接寫些應用範例,各位可以依自己目前程度來挑書)
我相信不少人都是學了A,之後就跳到D,雖然初期看起來很有成就感, 拉一拉就有程式出來,但其實基礎並不好,對於日後程度提升反而是一種障礙

6. 在完成第 5 點的學習,熟悉控制項之後呢? 我覺得應該期許自己朝規劃系統架構著手, 總不能只是一直停留在撰寫 Button Click, GridView.DataBind() 的程度上, 系統有了良好的架構,會讓您覺得開發系統不再是"做苦工",而將重心放在'規劃'上, 您的系統也會變得比較好擴充, 好維護, 甚至程式碼更短更易閱讀

我的結論是:
1.C# 並不能寫出比 VB.NET 還好的程式, 但學習 C# ,會讓您有機會看得懂別類的書籍
2.C#,VB.NET 入門書相較之下,我個人覺得 C# 中文書在介紹物件的部份, 深入程度是比較夠的
3.只要對物件有一定程度的了解, 在能力提升上,是有一定的幫助的
4.如果您有本事經由學習 VB.NET ,卻仍能對物件導向有正確的了解, 仍然可以學習 VB.NET
5.如果您平凡如我,也沒什麼天份,需要靠書籍來學習, 那麼學 C# 會比 VB.NET 好, 因為好書比較多

.NET Framework 3.0 Versioning and Deployment QA

scooter.tw@gmail.com(admin) — Sat,14 Oct 2006 00:46:29 +0800

http://msdn2.microsoft.com/aspnet">

.NET Framework 3.0 Versioning and Deployment Q&A

In June 2006, Microsoft Corporate Vice President S. Somasegar http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx">announced that WinFX would be renamed the .NET Framework 3.0. Check out http://blogs.msdn.com/somasegar/archive/2006/06/09/624300.aspx">his blog post for more information.

This document includes some frequently asked questions about this renaming. For additional questions on deployment, take a look at the http://msdn.microsoft.com/library/en-us/dnlong/html/netfx30.asp">.NET Framework 3.0 deployment paper on MSDN.

Q: What is the .NET Framework 3.0 (formerly WinFX)?
A: The .NET Framework 3.0 is Microsoft's managed code programming model. It is a superset of the .NET Framework 2.0, combining .NET Framework 2.0 components with new technologies for building applications that have visually stunning user experiences, seamless and secure communication, and the ability to model a range of business processes. In addition to the .NET Framework 2.0, it includes Windows Presentation Foundation (WPF), Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and Windows CardSpace.

Q: What happens to the WinFX technologies?
A: The WinFX technologies will now be released under the name .NET Framework 3.0. There are no changes to the WinFX technologies or ship schedule the same technologies you're familiar with now simply have a new name.

Q: How does the .NET Framework 3.0 relate to the .NET Framework 2.0?
A: The .NET Framework 3.0 is an additive release to the .NET Framework 2.0. The .NET Framework 3.0 adds four new technologies to the .NET Framework 2.0: Windows Presentation Foundation (WPF), Windows Workflow Foundation (WF), Windows Communication Foundation (WCF), and Windows CardSpace. There are no changes to the version of the .NET Framework 2.0 components included in the .NET Framework 3.0. This means that the millions of developers who use .NET today can use the skills they already have to start building .NET Framework 3.0 applications. It also means that applications that run on the .NET Framework 2.0 today will continue to run on the .NET Framework 3.0.

Here's a look at the structure of the .NET Framework 3.0:

http://msdn2.microsoft.com/en-us/winfx/aa663314.netfx30.gif" border=0>

Q: What happens when I install the .NET Framework 3.0? How can I upgrade if I already have the .NET Framework 2.0 installed?
A: When you install the .NET Framework 3.0, the installer will check to see whether you already have the .NET Framework 2.0 (released version) installed. If not, the .NET Framework 3.0 installer will install the .NET Framework 2.0 for you, and then install the new .NET Framework 3.0 components. If you do have the .NET Framework 2.0 installed, the .NET Framework 3.0 installer will only install the new components of the .NET Framework 3.0.

Q: My organization went through the approval process of supporting the .NET Framework 2.0 in production. Do we need to go through the same process all over again for the .NET Framework 3.0? Do I need to do any application compatibility testing for my .NET Framework 2.0 applications?
A: Because the .NET Framework 3.0 only adds new components to the .NET Framework 2.0 without changing any of the components released in the .NET Framework 2.0, the applications you've built on the .NET Framework 2.0 will not be affected. You don’t need to do any additional testing for your .NET Framework 2.0 applications when you install the .NET Framework 3.0.

Q: Will the name change be reflected in any of the existing .NET Framework 2.0 APIs, assemblies, or namespaces?
A: There will be no changes to any of the existing .NET Framework 2.0 APIs, assemblies, or namespaces. The applications that you've built on .NET Framework 2.0 will continue to run on the .NET Framework 3.0 just as they have before.

Q: Which version of the Common Language Runtime (CLR) does the .NET Framework 3.0 use?
The .NET Framework 3.0 uses the 2.0 version of the CLR. With this release, the overall developer platform version has been decoupled from the core CLR engine version. We expect the lower level components of the .NET Framework such as the engine to change less than higher level APIs, and this decoupling helps retain customers' investments in the technology.

Q: Why is the .NET Framework 3.0 a major version number of the .NET Framework if it uses the .NET Framework 2.0 runtime and compiler?
A: The new technologies delivered in the .NET Framework 3.0, including WCF, WF, WPF, and CardSpace, offer tremendous functionality and innovation, and we wanted to signal that with a major release number.

Q: How does "Side by Side" work for the .NET Framework 3.0?
A: Since the .NET Framework 3.0 includes only new components that are added to the .NET Framework 2.0 and there is no overlap between the assemblies of the .NET Framework 2.0 and the .NET Framework 3.0, there's no real "Side by Side" scenario. You can run applications based on the .NET Framework 2.0 and applications based on the .NET Framework 3.0 on the same machine.

Q: I'm running an application built on WinFX today. Do I need to do anything different to make it run on the .NET Framework 3.0?
A: No, applications running on WinFX will now run on the .NET Framework 3.0 without any changes. Of course, since the .NET Framework 3.0 is still under development, there may be changes to the framework in the future.

Q: Can I remove particular .NET Framework 3.0 components?
A: No, the .NET Framework 3.0 components (WPF, WCF, WF, and CardSpace) are part of a single package, and are installed together.

Q: Will C# 3.0, VB.NET 9.0, Atlas, or Linq be included in the .NET Framework 3.0?
A: No, these features are planned for future releases of the .NET Framework. The .NET Framework 3.0 includes only the technology formerly described as WinFX.

Q: Will there be a .NET Compact Framework 3.0 release with release of .NET Framework 3.0?
A: No. We are currently working on developing a version of the .NET Framework 3.0 functionality that will be supported on the Compact Framework, but shipping plans and included functionality have not been announced.

Q: What is the version number for the next version of the .NET Framework, codenamed "Orcas"?
A: We're still planning the "Orcas" release, and so this number is not yet defined.

Q: Where is the new functionality in the .NET Framework 3.0 (such as WCF, WF, WPF, and CardSpace) installed to? Is that different from where the .NET Framework 2.0 is installed to?
A: Components shared with the .NET Framework 2.0 are installed at %windir%\Microsoft.NET\Framework\V2.0.50727. Components that are new to the .NET Framework 3.0 are installed to %windir%\Microsoft.NET\Framework\V3.0. Check out the http://msdn.microsoft.com/library/en-us/dnlong/html/netfx30.asp">.NET 3.0 Deployment whitepaper for more information on installation and deployment.

Q: How large is the .NET Framework 3.0? Does this change make the release larger?
A: There's no change to the size of the .NET Framework 3.0 as a result of the name change from WinFX. It is about 49Mb, and that includes the .NET Framework 2.0, which is about 22Mb.

Q: How does servicing work for the .NET Framework 3.0? If I install the .NET Framework 3.0, can I get service updates for the .NET Framework 2.0?
Servicing will be available for the .NET Framework 2.0 components as long both it and the operating system it is installed on are still in service. Any service updates for the .NET Framework 2.0 will work for the 2.0 components installed as a part of the .NET Framework 3.0 as well.

Q: What operating systems will the .NET Framework 3.0 be available for?
A: The .NET Framework 3.0 will be available for and supported on Windows Vista, Windows Server 2003 (SP1), and Windows XP (SP2).

Q: When will the .NET Framework 3.0 be released? A: The .NET Framework 3.0 is included as part of Windows Vista, and customers who get Windows Vista will receive the .NET Framework 3.0. The first release of Windows Vista to business customers is currently planned for November 2006, although the final date will depend on customer feedback.

At the same time, we will make the .NET Framework 3.0 broadly available for download to all customers using Windows XP and Windows Server 2003.

Q: How does the .NET Framework 3.0 relate to Windows Vista? A: The .NET Framework 3.0 is a core component of the Windows Vista operating system, and is installed by default on Windows Vista. It will also be available for Windows XP and Windows Server 2003.

Q: Are there any parts of the .NET Framework 3.0 that only work on Windows Vista? A: Though there are some optimizations in the .NET Framework 3.0 that take advantage of new functionality in Windows Vista, we've striven to provide a consistent experience for the .NET Framework 3.0 across Windows Vista, Windows Server 2003, and Windows XP.

DreamWeaver VS Microsoft Visual Studio 2005

scooter.tw@gmail.com(admin) — Fri,13 Oct 2006 13:50:44 +0800

101 Microsoft Visual Studio 2005 features Compared to Adobe DreamWeaver

Here you have the opportunity to compare features of these products aimed at professional developers. However, Dreamweaver 8 also serves as a tool for professional designers. If you or anyone on your team is a designer, please also explore the designer features of http://www.microsoft.com/products/expression/en/web_designer/default.mspx">Expression Web

對SqlParameter不求甚解？

scooter.tw@gmail.com(admin) — Thu,12 Oct 2006 00:13:05 +0800

你是否曾對SqlParameter不求甚解？我竟然也是... 節錄自【聖殿祭司的ASP.NET 2.0】新書

”不求甚解”一詞，有時是在責備讀書人做學問不夠徹底、一知半解、不求上進等等，對自尊心強或自負的人算是很沒面子，雖然我自認很努力學習.NET相關技術，至少在我自己常用的程式部分應讓瞭若指掌，但我最近發現我在Parameter這個東西上是”不求甚解”，以下是分析：
如果你要新增資料到資料庫，典型的ADO.NET寫法如下：

strSQL1+="TestDate,TestTime,RealDate,ModelTop,ModelDown,Machine) values"; strSQL1+="(@txtTestDate,@txtTestTime,@txtRealDate,@txtModelTop,@txtModelDown,@txtMachine)" SqlConnection conn=new SqlConnection(ConfigurationSettings.AppSettings["SQLConnection"]); conn.Open(); SqlCommand cmd=new SqlCommand(); cmd.Connection=conn; cmd.CommandText=strSQL1; cmd.Parameters.Add("@txtTestDate",SqlDbType.NVarChar,10).Value=myRow["TestDate"]; cmd.Parameters.Add("@txtTestTime",SqlDbType.NVarChar,8).Value=myRow["TestTime"]; cmd.Parameters.Add("@txtRealDate",SqlDbType.NChar,10).Value=new PublicClass().GetDate(); cmd.Parameters.Add("@txtModelTop",SqlDbType.NVarChar,5).Value=myRow["ModelTop"]; cmd.Parameters.Add("@txtModelDown",SqlDbType.NVarChar,5).Value=myRow["ModelDown"]; cmd.Parameters.Add("@txtMachine",SqlDbType.NVarChar,20).Value=myRow["Machine"];
... ... ...

或者你會用傳一段SQL語法用+加字號相連
以上有什麼問題呢？
1.我一直無法明確告訴那些直接帶SQL語法字串的人，不要用字串相加的方法，應該要用SqlParameter
2.我又無法明確告訴他們SqlParameter到底有什麼好處，且SqlParameter字串明顯又臭又長
3.微軟MCSD.NET只教大家用Parameter參數，好嘛！用參數才是純.NET人，我就用吧！
4.國內外的書籍也不曾有作者提過為什麼要用Parameter參數（可能是我看書不夠多）
5.我竟沒想過要去追根究底為何要使用Parameter參數
如此"混"過了好幾年，什麼時候才覺醒？在寫ASP.NET 2.0資料來源控制項時！為何會突然想到？因為被Shock了一下，請看我書中的節錄：
ASP.NET 2.0對於資料控制項參數又增加多達六種參數，我第一次看到心裡只有一個感覺：「天哪，太過份了吧！」以前的Parameter帶參數雖然可以保持彈性，但是程式碼卻比SQL Statement又臭又長，現在微軟竟肆無忌憚地為擴充技術而擴充，把原本一種Parameter變成六個，請問程式設計師不累死才怪，哪裡學得完？以上是直覺想法沒錯，但在發怒前我先冷靜一下給微軟一個辯駁的機會，其實參數除了彈性之外，最重要的理由是「安全性！」所謂的安全性是為了防範SQL Injection的攻擊，而SQL Injection發生的原因有三點：
(1)資料輸入沒有經過驗證，或很薄弱的驗證。
(2)以動態SQL Statement建構SQL命令，讓有心人可隨意傳入SQL命令破壞資料庫（這是非常多的程式設計師通病，請儘量不要使用可接受任意SQL命令方式來設計你的程式，只消一道Drop database命令就可能徹底毀滅掉資料庫）。
(3)使用過大權限的帳號來存取資料庫，而非適度的權限（如程式以sa來進行登入）。
以上三點平心而論你我大家都可能會犯，而且也是許多專案與程式設計師仍然廣泛使用的方式，如此在企業資訊安全當道的時代，若您沒有特別用心防護無異留給駭客一個看似微小卻比天還大的漏洞，一如教育部或聯考放榜十萬考生資料及成績可以被隨意竄改，資訊人員技術簡直是被看笑話，但就我個人觀點並不是安全技術不夠成熟，而是對安全性的投入太少、無知、沒有專家看管或根本無安全性可言，等發生重大機密外洩或資料遭竄改才驚覺安全性風暴已狂捲企業內部，下台的下台、處分的處分，其實可以不必這樣的，現在來看看使用Parameter參數能夠改善些什麼？Parameter參數除了動態提供傳值的作用外，最重要的是它會執行幾項工作：(1)檢查參數的型別(2)檢查參數的長度(3)保證Injected Code在資料庫中會被當成純文字而不是可以執行的SQL命令，因此參數進行了以上三項安全性檢查，將安全性強化到一定水準之上，以下是由Parameter衍生出六種新的參數型態：

從上面的SQL Injection安全性議題及參數又區分成六種更加明確的類型來看，使用新參數型態的確可以大幅增加安全性防護，比如說系統如果接受的是SessionParameter型態，當您餵的是CookieParameter或QueryStringParameter的型態勢必無法成功，或字串長度不合都會被系統擋掉，更別說駭客想用插入SQL命令的方式來攻擊你的資料庫了，故基於以上種種論述，ASP.NET 2.0的新六種參數型態在安全性方面大大加分，與安全性至上前提相較之下，參數的程式碼多寫幾行根本是微不足道的。

看過這篇後，至少我及沒注意到的人不會再不求甚解了^^

節錄自【聖殿祭司的ASP.NET 2.0】新書

被ASP.NET 2.0搶走飯碗的Programmer?

scooter.tw@gmail.com(admin) — Wed,11 Oct 2006 23:53:22 +0800

　　VS2005已經正式推出，很多人都看過ASP.NET 2.0的華麗外表！那些可以自由在頁面上拖曳的WebPart，可以套用版型的MasterPage，可以為頁面穿戴炫華麗衣裳的Theme和skin...。不只如此，大幅節省程式碼的登入控制項群組(包含完整的Forms認證機制、MemberShip和Role類別)，把過去UI(使用者介面)和資料庫存取機制徹底簡化的資料存取控制項(DataSource、和xxxxView字尾的超強控制項)，這些東西讓頁面上的表單維護(master-Detail或電子表單)機制變的幾乎不用寫程式。

　　再加上VS2005對開發環境的大幅改善(SmartTag、程式碼片段、到處都出現的精靈...)，總之，開發人員需要作的事情相對的減少，很多朋友看到之後，第一個問題都是，那...以後程式設計師要做什麼？？？會不會一堆初學者，做出來的網站，都要比累積了很多年的開發老手來的好？難道，很多人就這樣要失業了嗎？或者，又得要放棄才剛學好的ASP.NET 1.1，重新投入2.0的懷抱？(知道嗎？很多公司才剛擬定從ASP轉換到ASP.NET的計劃...)

　　現在台灣市場上，還有為數不少的產品都以ASP來開發，過去在筆者很『熱心的推廣』ASP.NET 1.1的那個時代，已經討論過這個問題。當您(ASP開發人員)，看到其他剛畢業的年輕小夥子，隨手寫出的系統，都比自己用ASP開發了三天三夜的功能還強，這時候情何以堪？這個問題，到了ASP.NET 2.0將會更加明顯。過去ASP.NET 1.1要開發很久(甚至做不出來)的功能，現在到了ASP.NET 2.0很可能已經是基本功能了！相較之下，ASP與ASP.NET 2.0之間的差異則是月來越大，因此對於在業界開發的朋友們，相信很多人早已經自動歸入轉換的跑道了...

　　另外則是採用ASP.NET 1.1作為專案開發的人員(類似筆者這種)。過去我們花了很多心思從ASP轉換到ASP.NET 1.1，沒想到在ASP.NET 1.1才辛苦開發完成的函式庫，到了ASP.NET 2.0後，某些變成基本功能，我要說，心裡除了很X之外，實在也有點佩服微軟，畢竟這是一種進步，過去ASP.NET 1.1上要花長時間才能完成的東西，現在微軟則幫你做好擺在眼前等你享用...

　　有人會說，ASP.NET 2.0這樣的改版，讓很多開發人員越來越不知道系統內部的運作...，我要說的則是，現在很多開發人員，其實從很早以前就已經不知道系統內部的運作了，現在的問題是，開發人員目前所扮演的角色以及他究竟該不該知道系統內部的運作？

　　從不知道什麼時代開始，很多從事軟體開發的社會新鮮人，早已經不知道(也不需要知道)DOS的存在(和它輝煌歷史)，也不知道0與1的意義，但是他們開始會物件導向，開始知道SOA架構，可是卻從沒寫過Client-Server的程式，他們生來系統就已經是那個樣子，程式在Web上面跑的很自然，至於瀏覽器怎麼處理HTML，IIS怎麼處理CodeBehind程式碼，他都覺得這應該不是他的問題...

　　如果你對照ASP.NET 2.0的很多功能，你會發現這個現象異常明顯，從很多角度來看ASP.NET 2.0+VS2005這樣的組合，已經有點像『整合了程式產生器的程式語言』，而新增的很多炫麗套件，則根本有點像是網路上的網站樣板或是模組...，不知道這個現象是否是微軟衝著網路上越來越多的免費資源而來，但是不可否認的，這樣的組合，確實會為很多初階開發人員節省不少時間。

　　回到前面的那個問題，當我們討論到這樣的改變對於程式設計師來說，究竟好不好？筆者除了建議採用其他開發工具(ASP、JSP、PHP...)程式設計師，一定要花點時間來了解ASP.NET 2.0之外(根據筆者的經驗，同時會去涉獵兩種以上開發工具的人真的不多...)，也建議從ASP或是ASP.NET 1.1轉換到ASP.NET 2.0的開發人員必須深思一個問題：『你認為自己未來的角色是什麼？』(是寫程式的人？還是開發系統的人？)

　　根據不知道哪裡的DM，據稱ASP.NET 2.0開發一套系統，比ASP.NET 1.1約減少70%的程式碼，有沒有很誇張？筆者要說，根據我自己測試的結果，雖然不敢說到70%，但是節省的時間絕對超過一半！

　　一半！一半的意思是什麼？一半的意思是，過去老闆要請兩個人，現在只需要請一個！那理論上，ASP.NET 2.0的開發人員應該要比ASP.NET 1.1或ASP要值錢一點，但是，以後當大家都使用這個開發工具，那還玩什麼？我要說的是，程式設計師要注意自己的『Value』！

　　我們回憶一下，當開發一套系統的時候，開發人員花了多少的時間在做商業核心的部分？我們所謂的核心，不是資料庫的基本存取、不是畫面的調整與呈現、不是那些寫過一次之後，另外一隻程式只需要小改一下就可以用了的部分。而是這套系統的核心，例如MRP的物料相關運算，例如CRM的客戶評等運算...等。一套系統裡面，一定有一些商業邏輯，是這個系統裡面最重要的部分，是這個系統要達成的『目的』，其他的環節則都是配合著這個『目的』而來的。資料庫，只是為了存放資料，UI，只是為了讓使用者有個操作環境...，這些其他的東西不是不重要，而是因為模式固定，所以開發的成本越低越好(也就是花的時間和錢越少越好)！

　　從ASP到ASP.NET 2.0的轉變就是這樣(事實上所有開發工具的改版目的都是這樣，從Windows到Java亦是，從VB到VB.NET又何嘗不是！)，請不要忘記，開發一套系統的目的不是要來『讓程式設計師寫程式』，開發一套系統的目的是要來『解決一個問題』。因此系統的重點是能否解決問題，而不是這套系統宣稱花了幾萬個工時，內含幾千隻程式，包含上百個模組...。一個CRM系統畫面做的再漂亮，記憶體使用再精簡，資料庫運算再迅速，找出的目標客戶永遠無效(不購買)那要系統又有何用？

　　時至今日，開發工具已經可以為我們節省絕大部分的時間(特別是花在與程式核心運算無關的開發時間)，因此我們回顧從ASP到ASP.NET 2.0，我們越來越不需要花時間在調整UI、在寫前端JavaScript、版型和版面可以透過MasterPage和Theme快速完成，資料庫存取可以利用DataSource大幅減少程式碼，WebPart可以幫助我們迅速做出一個炫麗的Portal，Login控制項可以讓我們使用現成的會員管理機制...這一切的一切，都只有一個目的，縮短開發人員花在系統『非核心程式碼』的開發時間。

　　整個物件導向程式設計的目的也是，希望程式碼『可重用』，縮短開發時程，讓開發人員專注在開發系統的核心，最理想的狀況或許是，開發人員不要管與系統核心無關的程式，而多花點時間在核心的運算邏輯。回顧一些專案，您會發現，很多時候我們花在『主要目的』的時間遠低於『次要目的』。舉例來說，一套薪資處理系統，計算薪資的程式碼數量(核心功能)，遠低於系統內『產生報表、資料庫存取、使用者介面的調整和控制』(次要功能)的程式碼數量。當然，這些附屬或次要功能不是不重要(當產品的主要功能沒啥特色，人人都可以開發的時候，就會開始比較次要功能，例如我比其他競爭對手多了兩支報表~~哪怕這兩支報表一年只用一次，也會變成產品『特色』)，但是別忘記，從過去的例子我們可以發現，一套系統能構脫穎而出，絕大部分的原因都不是因為次要功能特別強，而是主要功能與眾不同。

　　也因此，開發工具一直在致力做一件事情(事實上，整個軟體工程也一直在做這件事情)，就是讓開發人員花少一點時間在次要功能上，而能夠把省下來的時間，多開發(或研發)一些具有真正價值或與眾不同的主要功能！可能是更強的運算邏輯、更搶眼的創意、更體貼的設計...等。至於只需要花苦工就可以完成的部分，還是交給開發工具(或程式產生器)吧。ASP.NET 2.0所有的新功能，幾乎都是針對這些部分而來，我們期待開發人員，能夠把省下來的時間，投資在更有創意和價值的事情上。

　　甚至，哪怕是把省下來的時間花在多陪陪家人都好~老實說，在台灣寫程式其實真的挺辛苦的，賺的錢不多，工時卻很長，又不受重視，也因此開發人員自我價值的提昇和成長，是很重要的，如果新開發工具的出現，能夠有效的節省我們的時間，那是令人興奮的，但若開發工具的出現，卻取代了你的價值，則是令人感到遺憾的，學習和成長，加上一點點的創意，依舊是奠定自己不變價值的基礎。

Comparison area	Watch the video	Download the video	Read the transcript	Specific features compared
Document Windows & Panels	http://go.microsoft.com/fwlink/?LinkId=68048">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68072">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (33 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/ide_panels/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Start Page http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Split View and Split Screen http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Modifying workspace layout using panels and panel groups http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Saving the workspace layout http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Built-in layouts http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using multiple monitors during development
Code Editors	http://go.microsoft.com/fwlink/?LinkId=68049">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68073">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (25.3 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/codeeditors/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Code Hints / Intellisense http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Selecting and collapsing regions of code http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Inserting server controls into code http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Modifying properties of controls http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Code Snippets http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Compiling server-side code
Components & Toolbox	http://go.microsoft.com/fwlink/?LinkId=68051">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68074">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (15.8 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/componentstoolbox/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Resolving name conflicts between controls http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Adding a control to the Tag Chooser / Toolbox http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using custom controls http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Creating the @Register directive for controls
Design Notes	http://go.microsoft.com/fwlink/?LinkId=68052">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68075">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (7.2 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/designnotes/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Providing Design Notes / Comments in code http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Hiding comments from the end-user http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Finding ToDo comments quickly
Help Features	http://go.microsoft.com/fwlink/?LinkId=68053">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68076">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (11 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/help/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Searching in help http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Context-sensitive help http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Dynamic help that automatically appears while you work http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Online support options
Properties	http://go.microsoft.com/fwlink/?LinkId=68054">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68077">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (16.6 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/properties/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Viewing properties set on an element http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Changing properties of an element http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Viewing style applied to tables http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Modifying properties of multiple controls at once http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Working with events on server controls
CSS	http://go.microsoft.com/fwlink/?LinkId=68055">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68078">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (17.1 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/css/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using the CSS Editor / CSS Panel http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Examining the cascade of styles on a design element http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Code Hint / Intellisense support when defining CSS http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Verifying styles meet WCAG accessibility guidelines
Customizing & Extending	http://go.microsoft.com/fwlink/?LinkId=68056">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68079">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (26.9 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/customizing/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using History to replay actions http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Creating Commands or Macros http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Automating design tasks using Extensions and Macros http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Assigning macros to a keystroke http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Inserting server-side code using Server Behaviors and Snippets
Optimizing Code	http://go.microsoft.com/fwlink/?LinkId=68057">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68080">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (24.2 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/optimizingcode/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Aids to automate creating compliant HTML and XML http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Removal of redundant tags http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Cleaning up extraneous markup from Word http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Customizing the appearance of tags in the editor http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Verification that tags throughout the document are balanced
Templates & Master Pages	http://go.microsoft.com/fwlink/?LinkId=68058">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68081">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (24.1 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/masterpages/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Automatically applying repetitive code http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Creating a Template / Master Page http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Adding pages that utilize a Template or Master Page http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Previewing the appearance of a page that uses templates or master pages http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Administrative overhead of static vs. dynamic pages
Code & Compiling	http://go.microsoft.com/fwlink/?LinkId=68059">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68082">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (28.7 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/codecompile/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using declarative code in a site with Server Behaviors and the Design Surface http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Deploying pages that use server-side code http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Binding a data source to a control http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Writing custom server-side code http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Presenting data from a database http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Discovering features via Intellisense http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Compiled source code has additional features and is less error-prone
Database Support	http://go.microsoft.com/fwlink/?LinkId=68060">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68083">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (21.3 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/databasesupport/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Preparing to make a data-driven Web page editable http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using a DataGrid or GridView to allow editing data in a database http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Creating SQL statements to reference data http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Creating data-driven applications entirely on the design surface
XML & XSLT	http://go.microsoft.com/fwlink/?LinkId=68061">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68084">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (18.3 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/xmlxslt/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Creating XSL transformation files http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Adding constructs to XSLT pages http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Previewing XSLT output http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Rendering XSLT output on a page http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using hierarchical controls with XML
User Controls	http://go.microsoft.com/fwlink/?LinkId=68062">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68085">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (20.3 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/usercontrols/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Editing a User Control http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Previewing how a User Control will render on a page http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Writing the @Register directive required to use a User Control http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Adding custom properties to a User Control that can be programmed with server-side code
Login Controls	http://go.microsoft.com/fwlink/?LinkId=68063">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68086">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (21.7 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/logincontrols/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Login controls in ASP.NET http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Defining custom actions surrounding login controls http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Providing a form for a user to create an account http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Allowing password recovery and reset http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Integration with a standard membership provider
Membership Controls	http://go.microsoft.com/fwlink/?LinkId=68064">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68087">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (22.2 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/membershipcontrols/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Providing an authentication strategy in ASP.NET http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Storing users and roles http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Securing pages with rules http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Redirecting unauthenticated users to a login page
Consuming Web Services	http://go.microsoft.com/fwlink/?LinkId=68065">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68088">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (32.5 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/webservicesconsumer/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Prerequisites to consume a Web service http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Locating an appropriate Web service to consume http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Generating a Web service proxy class http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Making a SOAP call into a Web service http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Establishing asynchronous calls to a Web service
Providing Web Services	http://go.microsoft.com/fwlink/?LinkId=68066">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68089">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (11.2 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/webservicesprovider/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Creating a Web service http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Testing a Web service http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Returning tabular data from a database http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Securing the data exchanged in a Web service
Debugging	http://go.microsoft.com/fwlink/?LinkId=68067">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68090">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (13.2 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/debugging/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Setting a breakpoint http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Editing code during a debugging session, and then continuing to run that code http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Use of visualizers to examine the contents of an object http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Debugging JavaScript
Source Control	http://go.microsoft.com/fwlink/?LinkId=68068">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68091">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (22 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/sourcecontrol/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Shared access provided by file locks http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Comparing multiple versions of a file http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Enabling connectivity to other source control systems through MSSCCI http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Checking out and checking in files http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Enabling rollback to a previous version
WCAG / Section 508	http://go.microsoft.com/fwlink/?LinkId=68069">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68092">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (7.2 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/wcag508/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Filtering manual checklist items out of the WCAG accessibility report http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Analyzing accessibility every time the project is built
Deployment	http://go.microsoft.com/fwlink/?LinkId=68070">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-play.png" width=30 border=0>	http://go.microsoft.com/fwlink/?LinkId=68093">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-download.png" width=30 border=0> (24.6 MB)	http://msdn.microsoft.com/vstudio/products/compare/vs05_dw/deployment/default.aspx">http://msdn.microsoft.com/vstudio/images/vs101_dw/101vs-grid-btn-transcript.png" width=30 border=0>	http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">FTP and WebDAV support http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Secured communication via SSL http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Inherent support for a test environment as well as production http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Using the Publish Website tool to prevent source code from being deployed http://msdn.microsoft.com/vstudio/images/bullet_orange.gif">Convenient installable MSI files for projects
Comparison Area	Watch the video	Download the video	Read the transcript	Specific features compared