Microsoft patterns & practices is excited to announce the latest addition to the p&p library of software architecture guidance: Unity Application Block April 2008 Release (1.0)    Resources ·          MSDN site: http://msdn2.microsoft.com/en-us/library/cc468366.aspx ·   Community Forum: http://codeplex.com/unity

About the Deliverable

The Unity Application Block (Unity) is a lightweight, extensible dependency injection (DI) container. It facilitates building loosely coupled applications and provides developers with the following advantages:

· Simplified object creation, especially for hierarchical object structures and dependencies;

· Abstraction of requirements; this allows developers to specify dependencies at run time or in configuration and simplify management of crosscutting concerns;

· Increased flexibility by deferring component configuration to the container;

· Service location capability; this allows clients to store or cache the container.

Design Goals

· To promote the principles of modular design through aggressive decoupling;

· To raise awareness of the need to maximize testability when designing applications;

· To provide a fast and lightweight dependency injection container mechanism for creating new object instances and managing existing object instances;

· To expose a compact and intuitive API for developers to work with the container;

· To support a wide range of code languages, with method overrides that accept generic parameters where the language supports these;

· To implement attribute-driven injection for constructors, property setters, and methods of target objects;

· To provide extensibility through custom and third-party container extensions;

· To provide the performance required in enterprise-level line-of-business (LOB) applications.

Getting Started

For an introduction to dependency injection, see the article Inversion of Control Containers and the Dependency Injection pattern by Martin Fowler.
Two Quickstarts packaged with the release are also a good start.

System Requirements

The following are the minimum system requirements for Unity:

· Microsoft Windows XP Professional, Windows Server 2003, Windows Server 2008, or Windows Vista operating system

· Microsoft .NET Framework 2.0, 3.0, or 3.5

· Microsoft Visual Studio 2005 or Visual Studio 2008 development system

Information on Microsoft patterns & practices

– Visit us at http://msdn.microsoft.com/practices/ to see the full line of existing patterns & practices.

– If this mail was forwarded to you, you can sign up for automatic notification through the pagnurel alias.

我的博客：http://vincentyang.cn/blogs/vincentyang/archive/2008/04/09/news-just-released-unity-application-block-1-0.aspx

原报告不是免费的，只有这条www.news.com的新闻：http://www.news.com/8301-10787_3-9892675-60.html?tag=nefd.top

其中有一段很有价值：

It has a long ways to evolve before it will be the home of applications with more gravitas, solving meatier social networking and collaboration problems. A social graph platform, comprised of profiles, connections, sharing and access controls, groups, communication, conversation, and collaboration, can provide an environment for so much more than just playful social networking. There is yet plenty of room for innovation going forward, as social networking applications become more sophisticated, with greater investment in applications for different target communities of users - users for whom it makes sense to build tools for sharing, knowledge management, and collaboration upon a social graph.

March 12, 2008 5:00 PM PDT

Navigating out of Facebook's awkward adolescence

Posted by Charles Cooper Post a Comment

It's easy to get caught up in the mania but as a new O'Reilly report reminds readers, only a handful of Facebook applications ever become smash hits.

Anyone who has encountered the new oddball Facebook app du jour can attest that the novelty gets old rather fast. That's because many of the ideas are insipid time sucks. At that point, you're more likely to tune out (if you haven't already hit the delete button.) Indeed, O'Reilly notes the "tendency for individual applications to grow very quickly within the first few weeks, and then to plateau in growth after a few weeks."

Growth pattern for "falling" apps

(Credit: O'Reilly)

The reasons why:

Only a very small percentage of Facebook applications have enough traffic to generate substantial advertising dollars (this was a key finding of O'Reilly Radar's original Facebook Application Platform report), and The social networking phenomena is still in its awkward (and baffling) adolescence, so few marketers can unravel the real opportunities from the hype and the hope.

Anybody who spends a fair chunk of time on Facebook inevitably is going to get bombarded by goofy apps forwarded by friends. O'Reilly's research backs up the anecodotal impression that "developers are not making heavy investments in the Facebook as platform. For the most part, applications are still fairly lightweight - "fluffy" - in nature."

So for the time being, O'Reilly is land zoning Facebook more as a testing ground for promotional and marketing activity than for serious applications. On the surface, that may not sound promising for the future, but it's useful to recall that we're still in the very early innings.

It has a long ways to evolve before it will be the home of applications with more gravitas, solving meatier social networking and collaboration problems. A social graph platform, comprised of profiles, connections, sharing and access controls, groups, communication, conversation, and collaboration, can provide an environment for so much more than just playful social networking. There is yet plenty of room for innovation going forward, as social networking applications become more sophisticated, with greater investment in applications for different target communities of users - users for whom it makes sense to build tools for sharing, knowledge management, and collaboration upon a social graph.

Once they figure that out, Facebook may be a more promising testbed where outside developers aim far beyond personal social networking.

Topics:

Business currents, Technology

Tags:

O'Reilly, Facebook, social graph

Bookmark:

Digg Del.icio.us Reddit

 

URL：http://vincentyang.cn/blogs/vincentyang/archive/2008/03/13/o-reilly-report-navigating-out-of-facebook-s-awkward-adolescence.aspx

软件+服务（S+S）是微软未来的战略方向，也是微软对市场的大胆预估。通过对中国市场的观察，我在中国已看到了一些势头，和微软的预测不谋而合。

比如，随着Alibaba的上市，马云成为中国最有影响力的创业偶像；于是在B2B,或Web2.0上，有许多人都开始大谈“软件即服务（SaaS）”的模式。其中，“马云亦云”的公司不乏少数，我也不想多说；但我看到有一些公司是在现有营销模式下，并在其以往客户商业基础上逐步探索，因而其成功的可能性会大得多。

这里举几个例子，来看看S+S模式在中国特有环境下有何特别优势：

1）某华东城市管理项目，（强调，此城管非彼城管！！！）是对城市设施，运维，应急指挥的自动化协同办公系统。在技术上，这有许多技术的整合，如视频，地理地图信息、安全、等等；在部门上，有交通，水电，公安，等等；在行政区划上，有省地市区镇乡村，等等。这时，只有结合软件+服务模式，才能满足所有各方需求，灵活部署在各种场合。比如，公安系统通常有较完整系统，同时又较高的安全要求，这时纯粹的服务模式难以达到对数字的敏感信息的保密。而另一方面，在一些镇乡村，通常没有较完善的IT环境，也许没有足够的经费完全实施，这时可以汇总资源，通过SaaS/Hosting的模式，提供平台服务，甚至通过租赁或附加产业（如广告）的方式提供服务。

2）张家界景区RFID门票系统。如同难产的3G标准一样，中国RFID大局未定，“引一代英雄尽折腰”，众多先驱成了先烈。但独有一家公司独辟蹊径，在张家界RFID门票系统一举站稳脚跟。其中的套路就是S+S中的“Finished Service”。他们为景区提供完全“免费服务”，由他们提供全部软硬件，并派三位全时间员工在景区提供全部的运维服务，唯一的条件就是必须由这家公司印刷门票，每张十元（含RFID芯片，封装，印刷）。这样，这个公司就有了一个每年1千多万的现金流；而景区完全不用关心任何系统问题，因为他们“购买"的是“门票服务”。

现在有人提到“C2C model"。这里不是指“Cusotmer 2 Customer”，是“Copy 2 China”。:) 因为中国在许多商业模式、系统架构上，能够迅速的学习，移植国外的先进经验。

我相信，微软的“S+S”在中国的落地一定不会慢，也许还会比其他国家快。

2007年5月，MSDN Architecture Center发表了

Building Distributed Applications

A Comparison of the Top Four Enterprise-Architecture Methodologies

URL:http://msdn2.microsoft.com/en-us/library/bb466232.aspx

Roger Sessions
ObjectWatch, Inc.

Summary: Twenty years ago, a new field was born that soon came to be known as enterprise architecture. This paper covers a broad introduction to the field of enterprise architecture. Although the history of the field goes back 20 years, the field is still evolving—and rapidly so. (36 printed pages)

Contents

Executive Summary
Introduction
A Brief History of Enterprise Architecture
Case Study
The Zachman Framework for Enterprise Architectures
The Open Group Architecture Framework (TOGAF)
Federal Enterprise Architecture (FEA)
Gartner
Comparison
Conclusion
Glossary
References

强烈推荐，软件架构师必读。其实，即使在其他行业，也有一定的借鉴，可惜不容易读懂。

我已推荐微软中国ＤＰＥ翻译成中文，一旦发表，我会马上通知大家。

http://www.vincentyang.cn