And so it releases. This has been a great project and team to work with. I feel privileged to have been able to work with all the folks who made it possible, and to have made such a step forward implementing a close customer connection throughout the project. http://msdn.microsoft.com/library/default...

Quickie blog post, just to get jamming: EntLib internals webcast . Yes, EntLib and CAB ship with ObjectBuilder, our common factory & dependency injection infrastructure ++. Answering the FAQs: Yes, we have one. Yes, it's this one. Yes, you can build something like Spring with it, if you wanted...

This is the last community release before our final release - the purpose of this release is to allow you to see the changes we've been doing into the API based on your feedback, to let you start building apps on what is closer to the final drop. There are a couple of significant things about this...

Hello. How are you? Enterprise Library for VS.NET 2005 will have API and configuration changes compared to the latest versions (January/June). So will other blocks and a lot of the rest of the guidance....and you should expect this. er...Is that a roar I hear approaching? Why can't patterns &...

We have relased the p&p Community Process to 2.0, incorporating feedback we got from customers, partners and field on the 1.0 version. This one includes: - A more realistic relationship between the internal process and externally visible process. In the 2.0 version now we open up the information...

5 years ago Microsoft executives approved the existence of a group focused on guidance - understanding enterprise customer scenarios, creating a dedicated engineering team to producing guidance in the form of code,patterns, frameworks and guides, and consolidating the authoritative content that enterprises...

The release day is the final battle with entropy. It's when the work of months seems to be put at risk and "die the death of a thousand paper cuts"...Xenon's paradox kicks in and every little task breaks up into some smaller tasks and it suddenly feels there is more work to do today than the rest of...

Hello all - Its been great to see the community interest in CAB. Thanks for your support! (Join us here: http://workspaces.gotdotnet.com/cab ) We have 1000 users before our 2nd community drop!!! As you know we are working hard to have an important release of CAB in July. This will be potentially...

I love how the CAB project is working with our community process. Not only does the transaprency give us a chance to ge great input from field, customers, partners and even folks at MS product groups; but it also is a nice forcing function to keep our house in order continoususly. We started CAB iteration...

Yesterday we finished some cleanup refactorings around the EventBroker feature of CAB. I'm happy with the result, because it's conceptually simple, it's easy to use, and it isn't much code, yet it helps a lot. I expect some things to be added before release but here is pretty much the core of it as it...

Great piece of news - today in the patterns & practices group we went through our M0 milestone for an exciting asset to assist with Smart Client development. We are calling it the CAB - which stands for Composite UI Application Block. It is not a great name, because it doesn't tell you much about...

In the Smart Client Program we have been working in a way that involves community in building p&p guidance , especially the application blocks, and lets expert advisors and community members influence the project execution, all the way to allowing the community to vote on our go/no-go process. We...

I had a conversation with Ward today where he was asking me if it was common for folks in MS to share their goals (what you go against when you do performance appraisal) as a way of communicating to others what they are working on. It led me to think about a lot of things, but especially: 1) How the...

Looking for the killer CAB demo... This week we spent a considerable amount of time working on the CAB - Composite UI Application Block ..aka Smart Client Portal. Part of the value it provides is simplifying how visual components (SmartParts - think WebParts for windows) find, share data with, and control...

This is not about EntLib and not about Smart Client specifically, but we expose some plans soon around working on VB6 --> .NET guidance focused on Enterprise customers' LOB apps. Part of the challenge with this guide will be finding and keeping to the line that exists between: The 6 tomes of 8000...

First things first Software is about the people. Scott , Tom , Bill, Peter , Brian , Tim S , Mo, Tim O, Hisham, Paul, Rohit, Prashant, Mani, and Kyle - you all rock. The team has pulled together a release that carries forward the best of the “Application Blocks” initiative that started within the patterns...

We are preparing v2 of the Updater Application Block . (Check out the 300+ members GotDotNet community ) We have some core goals we want to go for: - Simplify, simplify, simplify - Allow partial updates - Tooling to 'add' the block to the app - You tell us! We prepared a 5..10 min survey to let you tell...

It's out! Finally - we jumped through some hoops and versions and lots of trimming and one major rewrite,and finally the draft is out. Here is the doc- Please give feedback - it will set a precedent on how p&p interacts with community. (Please apply to join the Workspace) I think the name is OK but...

I have been during the last months becoming increasingly warm to the idea of branching the UIP block into two branches: windows and web. Here's the reasons why we did it unified in the first place, and my opinion on why the assumptions aren't holding that well: Assumption: The conceptual model for flow...

Today we got together with Jamie Cool to discuss the roadmap of the Updater Application Block (UAB). You know, the block that adds self-update capability to your app. (BTW we have the update for BITS 2.0 on the GotDotNet site ) ClickOnce (in the Whidbey timeframe) provides the fundamental support for...

We are currently drafting a document around 'Community Process' , that we intend to use for the Smart Client program. You'll see it coming up in the gotdotnet workspace for Smart Client soon. As I was writing it I imagined how the name by itself could convey some wrong messages. So what will this community...