WFP, WF, WCF and CAB

TheMSsForum.com: The Microsoft Software Forum

Is the introduction of these new technologies going to change the way that
CAB works or will CAB still use basically the same architecture?

Bill
Top

Re: WFP, WF, WCF and CAB by Bob

Bob
Thu Jul 26 16:11:58 CDT 2007

CAB is an unsupported Patterns and Practices guideline which is destined
for the scrap-heap.

Before you cry out in pain don't despair. CAB promotes many excellent
practices including a great deal of architectural and pattern usage
guidance. In particular the Dependency Injection system.

The lessons learned from CAB are currently being built into the new
application framework Acropolis which is in an early CTP form at the
moment but which will have great influence on future application
development systems, especially in the Orcas time-frame.

In my day job we have used CAB extensively and are currently studying
the Acropolis migration path which, Microsoft assures me, will be
relatively painless.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.





Bill Gower wrote:
> Is the introduction of these new technologies going to change the way that
> CAB works or will CAB still use basically the same architecture?
>
> Bill
>
>
Top

Re: WFP, WF, WCF and CAB by Bill

Bill
Thu Jul 26 20:43:21 CDT 2007

The reason that I ask is that Microsoft Press has just published a book on
CAB that looks interesting but if CAB is dead or dying, is it even worth
purchasing the book and getting into CAB for an upcoming project?

Bill

"Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message
news:e8RaVl8zHHA.600@TK2MSFTNGP05.phx.gbl...
> CAB is an unsupported Patterns and Practices guideline which is destined
> for the scrap-heap.
>
> Before you cry out in pain don't despair. CAB promotes many excellent
> practices including a great deal of architectural and pattern usage
> guidance. In particular the Dependency Injection system.
>
> The lessons learned from CAB are currently being built into the new
> application framework Acropolis which is in an early CTP form at the
> moment but which will have great influence on future application
> development systems, especially in the Orcas time-frame.
>
> In my day job we have used CAB extensively and are currently studying the
> Acropolis migration path which, Microsoft assures me, will be relatively
> painless.
>
> --
> Bob Powell [MVP]
> Visual C#, System.Drawing
>
> Ramuseco Limited .NET consulting
> http://www.ramuseco.com
>
> Find great Windows Forms articles in Windows Forms Tips and Tricks
> http://www.bobpowell.net/tipstricks.htm
>
> Answer those GDI+ questions with the GDI+ FAQ
> http://www.bobpowell.net/faqmain.htm
>
> All new articles provide code in C# and VB.NET.
> Subscribe to the RSS feeds provided and never miss a new article.
>
>
>
>
>
> Bill Gower wrote:
>> Is the introduction of these new technologies going to change the way
>> that CAB works or will CAB still use basically the same architecture?
>>
>> Bill
>>

Top

Re: WFP, WF, WCF and CAB by Bob

Bob
Fri Jul 27 16:00:32 CDT 2007

My opinion; Yes.

The migration route from CAB to Acropolis is supposed to be smooth.

I do consulting work fo a world renowned bank and we have based a lot of our
technology on CAB for this very reason.

--
--
Bob Powell [MVP]
Visual C#, System.Drawing

Ramuseco Limited .NET consulting
http://www.ramuseco.com

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.


"Bill Gower" <billgower@charter.net> wrote in message
news:%23agqE%23%23zHHA.3788@TK2MSFTNGP02.phx.gbl...
> The reason that I ask is that Microsoft Press has just published a book on
> CAB that looks interesting but if CAB is dead or dying, is it even worth
> purchasing the book and getting into CAB for an upcoming project?
>
> Bill
>
> "Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net> wrote in message
> news:e8RaVl8zHHA.600@TK2MSFTNGP05.phx.gbl...
>> CAB is an unsupported Patterns and Practices guideline which is destined
>> for the scrap-heap.
>>
>> Before you cry out in pain don't despair. CAB promotes many excellent
>> practices including a great deal of architectural and pattern usage
>> guidance. In particular the Dependency Injection system.
>>
>> The lessons learned from CAB are currently being built into the new
>> application framework Acropolis which is in an early CTP form at the
>> moment but which will have great influence on future application
>> development systems, especially in the Orcas time-frame.
>>
>> In my day job we have used CAB extensively and are currently studying the
>> Acropolis migration path which, Microsoft assures me, will be relatively
>> painless.
>>
>> --
>> Bob Powell [MVP]
>> Visual C#, System.Drawing
>>
>> Ramuseco Limited .NET consulting
>> http://www.ramuseco.com
>>
>> Find great Windows Forms articles in Windows Forms Tips and Tricks
>> http://www.bobpowell.net/tipstricks.htm
>>
>> Answer those GDI+ questions with the GDI+ FAQ
>> http://www.bobpowell.net/faqmain.htm
>>
>> All new articles provide code in C# and VB.NET.
>> Subscribe to the RSS feeds provided and never miss a new article.
>>
>>
>>
>>
>>
>> Bill Gower wrote:
>>> Is the introduction of these new technologies going to change the way
>>> that CAB works or will CAB still use basically the same architecture?
>>>
>>> Bill
>>>
>

Top