從sharepoint到aspnet 20 webparts------外文翻譯.doc
約12頁DOC格式手機(jī)打開展開
從sharepoint到aspnet 20 webparts------外文翻譯,古老而又智慧的諺語說“時(shí)間就是金錢”，及時(shí)和有針對(duì)性地獲取你所需的信息是節(jié)約時(shí)間和金錢的關(guān)鍵。如今的網(wǎng)站需要提供一個(gè)數(shù)量超級(jí)龐大的信息，但在單一的頁面上呈現(xiàn)過多的內(nèi)容只會(huì)導(dǎo)致混亂。模塊化頁面布局和個(gè)性化的內(nèi)容是提高用戶滿意度和生產(chǎn)力的關(guān)鍵。如果經(jīng)理每個(gè)早晨都需要審查一套特定的數(shù)據(jù)集，你應(yīng)該為她提供的是那套沒有修飾而且易...
內(nèi)容介紹
此文檔由會(huì)員 wanli1988go 發(fā)布
古老而又智慧的諺語說“時(shí)間就是金錢”，及時(shí)和有針對(duì)性地獲取你所需的信息是節(jié)約時(shí)間和金錢的關(guān)鍵。如今的網(wǎng)站需要提供一個(gè)數(shù)量超級(jí)龐大的信息，但在單一的頁面上呈現(xiàn)過多的內(nèi)容只會(huì)導(dǎo)致混亂。模塊化頁面布局和個(gè)性化的內(nèi)容是提高用戶滿意度和生產(chǎn)力的關(guān)鍵。如果經(jīng)理每個(gè)早晨都需要審查一套特定的數(shù)據(jù)集，你應(yīng)該為她提供的是那套沒有修飾而且易于訪問的數(shù)據(jù)。這就是為什么互聯(lián)網(wǎng)門戶網(wǎng)站依舊存在的原因。
在Windows世界中，SharePoint使產(chǎn)品和技術(shù)簡化，并支持在一個(gè)公司或組織與合作伙伴之間各種形式的合作?；赟harePoint的Web站點(diǎn)的網(wǎng)頁包含一個(gè)名為WebParts的專用附件用于特定的設(shè)計(jì)提供個(gè)性化和可定制的窗口信息給用戶。最后，WebParts是一個(gè)特別的代碼層而且它們是能與SharePoint框架有相互作用的ASP.NET控件。到目前為止一切順利。那么Whidbey的和.NET框架的下一個(gè)版本將會(huì)怎樣？
From Sharepoint to ASP.NET 2.0WebParts
“Time is money” an old and wise proverb says, and getting the information you need timely and at-your-fingertips is the key to save time and subsequently money. Today’s Web sites have a super-huge quantity of information to offer, but presenting too much content on a single page only leads to confusion. Modular page layouts and personalized contents are the key to increase user satisfaction and productivity. If a manager needs to review a given set of data each and every morning, you should be able to serve her just those data with no frills, and in an-easy-to-access way. That’s why Internet portals exist.
In the Windows world, SharePoint products and technologies simplify and support various forms of collaboration between partners within a company or an organization. The pages of a Web site based on SharePoint can contain special components named WebParts which are specifically designed to provide personalized and customizable windows of information to users. In the end, Web Parts are ASP.NET controls with an extra layer of code that make them interact with the SharePoint framework. So far so good. What about Whidbey and the next version of the .NET Framework?
ASP.NET 2.0 comes with a built-in portal framework that brings two significant benefits to the table. First, it dramatically reduces the investment for building ASP.NET portal solutions. Second, it provides a consistent model for building ASP.NET-based portals.
在Windows世界中，SharePoint使產(chǎn)品和技術(shù)簡化，并支持在一個(gè)公司或組織與合作伙伴之間各種形式的合作?；赟harePoint的Web站點(diǎn)的網(wǎng)頁包含一個(gè)名為WebParts的專用附件用于特定的設(shè)計(jì)提供個(gè)性化和可定制的窗口信息給用戶。最后，WebParts是一個(gè)特別的代碼層而且它們是能與SharePoint框架有相互作用的ASP.NET控件。到目前為止一切順利。那么Whidbey的和.NET框架的下一個(gè)版本將會(huì)怎樣？
From Sharepoint to ASP.NET 2.0WebParts
“Time is money” an old and wise proverb says, and getting the information you need timely and at-your-fingertips is the key to save time and subsequently money. Today’s Web sites have a super-huge quantity of information to offer, but presenting too much content on a single page only leads to confusion. Modular page layouts and personalized contents are the key to increase user satisfaction and productivity. If a manager needs to review a given set of data each and every morning, you should be able to serve her just those data with no frills, and in an-easy-to-access way. That’s why Internet portals exist.
In the Windows world, SharePoint products and technologies simplify and support various forms of collaboration between partners within a company or an organization. The pages of a Web site based on SharePoint can contain special components named WebParts which are specifically designed to provide personalized and customizable windows of information to users. In the end, Web Parts are ASP.NET controls with an extra layer of code that make them interact with the SharePoint framework. So far so good. What about Whidbey and the next version of the .NET Framework?
ASP.NET 2.0 comes with a built-in portal framework that brings two significant benefits to the table. First, it dramatically reduces the investment for building ASP.NET portal solutions. Second, it provides a consistent model for building ASP.NET-based portals.
