Microsoft   |   patterns & practices   |   Developer Network   |   Enterprise Library   |   Acceptance Testing Guide   |   Personal Site

Enterprise Library 5: Code is done, MSDN next week - Grigori Melnik: Thoughts on Agile Software Engineering and Beyond - Site Home - MSDN Blogs

Enterprise Library 5: Code is done, MSDN next week

Enterprise Library 5: Code is done, MSDN next week

  • Comments 6

Greetings, Enterprise Library users!

I know many of you have been eagerly waiting for the v5 release, which I announced in this roadmap to be tentatively available on Apr 14. It’s great to see such interest from the community! We are in the final steps of getting through the release gates and final paper work. As soon as these are completed, we will be releasing the binaries on MSDN.

The code is done and is available today through the Codeplex source tree. And for those of you waiting for the official bits… any day now.

- Grigori

Comments
  • Thanks for the news!

    From Costa Rica, waiting anxiously!

  • We are wating for the new Enterprise Library release.... Thanks for your work!!!

    Our team (entlib.com) will provide technical articles in Chinese version soon.

  • Greeting From Tunisia.

    Waiting for the release.

  • Thanks for the great news

    I have downloaded the source code from below location - http://entlib.codeplex.com/SourceControl/list/changesets/65503 as mentioned in the Grigori -blog.  I have recompiled the solution and copied the binaries in shared location to be used by the project team.

    When we try to add reference to the Microsoft.Practices.EnterpriseLibrary.Data and build our project it gives the following error

    Error 2 The type or namespace name 'Data' does not exist in the namespace 'Microsoft.Practices.EnterpriseLibrary' (are you missing an assembly reference

    Please advice

  • Released and live now - http://blogs.msdn.com/agile/archive/2010/04/20/microsoft-enterprise-library-5-0-released.aspx

  • Hi Subu,

    i sorted the problem of missing an assembly reference by changing target framework from .NEt Framework 4 Client Profile to .NET Framework 4.

    Luca

Page 1 of 1 (6 items)
Leave a Comment
  • Please add 3 and 6 and type the answer here:
  • Post