Component UI CAB Architecture Guide??? For Dummies Book? :-)

18 Aug 2006 4:18 AM

Spam Catcher

Is there a "For Dummies" guide to the Component UI Application Blocks
(CAB)?

CAB seems to do what I need for a new application I'm building... but the
documentation provided with the Quickstart is a bit mediocre (I hate VS.NET
2005's help browser).

Are there any books out that go over the architecture in detail - and how
to build a sample app from the ground up?

Thanks!

18 Aug 2006 5:28 AM

Cor Ligthert [MVP]

Spam Catcher,

Do you really want to go that way, I have the idea that most in the dotNet
newsgroups don't like the Application Blocks,

Cor

Show quoteHide quote

"Spam Catcher" <spamhoneypot@rogers.com> schreef in bericht
news:Xns98233050D273usenethoneypotrogers@127.0.0.1...
> Is there a "For Dummies" guide to the Component UI Application Blocks
> (CAB)?
>
> CAB seems to do what I need for a new application I'm building... but the
> documentation provided with the Quickstart is a bit mediocre (I hate
> VS.NET
> 2005's help browser).
>
> Are there any books out that go over the architecture in detail - and how
> to build a sample app from the ground up?
>
> Thanks!

18 Aug 2006 3:33 PM

Spam Catcher

"Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in
news:uO6qvbowGHA.4880@TK2MSFTNGP04.phx.gbl:

> Spam Catcher,
>
> Do you really want to go that way, I have the idea that most in the
> dotNet newsgroups don't like the Application Blocks,

I know what you mean... I've used the latest Enterprise Libaries but they
seem OK. Missing some features, but generally they're not hard to use.

As for the Component UI block - what I'm hoping to do is a build a GUI
which is extensible. I need the ability to plug in different GUI
components depending on customer needs.

A standard plugin interface would take too much trouble to build (i.e.
I'll need a GUI interface, and some sort of background communications
framework). For the most part, I *believe* CAB solves this and allows
isolated components to talk to each other?

So here's my problem:

What's the best way to build an extensible GUI application which distinct
components that need to talk to each other.

For example:

Customer A needs a Customer Screen + Custom Data Entry Form.
Customer B needs a Customer Screen + Web Browser + Custom Logic

I don't really want to rewrite my app for each customer ; )

18 Aug 2006 4:50 PM

Cor Ligthert [MVP]

Spam Catcher,

I think that you ask to much from a newsgroup.

But you never know who want to give it a try.
I have as well not real a "good" link for this.

Sorry

Cor

Show quoteHide quote

"Spam Catcher" <spamhoneypot@rogers.com> schreef in bericht
news:Xns9823757FBDE6Fusenethoneypotrogers@127.0.0.1...
> "Cor Ligthert [MVP]" <notmyfirstn***@planet.nl> wrote in
> news:uO6qvbowGHA.4880@TK2MSFTNGP04.phx.gbl:
>
>> Spam Catcher,
>>
>> Do you really want to go that way, I have the idea that most in the
>> dotNet newsgroups don't like the Application Blocks,
>
>
> I know what you mean... I've used the latest Enterprise Libaries but they
> seem OK. Missing some features, but generally they're not hard to use.
>
> As for the Component UI block - what I'm hoping to do is a build a GUI
> which is extensible. I need the ability to plug in different GUI
> components depending on customer needs.
>
> A standard plugin interface would take too much trouble to build (i.e.
> I'll need a GUI interface, and some sort of background communications
> framework). For the most part, I *believe* CAB solves this and allows
> isolated components to talk to each other?
>
> So here's my problem:
>
> What's the best way to build an extensible GUI application which distinct
> components that need to talk to each other.
>
> For example:
>
> Customer A needs a Customer Screen + Custom Data Entry Form.
> Customer B needs a Customer Screen + Web Browser + Custom Logic
>
> I don't really want to rewrite my app for each customer ; )