.NET大地震冲击IT

原创 2002年05月04日 17:45:00

The.NET Earthquake hits IT

By David Chappell<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

 

The following digest article is adapted from Chapter 1 of
Understanding .NET, A Tutorial and Analysis
by David Chappell. Used with the permission of
the author and Addison–Wesley, 2002. Go to http://www.aw.com/catalog/academic/product/1,4096,0201741628,00.html for more information on this fine book.

<?xml:namespace prefix = v ns = "urn:schemas-microsoft-com:vml" />

 

The world of software development is a volatile place. New ideas appear and are quickly embodied in new technologies. Sometimes those new technologies can be absorbed incrementally, adding to what software professionals already know. Other times, the changes are too great to be introduced as gradual innovations in what already exists. In cases like this, software developers, architects, and managers all experience a fundamental tectonic shift, an earthquake, in their world.

 

Microsoft's .NET initiative is this kind of earthquake. It will affect everybody who works in the Windows environment, and it will generate aftershocks in the wider world, too. By giving us so much change to adapt to at once, Microsoft has made our lives more difficult in the short run—there's a lot to learn. Once we've absorbed this new set of tools and technologies, however, most Windows developers will find themselves capable of building more powerful, more useful software in less time.

 

Defining .NET
Microsoft views .NET as a vision, a platform for the digital future. A more concrete and equally accurate way to think about this initiative is to understand that .NET is a brand, one that Microsoft has applied to several different technologies. Some of these technologies are entirely new, providing new services and new possibilities. Others allow an updated approach to creating the kinds of Windows applications we know today. Still other parts of the .NET family are just new releases of existing technologies dressed up with the .NET brand.

 

The most important new technology in .NET is Web services. As the name suggests, a Web service provides some function that can be invoked programmatically via the Web. Most technologies that carry the .NET brand have direct support for Web services in some way, yet .NET is more than just Web services. The technologies that Microsoft has placed under the .NET umbrella today include the following:

²         The .NET Framework: Includes the Common Language Runtime (CLR) and the .NET Framework class library. The CLR is a standard foundation for building a range of new applications, while the .NET Framework class library provides standard implementations of many new services for CLR-based applications. Among the technologies in the library are ASP.NET, which is the next generation of Active Server Pages (ASP); ADO.NET, the next generation of ActiveX Data Objects; support for building and using Web services; and much more. Microsoft is also releasing a trimmed-down incarnation of the .NET Framework called the .NET Compact Framework. This version is intended for use in smaller devices, such as personal digital assistants (PDAs).

²         Visual Studio.NET: Supports several programming languages that can be used with the .NET Framework. These languages include Visual Basic.NET, which is the next generation of Visual Basic; an enhanced version of C++; and a wholly new language called C# designed explicitly for the .NET Framework.

²         NET My Services: A group of services that allow users to store and access personal information, such as a calendar and address book, on Internet-accessible servers. These services also provide more general features such as authentication, which allows a client to prove its identity, and a way to send alert messages to clients on various devices.

²         The .NET Enterprise Servers: A family of software servers that includes BizTalk Server 2000, Application Center 2000, Commerce Server 2000, Host Integration Server 2000, SQL Server 2000, Exchange Server 2000, Mobile Information Server 2001, and Internet Security and Acceleration Server 2000. In their current releases, these products are largely independent from the other .NET technologies listed here. They don't, for example, make use of the .NET Framework, nor do they provide much direct support for Web services.

Standards for Web services

Web services are an unassailably good idea. Yet if these technologies were supported by Microsoft alone, they wouldn't be very interesting. Fortunately, Microsoft, IBM, Sun, Oracle, BEA, and many other vendors have all endorsed the core Web services technologies of SOAP, WSDL, and UDDI. Some of those technologies have been submitted to the World Wide Web Consortium (W3C) and so are on their way to becoming official standards. For example, the W3C has created an XML Protocol working group. This group now owns SOAP and is working to create the next version of this workhorse protocol for Web services. The key point is that while not all of these Web services technologies are official standards yet, all of them have broad vendor support.

 

Also, none of [these technologies] contains dependencies on Microsoft-specific technologies such as the .NET Framework. This is a little surprising, given that Microsoft was a major player in the creation of each one. Despite the company's less than stellar reputation for conforming to multi-vendor standards, Microsoft seems to have realized that Web services cannot succeed without widespread endorsement. Accordingly, the Web services decision-makers within the Redmond giant have thus far chosen to work with their competitors to make this new technology a multi-vendor reality.

—David Chappell

 

Understanding .NET requires understanding Web services. It also requires grasping at least the basics of each of the .NET technologies listed above.


David Chappell is principal at Chappell & Associates, an education and consulting firm focused on enterprise software technologies. He can be reached via E-mail at david@davidchappell.com.

 

惊爆--唐山大地震的惊天谎言!!!

惊爆--唐山大地震的惊天谎言!!!--预测出来被当时的政府说是谣言2008年05月11日 星期日 22:29      世界上最严重的三个自然灾害(1556年陕西华县的8级大地震,波及面极广,共死亡约...
  • alei8583
  • alei8583
  • 2008年05月19日 23:49
  • 1793

hdu 2189 悼念512汶川大地震遇难同胞——来生一起走

悼念512汶川大地震遇难同胞——来生一起走 Time Limit: 1000/1000 MS (Java/Others)    Memory Limit: 32768/32768 K (Java/O...
  • u013806814
  • u013806814
  • 2014年08月11日 23:48
  • 796

数字信号处理——单位冲击响应

作者:KE meng 链接:https://www.zhihu.com/question/29461110/answer/93942919 来源:知乎 著作权归作者所有,转载请联系作者获得授权。 那...
  • tbl1234567
  • tbl1234567
  • 2016年09月22日 20:11
  • 1843

亲身经历唐山大地震的人生感悟

亲身经历唐山大地震的人生感悟1976年7月28日3时42分53.8秒,河北唐山地区发生8级大地震,遇难者24万余人,重伤者16.4万,轻伤者不计其数。这次地震堪称世界第一大地震。1976年初夏,我带领...
  • yuanmeng001
  • yuanmeng001
  • 2017年07月28日 17:56
  • 475

区块链风暴来袭,这五大行业将受到强烈冲击

自从第一枚比特币诞生以来,加密货币就代表了经济实现重大飞跃的一次机会。尽管比特币出现了,没有中心化的机构,并且成为了传统货币的数字化选择,驱动加密货币运作的底层计算机协议则是从之后才被认为具备大量其他...
  • Ag0JAB
  • Ag0JAB
  • 2017年09月21日 00:00
  • 197

HDU ACM 2187 悼念512汶川大地震遇难同胞——老人是真饿了

原题描述Problem Description 对于幸存的灾民来说,最急待解决的显然是温饱问题,救灾部队一边在组织人员全力打通交通,一边在组织采购粮食。现在假设下拨了一定数量的救灾经费要去市场采购...
  • jjhfen00
  • jjhfen00
  • 2015年11月22日 21:21
  • 517

《大数据的冲击》

第一章 什么是大数据 第二章 支撑大数据的技术 第三章 以大数据为武器的企业(欧美企业篇) 第四章 以大数据为武器的企业(日本企业篇) 第五章 大数据的运用模式 第六章 大数据时代...
  • u013593035
  • u013593035
  • 2015年09月29日 10:42
  • 330

HDU - 2191 悼念512汶川大地震遇难同胞――珍惜现在,感恩生活

悼念512汶川大地震遇难同胞――珍惜现在,感恩生活 Time Limit: 1000MS   Memory Limit: 32768KB   64bit IO Format: %I64d & ...
  • qq_18738333
  • qq_18738333
  • 2015年03月29日 03:00
  • 444

Google谷歌在根据流量统计分析当年的2008年汶川大地震

这是一张2008年的老图,Google当时的博文说道:“当我们依照惯例整理和分析谷歌搜索引擎的流量数据时,一条从未见过的曲线出现在我们面前。当意识到发生了什么事情时,我们的眼睛湿润了。”...
  • qq_21376985
  • qq_21376985
  • 2016年05月14日 12:57
  • 1147

hdu 2191 C - 悼念512汶川大地震遇难同胞――珍惜现在,感恩生活

问题描述 急!灾区的食物依然短缺! 为了挽救灾区同胞的生命,心系灾区同胞的你准备自己采购一些粮食支援灾区,现在假设你一共有资金n元,而市场有m种大米,每种大米都是袋装产品,其价格不等,并且只...
  • qq_31237061
  • qq_31237061
  • 2015年12月27日 23:34
  • 316
内容举报
返回顶部
收藏助手
不良信息举报
您举报文章:.NET大地震冲击IT
举报原因:
原因补充:

(最多只允许输入30个字)