Thwarted!
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 Microsoft.com 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 https://msdn.microsoft.com/practices 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
- Anonymous
June 30, 2005
Tom,
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: http://weblogs.asp.net/jan/archive/2005/06/23/414699.aspx).
How difficult would it be to add code signing (using a SN keyfile preferably) to the 1.1 build?
Thanks!
--Jim - Anonymous
June 30, 2005
Not to be pedantic but June only has 30 days -- close enough anyways! - Anonymous
June 30, 2005
Will Enterprise Library June 2005 support vs 2005 beta 2 and sql server 2005?
thanks - Anonymous
June 30, 2005
The comment has been removed - Anonymous
June 30, 2005
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. - Anonymous
June 30, 2005
The comment has been removed - Anonymous
June 30, 2005
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! - Anonymous
June 30, 2005
"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 :-) - Anonymous
July 01, 2005
Don't shoot the messenger, but the download does not appear to be there today.
Any ideas... - Anonymous
July 01, 2005
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!) - Anonymous
July 01, 2005
The comment has been removed - Anonymous
July 01, 2005
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 http://blogs.msdn.com/scottdensmore/archive/2005/03/01/382650.aspx to get started.
Tom - Anonymous
July 01, 2005
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. - Anonymous
July 01, 2005
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.
Tom - Anonymous
July 01, 2005
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.
Marc - Anonymous
July 11, 2005
Let me also thank you for making String Resource Tool available in gotdotnet site. - Anonymous
July 12, 2005
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?
Cheers
Colin - Anonymous
July 22, 2005
Colin,
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.
Thanx,
Mike Quinn