Hello World – its Enterprise Library

Now would be a good time to start my day...if I were in London where it is 10:46 GMT but here I am at 2:46 wide awake writing my blog.  I'm sorry I can't help it but I am really pumped about Enterprise Library and the great work that Tom, Bill, Scott, Peter, Ed and the rest of the team has done.  I'm pumped because I really believe that this is going to help people and if you don't know about it make sure you visit the Enterprise Library home page and take a look.

What I really want though is to hear from you about Enterprise Library...what are your first impressions?  How will you use this great new resource?

It has been a long time coming and already thousands have downloaded it over the weekend.  I can't wait to hear from you so blog away my friends its a great day.

Comments (9)

  1. Adam Young says:

    What happened to the Smart Client Offline and Updater blocks… there’s a v2 release of the Updater block on GotDotNet. Will these two blocks not be incorporated into the Enterprise Library?

  2. Cyriel says:

    @Adam Young: AFAIK MSFT didn’t include the Smart Client and Updater App Blocks in the first version of EntLib, can’t remember the reason why that easily though. They most probably will be included in future versions I guess…

  3. Senkwe says:

    Not to mention the User Interface App Block

  4. Daniel Chait says:

    As it turns out, Saturday was the day I had blocked off to add logging to my application, so I decided to see what the EntLib had to offer. Boy was I disappointed! I ended up using log4net as always. Here are just a couple reasons:

    1. With log4net, I didn’t have to change the way my app is configured. The EntLib stuff is all tied in with the Config block, so it seems impossible to use the logging block on its own without the Config block. Since our app uses its own homegrown configuration code (which uses a combination of settings stored in 2 xml files (one global and one user-specific), command-line args, and environment variables, it was impossible to rework that all to use the config block in a reasonable time.

    2. RollingFileAppender!!!

  5. Smart Client blocks and UIP: Yes, we’re working on it. We had to limit the scope of Enterprise Library v1 to get it out the door sooner, but we’re working on new blocks that will be given the same treatment

    Config: While it is possible to use the EntLib blocks without config (in most blocks you can use factory constructors with your own ConfigurationContext, or in the Logging block you can directly write to an ILogSink of your choosing), you are correct in saying that the Enterprise Library blocks are pretty closely linked to the config block. However the config block itself is extensible. By writing your own storage providers and/or transformers, you can make the config block load configuration from wherever you like.

    RollingFileAppender: Great idea, we will consider this for vNext. Alternatively we’d love to see someone implement this and share it with the community.

    Hope this helps

    Tom Hollander

    Enterprise Library Product Manager

  6. Colin says:

    Can you remove any collation specific elements from the Cache database script, the collation in the script is the default for installations with a US English system locale, installations with a UK English system locale use a different default collation.

  7. Daniel Chait says:

    Tom –

    I too would like to see it. I guess my advice would be – if you’re starting a project now, or are early enough along in it, AND you have the budget to develop the parts you really want, then I would consider using the Ent Lib.

    And seriously, logging to a file without rolling over? You guys ought to not have released that one. That’s a time bomb in anyone’s app who uses it, be prepared in about 6 months when people have deployed the first EntLib apps to production, they run for a little while, then disks start to fill up. I would not want to be the guy responsible for that one…

  8. Steve Maine says:

    FYI, Hisham just posted an implementation of a Rolling File Sink for Enterprise Library that addresses this feature gap.


Skip to main content