In my last post I expressed considerable optimism that we would get Enterprise Library June 2005 released in the month that bears the same name. The good news is that we got the code and installer built, tested and signed off with a day to spare. However today we are having some internal process problems that have prevented us getting the download on the website. I've just been told that we've missed the cutoff today. However I'm going to try pulling some strings so that tomorrow will officially be Friday June 31st (surely someone at Microsoft has the power to do that? 😉

Anyway, my sincere apologies for the additonal delay. Provided nothing else goes wrong, the download should be up on tomorrow.

Update (June 31st):

I have good news and bad news. The good news is that we finally worked out the problem that was preventing the download system from accepting the file. The bad news is that this happened after today's 2pm cutoff. Since Monday is a holiday in the US, the expected release date is now Tuesday, June 35th. This time I'm really confident it will actually happen! Thanks again for your patience...

This posting is provided "AS IS" with no warranties, and confers no rights.

Comments (18)
  1. Jim McCusker says:


    I noticed you didn’t reply to the question about code signing. My group would like to leverage the Enterprise Library in our Sharepoint development activities. We use code signing in order to grant our code FullTrust while running under Sharepoint (see Jan Tielen’s blog post:

    How difficult would it be to add code signing (using a SN keyfile preferably) to the 1.1 build?



  2. Mike Bouck says:

    Not to be pedantic but June only has 30 days — close enough anyways!

  3. Param says:

    Will Enterprise Library June 2005 support vs 2005 beta 2 and sql server 2005?


  4. Brian says:


    There are a couple of changes I’d like to see made if at all possible to the data block.

    I have ported my entire line of .NET apps to use the enterpriselibrary including some backup utilities that run some large queries on the AS/400. Anyway to make a long story short I can parameterize the the command timeout for the connection object in the config file but the command object does not inherit it thus causing the queries running over 30 seconds to bomb. This is a simple one line code add to fix.

    The other is alternate functionality I’d like to see.

    1) Overload Database.GetStoredProcCommandWrapper to take just a command name and a boolean about whether or not to derive the parameters. This will require doing the derive from the cache or database before the method ends because I’d like to be able to call set parameter value for some of the parameters prior to running the Execute series of methods.

    Other than that keep up the good work.

  5. Jonathan says:

    Well done,

    A marvelous effort by all involved.

    Brian, Jim you should probably join the EntLib Community over at gotdotnet and log these as suggestions. 🙂

    I’ve long suspected June needed an extra day, now there is good reason.

  6. Thanks for all the comments.

    Jim: We definitely recommend that you strong-name the Enterprise Library assemblies. We don’t do this for you since we don’t ship binaries (by policy) and it would have been bad to ship with a keyfile (since anyone could use the key for any purpose). We haven’t done anything in 1.1 to make it any easier to sign the assemblies (hopefully in the .NET 2.0 version). That said, it isn’t too hard – just create a keyfile (using "sn -k mykey.snk"), update the attributes in the AssemblyInfo.cs files (you can use search/replace) and recompile. Note we thought about letting you put this in the single GlobalAssemblyInfo.cs file, but this would have caused problems with relative paths due to the different folder structures across the projects.

    Mike: Yes, I know – hence the joke 🙂

    Param: Yes, the June release of EntLib will work with VS2005 beta 2. There are a few tricks to this still, but it’s all documented in the readme. I don’t believe we did anything special to support SQL 2005 but it runs great on my box.

    Brian: Thanks for the suggestions. Note that you can programmatically access the Command object to set the timeout, but I agree it would be cool to do this through config. We can think about this in vNext.

    Jonathan: thanks for the praise – maybe you should hold off until you see the deliverable – but we hope you’ll be pleased! Again, this is a minor maintenance release so don’t expect too much this time around.

  7. jdrichar says:

    I would not stress out too much about missing a few days, I think all of us who are using the blocks can handle a long holiday weekend!

    For those of us who are geeks, can you post the readme?

    Is your team running the same level of unit testing as you did with the 1.0 release?

    By the way, great work guys, I really appreciate what you are doing for the community!

  8. chrislesage says:

    "However I’m going to try pulling some strings so that tomorrow will officially be Friday June 31st "

    There was a guy who pulled it off once… it was emperor Augustus, he took a day from february and had it put in the month august 😉

    And btw at our company we also would like the assemblies strongly named. The deployment was a nightmare, the usage of the EL a dream come true 🙂

  9. Don’t shoot the messenger, but the download does not appear to be there today.

    Any ideas…

  10. Releases happen at 2pm Pacific Time, apparently. There is still some wierdness going on with the publishing process (I’m not involved in this part so I’m really not sure what’s going on) – but hopefully it will happen today. If not, I’ll post an update (and get even crankier!)

  11. First of all congratulations for this great blocks of code but… Its just me or the Enterprise Library and all other MS blocks have a very very serious issue?

    What if I wanted, and I realy do, until next thursday at least, to create an assembly that uses some of the blocks(that need to have configurations) and is fully independant, free of every Application Domain?

    Very simple, just use an assembly config instead of an application config…

    …Wait a minute…


    Pardon me while I burst into flames… 🙂

    For now – out of the box – I just don’t know how.

    Example 1:

    What if I wanted to create a ‘DataAccessLayer.dll’ with it’s own config? So I could use it in my web service, per example?!?? (Just use the web.config… Yeah right…Bad example.)

    I simply don’t have an executable… So what?! I still want to use the application blocks.

    It’s all about distributed enviroments…

    Example 2 – The best example of all:

    The same assembly will have to work with a VB6 app, some old asp pages and new pages.

    Since the only exe it’s in VB6 it doesn’t know what an app.config is, correct? I also don’t have web configs in old asp. So how can I do it? HardCode everything? Re-write every call to the configuration block?!

    Answer: The assembly should have it’s own config.

    Thats my sugestion, the blocks should depend less of each other.

    I should be able to simply copy and paste one or more assemblies+their configs and by referencing it in a project, use them.

    Sorry for the long message. I hope I have explained myself in a correct way.

  12. Hi Sergio –

    No reason to scream; you can do this today :). It’s not the default or most obvious way of using the blocks, but you aren’t tied to app.config / web.config. Take a look at to get started.


  13. Ralph says:

    Hey Tom,

    I was hoping to take advantage this long weekend and start this new project for .net 2.0. Since, the Official Enterprise Library update won’t be released until Tuesday, do you think that I can start working using the one from rationalpath in the meanwhile. I mean the methods and function signatures should be the same correct? So, I should be able to start coding, and change to the official libraries when they are released on Tuesday? Please correct me if I am wrong?

    Thanks in advance for your help.

  14. Hi Ralph –

    This sounds like a reasonable strategy. The June release of EntLib is API-compatible with the January release, and I don’t think the RationalPath version breaks the API either. So you should be able to swap in the offical release pretty easily next week.


  15. Marc says:

    Not quite thwarted. it looks like your post is available for download on June 32nd. I just went to the site, saw something that was flagged 1.1 with a July 1 date, and download it. Haven’t quite installed it yet. I need to save my existing set up. I made some customizations.


  16. Siva Mateti says:

    Let me also thank you for making String Resource Tool available in gotdotnet site.

  17. Colin Hardie says:

    Hi Tom, download the June release of the Enterprise Blocks. Was trying to strong name the assemblies (which I done succesfully with the previous release). Since Configuration.Design references MSDASC.dll (Interop.MSDASC), which in turn does not have a strong name, then the build fails. Is there a work-around for this?



  18. Mike Quinn says:


    I ran into the same problem. I found from the newsgroups that you can place a key file reference in the project properties to apply your key file as a "wrapper" on any Com Interop references.

    In addition to adding your key file reference to each of the projects (or moving it to the GlobalAssembly.cs with an absolute path to your key file), you should do the following:

    Open the EnterpriseLibrary

    Open the Project Properties for the "Configuration.Design" project.

    Type your key file name in the "Wrapper Assembly Key File"

    That fixed it for me.


    Mike Quinn

Comments are closed.

Skip to main content