As you might already know, the VS2008 VPC will be expired on Nov 1st, the VSTS team is going to release a new VPC with updated expiration date.正如你可能已經知道， vs2008 vpcâ將屆滿， 11月1日， theâ vsts團隊是去釋放一個新的vpc withâ更新的截止日期。  Detail in below, â詳細的下面，

As the final act in our 作為最後的行為在我們的 saga of expiring VPCs 佐賀到期vpcs , I’m happy to announce that we’ve reissued VPCs for VS2008 Beta2 with an updated expiration date.  You can find the updated links on the ，我很高興地宣布，我們已經印發vpcs為vs2008 beta2與更新到期date.â您可以找到更新上的鏈接 VS2008 download page vs2008下載網頁 : ：

• Visual Studio Team System 2008 Beta 2 Team Suite VPC Visual Studio Team System的2008 Beta 2的團隊套房vpc
• Visual Studio Team System 2008 Beta 2 Team Suite & Team Foundation Server VPC Visual Studio Team System的2008 Beta 2的團隊套件＆ Team Foundation Server的vpc

Thanks to everyone that has helped us get the word out about this situation and please accept our apologies for any inconvenience this might have caused you.  Needless to say, we’re taking steps now to ensure that we don’t make this particular mistake again. 感謝大家幫助我們獲得了字對這種情況，請接受我們的道歉的任何不便，這可能造成you.â不用說，我們正在採取步驟，現在，以確保我們不使這個特別的錯誤再次。

Source from來源 Jeff Beehler’s Blog — VS2008 Beta2 VPCs re-released傑夫beehler的博客-v s2008b eta2v pcs重新發布

Last time, I speak in Hong Kong .NET UserGroup Monthly Gathering in 2007 Sept right after MSDN Seminar, the topic was “Experience Sharing: Upgrading ASP.NET 1.x –> 2.0 –> AJAX”.最後一次，我發言在香港。淨usergroup每月聚會在2007年9月後的MSDN研討會，主題是“分享經驗：提升asp.net 1.x -> ” 2 .0- >“ A j ax”的。 Well, I also promised that i will blog about it.那麼，我也承諾，我將博客約。 Actually, it is nothing new and it is nothing special.其實，它只不過是新的，這是沒有什麼特別。 I just shared my experience on how I upgrade ASP.NET 1.1 to 2.0 and how to enable AJAX.我只是分享我的經驗，就如何在我升級asp.net 1.1至2.0 ，以及如何使阿賈克斯。

First, I am not sure if you know that, in .NET framework 2.0, there is 2 types of Web Projects, ASP.NET 2.0 Web Site and ASP.NET 2.0 Web Application.首先，我不知道如果您知道，在。 NET Framework 2.0的，有二類型的Web項目， asp.net 2.0網站和asp.net 2.0 Web應用程序。 You may refer to the following link for more information if you would like to read more.您可參考以下鏈接的更多信息，如果您想閱讀更多資訊。

Introduction to Web Application Projects 介紹Web應用程序項目
http://msdn2.microsoft.com/en-us/library/Aa730880(VS.80).aspx http://msdn2.microsoft.com/en-us/library/aa730880 （ vs.80 ）的。 aspx

If you are going to upgrading your existing ASP.NET 1.x project, you should choose to be using ASP.NET 2.0 Web Application project.如果你要升級您現有的asp.net 1.x項目，您應該選擇要使用asp.net 2.0 Web應用程序項目。 This is the message from one of ScottGu’s blog, Tutorial on VB and C# are also mentioned.這是信息從一個scottgu的博客，補習VB和C ＃中也提到了。

“Because the VS 2005 Web Application Project model has the same conceptual semantics as the VS 2003 Web Project Model, it also makes migrating VS 2003 web projects very, very easy – with zero/minimal code changes “因為與2005年的Web應用程序項目模型具有相同概念的語義，作為與2003年Web項目模型，它也使遷移與2003年Web項目非常，非常容易â € ”零/最小代碼更改

…

Microsoft has announced that support for the微軟已經宣布支持為 F# f ＃ functional programming language will be fully integrated into Visual Studio.功能的編程語言將完全集成到Visual Studio 。 This marks a bold new commitment to facilitating functional programming on the .NET platform and could potentially help legitimize functional programming in enterprise environments.這標誌著一個大膽的新的承諾，以促進功能的節目。 NET平台，並有可能幫助合法化的功能規劃在企業環境中。 Microsoft’s promotion of F# to a fully-supported language in Visual Studio is also indicative of the extreme versatility of the .NET platform and Microsoft’s Common Language Runtime.微軟的推廣的F ＃一個完全支持的語言在Visual Studio也顯示極端多才多藝的。 NET平台和微軟的共同語言運行庫。

F# began its life as a Microsoft Research project to demonstrate the efficacy of .NET as a platform for mixing multiple distinct programming paradigms. f ＃開始它的生命作為一個微軟的研究項目，以展示的效果。淨額作為一個平台，混合多種不同的編程範式。 F# is heavily inspired by the OCaml programming language, and a subset of F# and OCaml are largely compatible. f ＃是大量的靈感，由ocaml編程語言，和一個子集的F ＃和ocaml ，主要是相容的。 F# offers developers many valuable and compelling features without sacrificing much runtime efficiency. f ＃發展提供了許多有價值的和令人信服的功能，在不犧牲很多運行時的效率。 F# supports type inference, pattern matching, high-order functions, and currying. f ＃支持類型推理，模式匹配，高階功能，並currying 。 F# also supports interactive execution, which means that F# programs can be run like scripts or inputted in an interactive top-level environment similar to the Python shell or Ruby’s IRB. f ＃還支持互動執行，這意味著的F ＃程序可以運行像腳本或輸入，在一個互動的高層環境類似的Python殼或紅寶石的內部評級法。 F# also has full access to the .NET APIs and components written in other .NET languages. f ＃也有充分接觸到的。 NET API和組件的書面在其他。 NET的語言。

The advantages of functional programming優勢功能編程

Unlike imperative or procedural programming languages, in which computation is typically performed by altering不像有必要或程序的編程語言，在這種計算通常是由改變

…

Mono單聲道 is the open-source version of Microsoft’s .NET Framework.是開放原始碼版本的Microsoft的。 NET框架。 It implements most of the backend framework features, but unfortunately, falls flat on its pretty little face when attempting to display the user interface - which is what desktop apps are all about.它實現大部分的後端架構，功能，但不幸的是，屬於單位就其漂亮的小時所面臨的企圖，以顯示用戶界面-這是什麼桌面應用程序都是約。

Wine葡萄酒 on the other-hand, is a Linux port of (major parts of) Microsoft’s Win32 library - the core dependencies of the Windows development libraries, and more importantly, the win32 interface elements.對其他手，是一個Linux的港口（主要部分） ，微軟的Win32的圖書館-為核心的相依性的W indows發展圖書館，和更重要的是， W in32的界面元素。 With Wine, you can run many traditional C++ win32 executables on Linux, with certain limitations.與葡萄酒，您可以運行許多傳統的C + +的Win32可執行文件在Linux上，與某些限制。

Mono’s biggest stumbling block is the GUI and .NET programs that use P/Invoke to call native non-managed win32 dlls - Mono is a pure .NET environment, and can’t handle them.單聲道的最大絆腳石是貴和。 NET程式使用P /引用呼籲本土非管理的Win32 DLL的-單是一個純粹的。 N ET環境，並不能處理他們。 But from the description above, that’s exactly what WINE excel at… So can’t we use WINE + Mono to make just about any .NET program run on Linux fresh out of the .NET compiler?但是，從以上的描述，這正是葡萄酒，善於…所以我們不能使用葡萄酒+單聲道，使剛剛對任何。 NET程序在Linux環境下運行的新鮮出來的。 NET編譯器？

Unfortunately, the answer is no.不幸的是，答案是否定的。 Back when the Mono project was first starting out, the Mono development team considered using WINE to implement the System.Windows.Forms namespace of the .NET Framework (which is practically 100% native C++ unmanaged win32 code in .NET wrappers).回時，單項目的第一出發，單聲道的開發團隊考慮使用葡萄酒實施system.windows.forms名字空間的。 NET Framework （這是幾乎100 ％的C + +非託管的Win32代碼在。 NET包裝） 。 But they made the right choice in deciding to not take the easy way and go that route, leaving the integrity of the Mono project intact and focusing on true cross-platform user interface libraries instead (the GTK# is now the UI Library of choice for cross-platform .NET applications).但他們做出了正確的選擇，在決定不採取簡單的方法和走的路線，離開的完整性，單項目的完整和著眼於真正的跨平台的用戶界面，而是圖書館（通過GTK ＃是現在的UI圖書館的選擇跨平台。 NET應用程序） 。

…