Enterprise Library 3.1 is coming!
While I've been jetsetting around the world, in Redmond the Enterprise Library team has hard at work putting together the 3.1 release. Before you get too excited, this is really just a maintenance release addressing a small number of issues discovered since the release of 3.0. Here is a summary of the main changes:
Policy Injection Application Block
- The default Remoting Policy Injector can now be replaced with alternative interception mechanisms via configuration without modifying the application block code
- Call Handler attributes are now honored correctly when placed on interface methods
- Fixed an issue that could cause duplicate handlers where matching rules matched both a class and its interface
- Classes implementing COM interfaces (including those deriving from System.Windows.Forms.Form) can now be intercepted
- TraceLogEntry class is now serializable, allowing it to be used with the MSMQ Trace Listener
Validation Application Block
- Fixed an issue that prevented the PropertyComparisonValidator from working with the Windows Forms integration adapter
- The message template for the PropertyComparisonValidator can now be saved using the configuration tools.
Data Access Application Block
- Connection strings for OLEDB and ODBC connections can now be edited using custom dialog boxes from the configuration tools
Of these changes, the only brand new feature is the ability to replace the PIAB's interception mechanism without code changes. This is quite significant, since as Ed mentioned a while ago, there are quite a number of different ways to do interception, and different approaches may be appropriate for different applications. While we still only provide the remoting proxy mechanism in the "box", it will now be much easier to build different approaches, such as dynamically emitting inherited proxies. Of course, if you build such a beast, please consider contributing it to EntLib Contrib.
Since I'm no longer in Redmond I'm not sure exactly when Enterprise Library 3.1 will hit the streets, but it's definitely in the "real soon now" timeframe!
Comments
Anonymous
May 22, 2007
The comment has been removedAnonymous
May 22, 2007
The comment has been removedAnonymous
May 22, 2007
The comment has been removedAnonymous
May 22, 2007
Jeg har ikke set så meget omkring dette release andet end Toms lille heads-up . The patterns & practicesAnonymous
May 24, 2007
I would like so much to adopt the validation block, but there are so many problems with it when using configuration (I don't want to use attributes) that it is unusable. For instance two major bugs are with resource files, so no localization support and you cannot use custom validators, so extending is unavailable. Can you please make these fixes for 3.1?Anonymous
May 24, 2007
Enterprise Library 3.1 just Released: It is a maintenance release to fix a few bugs. It also includesAnonymous
May 24, 2007
Cool - the 3.1 maintenance release to Enterprise Library is available from MSDN, its creatively namedAnonymous
May 24, 2007
Enterprise Library 3.1 Released...Anonymous
May 24, 2007
A few updates to EntLib for the May 2007 releaes. Just released in April, the P&P team updates (bugAnonymous
May 25, 2007
I second Guy's comments on the need to get name validation with external dll's fixed. We're using Entlib 3.0 with VSTO and have more than once contemplated going back to 2.0 because we can't seem to get around the errors except by giving full trust to all our typed dll's AND the Microsoft Office directory. Not exactly my idea of a good implementation so I'd love to see that fix.Anonymous
May 26, 2007
Guy and Rob - sorry if I missed a discussion on this before, but I'm not sure I know what problems you are talking about - could you please elaborate? TomAnonymous
May 28, 2007
Вийшли багофікси до Enterprise Library 3.0, тепер ця бібліотека розповсюджується з версією 3.1. ОзнайомитисьAnonymous
June 16, 2007
Hi, I am trying(no luck so far) loading the Entlib configuration dynamically from external resource(custom webservice). My custom webservice provides me the Entlib configuration as an XML(actually it is the App.config serialization), and i want to load this configuration without creating a local App.config Is'nt there any other easier way? Do i have to implement the section implementation for each section in the App.config,even if i do not work in a App.config manner??? Regards ShayAnonymous
July 17, 2007
The comment has been removed