Microsoft Unity Application Block (Unity) 2.0 Beta 1 – February 2010
This document contains late-breaking information about Microsoft Unity 2.0 Beta 1 – February 2010 that could not be included in the documentation. Any additional information and bug fixes that are delivered after the release date will be available on the
Unity Community site
and on the Unity MSDN site
The detailed change log is included in the HTML Help documentation (.chm file) installed with Unity and [here|].
This is a preliminary release of the code and documentation that may potentially be incomplete, and may change prior to the final release of Unity 2.0.
This release does not include the final test pass, full platform testing, and integration testing with Microsoft Visual Studio that will be completed for the final release. We do not advise use of this Beta release in production applications. It is provided
for preview and evaluation purposes only.
This release should not be interpreted as a commitment on the part of Microsoft as to any new features or improvements, and Microsoft cannot guarantee the accuracy of any information that may indicate features or changes to future releases.
Your Feedback is Invited
Organizations are encouraged to begin their Unity 2.0 evaluation now. This release is intended to be a feature complete version of Unity 2.0, with the exception of the Visual Studio integrated configuration tool.
We would appreciate feedback on any issues found, or any other general comments on this release. You can post feedback and comments on the Unity Codeplex forum.
The following are the known issues and important information about this release:
The input.Arguments collection available within a behavior when using interception has incorrect values for ref and out parameters, and does not correctly reflect the parameter direction.
The Interface Interceptor will intercept the call twice when the intercepted interface or class contains an attribute.
Behaviors that have the willExecute property set to false are not skipped, and will still execute.
Method access exceptions occur when building up List<T> on the .NET Framework version 4.0.
Interception fails when using a Transparent Proxy Interceptor and calling a generic method on an interface.
Dependency injection does not occur for explicitly implemented properties.
Some of the Unity unit tests use features of the Moq mock object library. We cannot include these libraries as part of the Unity download. To run the unit tests, please download the binaries for Moq 3.1 from the project site (current version as of this
writing is 3.1.416.3) and unpack the binaries and place them in this directory. Both the desktop and Silverlight binaries can be placed here. You will then be able to compile and run the unit tests.