Enterprise Library 4.0開發計劃
近日,微軟模式與實踐團隊釋出了Enterprise Library 4.0的開發計劃,最大的變化就是加入了依賴注入,在之前的推薦系列中我也曾經介紹過,暫定名稱為DIAB(Dependency Injection Application Block),除此之外主要的變化有:
支援Visual Studio 2008
解決了VAB和PIAB中的一些缺陷
對Caching Application Block提供了一些擴充套件
Logging Application Block效能提升
在VAB中支援WPF的驗證
......
全文如下:
Introducing a lightweight Dependency Injection container (also known as DIAB for now; the name will change) (prioritized uber-stories)
Primary goals: make p&p assets more container-friendly and more easily consumable; stimulate the use of dependency injection for building modular, loosely-coupled apps.
- Provide a reusable dependency injection container with convenient, non-invasive API (incl. support for constructor injection, property injection, method call injection)
- Support imperative configuration of DI container (via API)
- Support declarative configuration of DI container (via config files)
- Solid documentation – leveraging DI container to build loosely-coupled apps and improve their testability and maintainability – not just API docs (including: conceptual overview, quickstart, demos, hands-on labs)
- Enable container hierarchy
- Optimize performance of DI container
- Support imperative configuration extensibility of DI Container
- Support declarative configuration extensibility of DI Container
- Update EL configuration tool (both standalone and VS-integrated) to configure DI Container
- Provide intuitive installers (two packages: DIAB standalone; DIAB integrated with EntLIB; incl. side-by-side scenarios)
- Once refactored, compat-test refactored blocks on other containers (Castle, Spring.NET, etc.)
- Provide a simpler version of the EventBroker (support scenario: I want to use my Web service and to use DI to automatically wire it up when created with logging, exception handling etc.)
Enterprise Library enhancements to the current application blocks (prioritized stories)
Primary goal: make the lives of EntLib users easier.
- Ensure EL compatibility with VS2008 (incl. block factory; backwards compatible with .NET3.0 and VS2005, and support side-by-side scenario).
- Provide extensibility points for Caching Block to allow alternate caching implementations (including distributed cache providers) to be plugged in. The objective here is NOT to replace the ASP.NET caching but to provide more choices.
- Integrate WMI2 Support (pull it out of the core and make both WMI1 and WMI2 available according to the targeted .NET framework (if it's <3.0, it's WMI1; if it's 3.5, it's WMI2)
- Support partially-trusted callers (requires a full security review).
- Improve performance of the Logging Block by optimizing text formatter (lazy formatting in case of the local logger, and eager formatting in case of the remote logger).
- Enhance logging flat file functionality of the Logging Block: roll on period boundaries (with the period inferred from the pattern specified for the logging file).
- Improve documentation on how to avoid configuration pitfalls.
- Provide more descriptive error messages.
- Hands-on Labs: Validation Block, Policy Injection Block, Dependency Injection Block.
- Fix exception formatter when using the indexer.
- Allow to run multiple rulesets in Validation block.
- Refactoring PIAB: allow to control the order of how handlers are applied.
- Caching Block: expiring items when subjected to load.
- PIAB+VAB: Eliminate combining the results of searching attributes and config into an AndCompositeValidator without checking if either of those is null.
- PIAB fix: deal with race conditions in PolicySet.
- VAB: allow copying of existing rules in the config tool.
- LAB: allow finer-grained local filters in the config tool.
- Instrumentation: provide absolute values for performance counters.
- Instrumentation: enable performance counters to work on IIS.
- VAB: include WPF validation.
- VAB: provide a light-weight type picker.
- LAB: provide a way of checking if something was logged or not.
詳情大家可以訪問:http://www.codeplex.com/entlib/Wiki/View.aspx?title=EntLib4%20Backlog
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/12184684/viewspace-531837/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 微軟Enterprise Library 4.0將支援依賴注入微軟依賴注入
- Enterprise Library 4.0中的依賴注入容器(Unity)預覽依賴注入Unity
- 以太坊開發計劃
- zendAPI 專案開發計劃API
- 聯合國開發計劃署:2023年聯合國開發計劃署年度報告
- 規劃迭代--及時開發詳細計劃(轉)
- Enterprise Library - Data Access Application Block 6.0.1304APPBloC
- Enterprise Library:Unity的幾個注意事項Unity
- 黔村淘專案開發計劃
- OneBlog手機端開發計劃
- 『騰訊雲開發達人計劃』開始啦~
- Enterprise Library 4.1--實體驗證程式塊
- Accord.NET重啟4.0 開發
- iOS藍芽4.0(BLE)開發(一)iOS藍芽
- 譯文:Vue.js 3.0 開發計劃Vue.js
- Cloudflare 開發專家計劃:立即申請!Cloud
- Enterprise Library 4.1學習---快取應用程式塊快取
- 敏捷規劃,讓你做一個有計劃的開發人敏捷
- React Native 藍芽4.0 BLE開發React Native藍芽
- iOS藍芽4.0開發基礎教程iOS藍芽
- 有用AspectJ開發專案的麼?或者計劃
- Enterprise Library 6——Using the Logging Application BlockAPPBloC
- 泰山眾籌(阿凡達4.0)系統開發流程及分析丨泰山眾籌(阿凡達4.0)開發原始碼功能原始碼
- Google計劃開發開源WebKit核心Android瀏覽器GoWebKitAndroid瀏覽器
- SUN4.0眾籌模式系統開發模式丨SUN4.0阿凡達模式系統開發技術方案模式
- app開發的規劃與籌劃APP
- iOS 藍芽4.0開發使用(內附Demo)iOS藍芽
- 出行路線規劃系統設計與開發
- 【譯】闖入遊戲開發 #8:策劃(設計)遊戲開發
- Scrum:兼顧計劃與靈活的敏捷開發Scrum敏捷
- 專案開發計劃(GB856T——88) (轉)
- 凡事預則立:談專案開發計劃(轉)
- 聯合國開發計劃署:中國人類發展報告特別版
- KRAFTON正式公開新遊戲專案《inZOI》的開發工作計劃Raft遊戲
- 泰山眾籌4.0阿凡達開發原理丨泰山眾籌4.0阿凡達系統開發詳細技術及原始碼分析原始碼
- 泰山眾籌SUN4.0模式軟體開發模式
- JavaEye網站2010年開發計劃展望Java網站
- 軟體開發專案計劃編制過程(轉)