Microsoft | patterns & practices | Developer Network | Enterprise Library | Acceptance Testing Guide | Personal Site
We’ve released the following on MSDN today:
Available from the landing pages:
On to the next piece now – Hands-on Labs…
EntLib 5.0 had 2010 projects and solution. Any plan to do this for Unity, or should I do it myself?
Actually, they are included in the standalone Unity release.
Oh. I'll look again. Sorry. Thanks.
Ah. I wasn't looking in the UnitySource.zip that came with the standalone Unity release. I was pulling the source from the Unity codeplex site (change set 50871).
I have already downloaded, installed and started working with EntLib 5.0 final release (downloaded on 22nd April, 2010).
I also had Unity 2.0 Beta on my machine at that time. However, I found that Unity 2.0 is already supplied with EntLib 5.0 final release and am currently using Unity 2.0 from \EntLib50Src\bin.
Now that the Unity 2.0 Standalone final release is out should I continue to use Unity 2.0 from my \EntLib50Src\bin or update it with final Unity 2.0 assemblies?
It's the same Unity 2.0 - whether packaged with EntLib5.0 or downloaded as standalone.
The only reason the standalone version was made available at a later date is because the Unity documentation set was being finalized.
So, no need to do anything with your setup.
Happy coding! Feel free to share your experience with EntLib 5.0 and Unity 2.0 and any feedback.
Thanks for the update. It's always a timesaver working with EntLib and you did a real good feature with unity Overrides (esp. constructor parameter). Allowing to pass a parameter was an issue that was holding me back from using Unity. Now it's just great.
Just an update. I had posted a discussion at http://unity.codeplex.com/Thread/View.aspx?ThreadId=212000 but got no acknowledgement. Would be great to know if that's a valid request or I am missing something.
Why wasn't support to configure Unity with the configuration tool added?
Thanks for the feedback.
Also, please don't expect acknowledgments in the forum immediately, especially on Saturdays :)
Your suggestion sounds like a feature request and I'll include it in the future release backlog.
Simply because of time constraints. We'll keep it on the backlog for future releases.
However, we've made XML authoring of the Unity config significantly easier with assembly and namespace aliases and such.
Please keep us informed about your experience as it is impotant in our planning of vNext.