visual studio 2005的首映【外文翻譯】

1、<p><b>　　外文翻譯</b></p><p>　　Visual Studio 2005 Premieres</p><p>　　MaterialSource:Visual Studio Magazine Author:Peter Varhol</p><p>　　The question of wh

2、ether to upgrade to Visual Studio 2005 is a no-brainer for many of us. When MSDN releases the new version, we will exercise our subscriptions and install the new IDE. You can import existing Visual Studio 2003 projects a

3、nd have them ready for use within minutes (but don't try going back to your old IDE at that point).</p><p>　　For others the decision is not as easy. It's not so much a question of whether to upgrade,

4、 but when. Most software development groups are unwilling to change IDEs in the middle of a major project. Others believe that if their current tools of the trade are not broken, there is no reason to upgrade them. And t

5、he rest are looking for reasons to move to .NET to begin with</p><p>　　Does Visual Studio 2005 provide these reasons? Further, does Visual Studio 2005 better support the development of high-quality software

6、and the ability to work as a team, out of the box? To answer these questions, I put Visual Studio 2005 to the test, importing projects, creating others from scratch, coding, testing, and prepping for deployment. I also t

7、ook a look at the various flavors of VS 2005 that Microsoft will offer, with an eye toward which audience the specific versions will serve (see </p><p>　　I confined my exploration of Visual Studio 2005 to C#

8、 and Visual Basic. I'm a strong believer in managed code as a quality and productivity enhancer, and a primary reason Visual Studio is what it is today is because it supports development with managed code. That is no

9、t to say that C++, managed or unmanaged, doesn't have a role in application development today, but it continues to be a diminishing role. </p><p>　　Visual Studio 2005 will be readily recognizable and eas

10、ily adopted by veteran developers today. One of the true gifts of the development environment across versions is that developers can pick it up and use it immediately, while learning the new features over time. If you op

11、en an existing Visual Studio 2003 project, a conversion wizard opens automatically to bring it into the new version and ready it for use. There are some small differences in the menus, but any Visual Studio developer wil

12、l be </p><p>　　However, new features abound, and it will take developers a while to find and use many of them. Visual Studio now features the ability to refactor classes and types. While refactoring is an en

13、vironment rather than a language feature, some of the capability is available only for C#. The refactorings available include renaming, moving, and overriding type members; reordering parameters; implementing an interfac

14、e and extracting from a type to an interface; and implementing an abstract class. You ac</p><p>　　The Class Designer can also serve as a starting point for application development, minimizing manual coding w

15、hile making the most from a visual design process. Build a new application by placing classes from the toolbox onto the Designer form, where you can visually add methods, establish class relationships, define interfaces,

16、 and create structures and delegates. The Class Designer makes switching back and forth between visual modeling and coding seamless, with the code and model complementing </p><p>　　It is unfortunate that Mic

17、rosoft has chosen to support a modeling approach different than the widely accepted Unified Modeling Language (UML). Microsoft's class-only approach is an easy and highly usable method of creating class diagrams that

18、 would complement any UML implementation. However, the Class Designer requires you to have a much deeper understanding of your application before beginning. In other words, you might as well use UML as your starting poin

19、t anyway, and simply implement your UM</p><p>　　Using the Class Designer is not the only way you can view a Visual Studio application. The document outline view, available in ASP.NET applications, provides a

20、 treeview of HTML documents that makes it easier to navigate complex Web applications. The Design view shows the elements in the body of the HTML file, and the Source view shows the body elements as well as elements in t

21、he head, the page directive, the script, and code elements. </p><p>　　Visual Studio 2005's Object Browser lets you examine and expand system objects in a treeview. In addition to understanding and workin

22、g with the class structure and methods within each class, it displays the description for all Framework classes and where they reside within the class hierarchy. And it now lets you filter and sort data by namespace, obj

23、ect type, alphabetically, and other characteristics. </p><p>　　Framework Enhancements</p><p>　　While the .NET Framework is not a formal part of Visual Studio, the IDE provides easy access to its

24、 features. The Framework 2.0 has a number of incremental features, including new controls, new databinding, support for generics (implemented in both languages), improved FTP and HTTP support, ClickOnce deployment, a var

25、iety of improvements to ASP.NET, and many more. </p><p>　　In fact, there are too many additions and improvements to detail at any length. Instead, I'll pull out a few for specific mention. The BindingSou

26、rce class improves the manipulation of data. It simplifies the process of databinding between control and data, sitting in between the bound control and the target data source. It helps in managing many databinding issue

27、s such as currency, data-related events, and target data source changes. </p><p>　　The DataGridView control provides a useful and flexible way to display data in a tabular format. ToolStrip controls are tool

28、bars that can host menus, controls, and user controls in WinForms applications. And the WinForms SplitContainer is two panels separated by a movable bar, useful for displaying and browsing information. </p><p&

29、gt;　　For anyone who has to take their application out of Visual Studio and deploy it independently, ClickOnce deployment tries to address issues with versioning of common files, updating of specific files within applicat

30、ions, and permissions issues during application installation. ClickOnce is based on an application manifest and a deployment manifest, both of which are implemented as XML files. As the names imply, the application manif

31、est describes the characteristics of the application itself, and </p><p>　　Developers often wonder about application compatibility across versions of the Framework. Microsoft claims to try to maintain both f

32、orward and backward compatibility across Framework versions, but it occasionally makes changes or deprecates APIs in the name of security, function, or simply because it didn't work right the first time. </p>

33、<p>　　For Framework 2.0, Microsoft has made some APIs obsolete, and makes available a reference for those interfaces. However, to be on the safe side, it makes sense to install the Framework version with which your

34、application was built. I've run both the Framework 2.0 and 1.0 for almost a year with no difficulty in compatibility between applications using different versions. </p><p>　　Of course, Visual Studio 2005

35、 goes hand in hand with Visual Studio Team System (VSTS), the application development lifecycle platform that complements and integrates with Visual Studio in a team development environment. VSTS adds source-code control

36、 (not Visual SourceSafe), static code analysis (FxCop), performance analysis, load testing, and other features to smooth the development process and improve quality. </p><p>　　One innovation is the use of th

37、e rules engine in conjunction with the source-code control system. This makes it possible to enforce best practices as a part of the development process. For example, you can require team members to perform a static code

38、 review with FxCop prior to checking in a file. </p><p>　　While the client portion of VSTS will be available at the same time as Visual Studio, the all-important Team Foundation Server won't ship until n

39、ext spring. Those seeking to integrate their existing development processes with VSTS will have to wait for the arrival of the server. </p><p>　　Looking Ahead to Orcas and Beyond</p><p>　　Micros

40、oft could conceivably take future versions of Visual Studio in many directions. Support for new operating system features is almost a given. And based on some presentations given at Microsoft Professional Developers Conf

41、erence 2005, it appears that the company has chosen working with data as the next mountain to climb. </p><p>　　Orcas (the code name for an upcoming version of Visual Studio that will provide support for Wind

42、ows Vista) will have a pretty quick cycle as far as enterprise development tool sets go. In order to take advantage of some of the new features available in Windows Vista, Orcas must come out at around the same time, now

43、 projected for the second half of 2006. This means that there is perhaps as little as a 12-month turnaround time for Orcas (although there is no doubt that it is already under developm</p><p>　　Windows Vista

44、 (or Longhorn, for those of us who identify more readily with its sobriquet) will introduce a declarative programming model called Extensible Application Markup Language (XAML) that will complement existing programming l

45、anguages and Windows Forms by enabling developers to use the Avalon presentation layer to build the sophisticated mix of Web-like rich-client user interfaces available with the new operating system. Avalon user interface

46、s written with XAML employ some stunning visual</p><p>　　Orcas will also deliver more support for Indigo, Microsoft's new programming model for building Web services. Indigo introduces a unified model fo

47、r developing connected applications on the Windows platform that makes it easier to build service components employing remote procedure calls, messaging, and remote object invocation. Indigo has few fundamentally new Web

48、 service capabilities, but Orcas will provide a far easier way to implement some capabilities, such as security and reliable transacti</p><p>　　From the standpoint of language, the use of data in application

49、s appears to be some low-hanging fruit Microsoft can exploit in that limited amount of time. Many developers write data-driven applications, yet there is little in Visual Studio beyond ADO.NET to make such development ea

50、sy. In particular, while it is possible to build a state-of-the-art graphical user interface visually by selecting from a vast set of user interface components, and write processing logic in VB.NET or C# using convent<

51、;/p><p>　　Orcas seeks to improve on that experience by adding language features to C# that make data handling more seamless. If C# were a data-aware language, for example, you could easily and seamlessly transf

52、er data between the user interface and the database entirely in C#, without necessarily knowing the details of the database tables and fields you are accessing. Consider the improvement in developer productivity and appl

53、ication reliability if you could take a data item directly from a screen object </p><p>　　This goal, in fact, might have been one of the fundamental reasons that Visual Studio and SQL Server have been made a

54、vailable at the same time. The first step in achieving such transparency is to provide the same managed execution environment for both the database and the language. </p><p>　　Other projected features for C#

55、 include extension methods, lambda expressions, type inference, and anonymous type for expressing queries and interacting with objects, XML, and databases in a strongly typed, natural way. For example, the next version o

56、f C# ties in with the .NET Language Integrated Query (LINQ) framework, which will allow you to build queryable APIs.</p><p>　　Much of these projections are speculation at this time, although C# architect And

57、ers Hejlsberg and others at Microsoft have done some speaking on the subject. It is also likely that Visual Basic will continue to return to its roots as a rapid application development language for business-oriented dev

58、elopers. And because software development as a whole is moving in this direction, expect a greater ability to build application models graphically in both languages. </p><p><b>　　譯文</b></p>

59、<p>　　Visual Studio 2005的首映</p><p>　　資料來源: Visual Studio雜志 作者：Peter Varhol</p><p>　　是否升級至visual studio 2005對我們許多人來說是顯而易見的。當(dāng)MSDN發(fā)布新的版本，我們將會行使我們的訂閱并安裝新的IDE。你可以導(dǎo)入現(xiàn)有的visua

60、l studio 2003項目，并讓他們在幾分鐘之內(nèi)就可以使用（但不要回到你的舊IDE這一點上）。</p><p>　　對其他人的決定并不是件很容易的事。但對于是否升級沒有太多的問題。大部分的軟件開發(fā)小組不愿意在開發(fā)一個大項目的過程中改變開發(fā)環(huán)境。有些人則認(rèn)為，如果他們的現(xiàn)有工具沒有被破損，也沒有理由去升級。其余的是正在尋找原因遷移到.net中開始。</p><p>　　visual st

61、udio 2005是否提供這些原因嗎？此外，visual studio 2005是否提供更加高質(zhì)量的軟件和作為一個團(tuán)隊擁有創(chuàng)造性地工作能力？為了回答這些問題,我用visual studio 2005來測試，引進(jìn)項目,從頭開始創(chuàng)建編碼，測試和部署。我也查看了微軟提供的各種VS 2005，瞄準(zhǔn)向大眾服務(wù)的特定版本。微軟提供visual studio的對象很廣，VS 2005工具更加推動它所涉及的領(lǐng)域有企業(yè)團(tuán)隊版本，同時被分解成地區(qū)典型的業(yè)余

62、愛好者，部門和教育為中心的開發(fā)和未來的開發(fā)商。在后者的情形中，微軟實在沒那么多計劃制定新領(lǐng)域像重建一組程序員的關(guān)系那么多并且留下大量的.NET介紹。</p><p>　　我只限于對visual studio 2005中的c#和Visual Basic 的探究。我堅信托管代碼作為一個質(zhì)量和生產(chǎn)力的增強(qiáng)劑，主要的一個原因就是visual studio有現(xiàn)在的發(fā)展是因為它支持使用托管代碼開發(fā)。這并不是說C++，托管或非

63、托管在應(yīng)用發(fā)展的今天沒有了一個角色，但它仍然是一個逐漸衰弱的角色。</p><p>　　Visual Studio 2005將很容易識別并且很容易被資深開發(fā)商采用?？绨姹镜拈_發(fā)環(huán)境中真正的禮物之一是，隨著時間的推移而學(xué)習(xí)的新功能，開發(fā)人員可以撿起來,立即使用它。如果你打開一個現(xiàn)有的Visual Studio 2003項目，轉(zhuǎn)換向?qū)⒆詣哟蜷_新的版本，并準(zhǔn)備使用它。在菜單中有一定的差異，但任何visual stud

64、io開發(fā)者在數(shù)分鐘內(nèi)可提高效率。</p><p>　　然而，新功能比比皆是，開發(fā)者需要一段時間去尋找和使用它們。visual studio現(xiàn)在的特點是重構(gòu)類和類型的功能。重構(gòu)是一個環(huán)境而不是語言特征，一些性能只適用于C#。可用的重構(gòu)包括重命名，移動和突出的類型參數(shù)；重新排序參數(shù)；執(zhí)行一個接口和從一個類型提取一個接口；實現(xiàn)一個抽象類。你完成這些活動并多使用類設(shè)計器，作為一種新型的、獨特的建模工具，可以查看現(xiàn)有應(yīng)用程

65、序類的結(jié)構(gòu)或創(chuàng)建一個類來確定其視覺應(yīng)用程序。你右鍵點擊類設(shè)計器中的類圖選擇你要實現(xiàn)的重構(gòu)類型。類設(shè)計器使圖表中的產(chǎn)生相應(yīng)變化，并在代碼中的自動變化。值得注意的是重構(gòu)過程只是通過圖并不是通過代碼本身。</p><p>　　類設(shè)計器也可以作為應(yīng)用開發(fā)的出發(fā)點，當(dāng)可制作一個可視化設(shè)計最大限度地減少手工編碼。從設(shè)計工具欄拖至設(shè)計窗口建立一個新的應(yīng)用程序，您可以可視化的增加方法，建立類關(guān)系，定義接口，并創(chuàng)建結(jié)構(gòu)和代表。類設(shè)

66、計器使使可視化建模和編碼之間無縫的來回切換，使兩者互補(bǔ)。</p><p>　　不幸的是，微軟選擇支持建模方法不同于被廣泛接受的統(tǒng)一建模（UML）。微軟的類的唯一方法是創(chuàng)建類圖來補(bǔ)充任何UML實現(xiàn)變得更加容易高度可用的方法。然而，類設(shè)計器要求你在開始之前就要非常深入的了解你的應(yīng)用程序。換句話說，總之你可以使用UML作為你的起點，只需要通過類設(shè)計器實現(xiàn)簡單的UML類圖。</p><p>　　使

67、用類設(shè)計器并不是你可以查看visual studio應(yīng)用程序的唯一途徑。該文件的概要點，有效的ASP.NET應(yīng)用程序，提供了一個HTML文件的樹狀視圖，使其更容易瀏覽復(fù)雜的網(wǎng)絡(luò)應(yīng)用程序。設(shè)計視圖中顯示HTML文件正文中的元素，和源視圖顯示在頭部，頁面指令，腳本和代碼元素。</p><p>　　visual studio 2005的對象瀏覽器讓你在樹狀視圖中檢查并擴(kuò)展系統(tǒng)對象。除了理解和處理類結(jié)構(gòu)和每個類方法,它顯

68、示了所有框架類的描述和類的層次結(jié)構(gòu)。現(xiàn)在讓你按字母順序過濾和分類命名空間數(shù)據(jù)，對象類型和其他特點。</p><p><b>　　框架改進(jìn)</b></p><p>　　然而.NET框架不是visual studio正式的一部分，IDE提供方便地訪問到它的特點。該框架2.0有許多增加的特點,包括新的控制、新的數(shù)據(jù)綁定，對泛型的支持（在兩種語言中實現(xiàn)），提高FTP和HTTP

69、的支持，ClickOnce部署，對ASP.NET的多項改進(jìn)措施等等。</p><p>　　事實上，在任何長度有太多細(xì)節(jié)的增加和改進(jìn)。相反，我會拿出一些特別提到的。BindingSource類提高數(shù)據(jù)處理。它簡化了控制和數(shù)據(jù)之間的綁定，在綁定控制和目標(biāo)數(shù)據(jù)來源之間。它有助于管理許多數(shù)據(jù)綁定的問題，如貨幣，數(shù)據(jù)相關(guān)的事件和目標(biāo)數(shù)據(jù)源更改。</p><p>　　DataGridView控制提供了

70、一個有用的且靈活的方式來顯示在一個表格格式中的數(shù)據(jù)。工具欄控件，可以在WinForms應(yīng)用程序中容納菜單欄，控制和用戶控件。WinForms的拆分是兩個面板由一個可移動的欄隔開，可以用來顯示和瀏覽信息。</p><p>　　對任何人都必須采取獨立的其應(yīng)用的visual studio和部署，ClickOnce部署的版本試圖解決共同文件，更新在應(yīng)用程序中特定的文件，并在應(yīng)用程序安裝中出現(xiàn)的權(quán)限問題。ClickOnce

71、是基于一個應(yīng)用程序清單和一個部署清單，這兩者都是作為XML文件被實現(xiàn)。顧名思義，應(yīng)用程序清單描述應(yīng)用程序本身的特點，部署清單描述位置和文件的版本。</p><p>　　開發(fā)人員經(jīng)常想了解跨框架版本的兼容性。微軟聲稱，試圖保持向前和向后跨框架版本的兼容性，但它有時變更或者不贊成接口在安全名義下，或者只是因為它第一次沒有正確工作。</p><p>　　框架2.0，微軟已經(jīng)淘汰了一些過時的API

72、，并且可以給接口提供一個有用的參考。然而，為了安全起見,應(yīng)用程序被建立中安裝框架版本是有意義的。我已經(jīng)運行框架2.0和1.0將近一年的時間里使用不同的版本的應(yīng)用程序在兼容性上沒有困難。</p><p>　　當(dāng)然，Visual Studio 2005與Visual Studio團(tuán)隊系統(tǒng)（VSTS中）齊頭并進(jìn)，應(yīng)用程序開發(fā)生命周期平臺，結(jié)合Visual Studio團(tuán)隊開發(fā)環(huán)境。 VSTS中增加了源代碼控制，靜態(tài)代碼

73、分析，性能分析，技術(shù)性能分析，負(fù)載測試，和其他功能為了順利發(fā)展進(jìn)程和提高質(zhì)量。</p><p>　　一個創(chuàng)新是規(guī)則引擎與源代碼控制系統(tǒng)配合使用。這使得人們有可能執(zhí)行作為開發(fā)進(jìn)程的一部分的最佳做法。例如，你可以要求團(tuán)隊成員執(zhí)行靜態(tài)代碼FxCop之前在同一個文件檢查。</p><p>　　雖然VSTS的客戶端將與Visual Studio在同時間被使用，所有重要的團(tuán)隊基礎(chǔ)服務(wù)器將不會運送直至下

74、一個彈出。那些尋求整合其現(xiàn)有VSTS的開發(fā)程序?qū)⒉坏貌坏却?wù)器的返回。</p><p>　　展望Orcas與超越</p><p>　　可以想象，微軟可能在未來版本的Visual Studio采取許多不同的方向。為新操作系統(tǒng)功能的支持是理所當(dāng)然的。并在2005年微軟專業(yè)開發(fā)者大會上基于基礎(chǔ)的一些介紹，看來該公司已選擇數(shù)據(jù)作為下一個高峰攀登。</p><p>　　Or

75、cas（用于Visual Studio的未來版本將提供Windows Vista的支持代號）將有一個相當(dāng)快的循環(huán)的企業(yè)開發(fā)工具集。為了利用新的功能在Windows Vista中提供的一些優(yōu)勢， Orcas必須在同一時間出現(xiàn)，現(xiàn)已為2006年下半年預(yù)期。這意味著，也許Orcas至少需要12個月的周轉(zhuǎn)時間（盡管毫無疑問，它已經(jīng)在開發(fā)中），所以不要期望太高。</p><p>　　Windows Vista將推出一種聲明

76、性編程模型，稱為可擴(kuò)展應(yīng)用程序標(biāo)記語言（XAML），將補(bǔ)充現(xiàn)有的編程語言和窗體可以支持開發(fā)人員使用Avalon表現(xiàn)層以建立類似Web的客戶端用戶界面上復(fù)雜的混合與新的操作系統(tǒng)。 Avalon用戶界面使用XAML雇用一些驚人的視覺效果，包括三維對象，細(xì)微陰影，透明和重疊對象。</p><p>　　Orcas還將提供更多的Indigo支持，微軟新編程模型的網(wǎng)絡(luò)服務(wù)建設(shè)。Indigo介紹了發(fā)展連接應(yīng)用程序的一種統(tǒng)一模型

77、在Windows平臺上開發(fā)，使得它更容易建立服務(wù)組件遠(yuǎn)程過程調(diào)用，消息傳遞和遠(yuǎn)程對象調(diào)用。Indigo幾乎沒有新的Web服務(wù)功能，但Orcas會提供一個更容易的方法來實現(xiàn)，如安全和可靠的處理。 Indigo的技術(shù)示范表明使用Orcas中Indigo技術(shù)可以減少許多復(fù)雜的工作可以將成千上萬的代碼行簡單化。</p><p>　　從語言的角度來看，在應(yīng)用程序中使用的數(shù)據(jù)微軟可以利用有限的時間可以容易實現(xiàn)。許多開發(fā)人員編

78、寫數(shù)據(jù)驅(qū)動的應(yīng)用程序，但很少有超越的Visual Studio中的ADO.NET使開發(fā)容易。特別是，盡管它有可能建立一個國家的最先進(jìn)的圖形用戶界面直觀地從廣大的用戶界面組件設(shè)置選擇，寫在VB.NET或C＃中使用常規(guī)的處理邏輯編程為輔的綜合性技能幫助系統(tǒng)，數(shù)據(jù)庫訪問需要熟悉數(shù)據(jù)庫的結(jié)構(gòu)，再加上在SQL中的工作能力。</p><p>　　Orcas，旨在改進(jìn)增加C＃語言功能的經(jīng)驗，使數(shù)據(jù)處理更加無縫。如果C＃是一個數(shù)

79、據(jù)感知語言，例如，您可以輕松地，無縫地在用戶界面和數(shù)據(jù)庫之間完全的用C#傳輸，而不必知道您正在訪問數(shù)據(jù)庫的表和字段的細(xì)節(jié)。考慮在開發(fā)效率和應(yīng)用程序的可靠性改進(jìn)，如果你可以采取一個數(shù)據(jù)項無任何中介結(jié)構(gòu)直接從屏幕對象寫入到數(shù)據(jù)庫。</p><p>　　這個目標(biāo)，事實上，有可能是基本原理之一，Visual Studio和SQL Server可在同一時間使用。在實現(xiàn)這種透明度的第一步是提供數(shù)據(jù)庫和語言相同的托管執(zhí)行環(huán)境。

80、</p><p>　　C＃其他功能包括擴(kuò)展方法，Lambda表達(dá)式，類型推斷，以及表達(dá)查詢和對象，XML交互匿名類型，并在強(qiáng)類型的數(shù)據(jù)庫，自然的方式。例如，下一個版本的C＃的關(guān)系中使用.NET語言集成查詢（LINQ）的框架，這將允許你建立可查詢的接口。</p><p>　　在這個時候大部分規(guī)劃是推測，雖然C＃架構(gòu)師Anders Hejlsberg和微軟的其他人做了一些關(guān)于這個問題的發(fā)言。也