> Does anyone have any input on setting up my CAB application so that the
> application is thread safe, and cached appropiately? I read that this
> can be managed through Services, and dynamic injection. On the
> contrary, I was told that this can be handled using Enterprise Library
> cached application block. Last, but not least, i read you can implement
> this at the class level, creating immutable classes, and caching them
> accordingly. Any suggestions would be greatly appreciated?
>

On Jan 25, 7:31 pm, "Bob Powell [MVP]" <bob@_spamkiller_bobpowell.net>
wrote:
> All UI operations must be carried out on the UI thread. Therefore you
> still need to make the distinction in CAB whether the operation is a
> graphical one or not.
>
> A service dependency for example may work well on some other thread but
> a UI operation will not.
>
> CAB only connects up the various parts of the application. Those parts
> all need to respect the basic principals.
>
> --
> Bob Powell [MVP]
> Visual C#, System.Drawing
>
> Ramuseco Limited .NET consultinghttp://www.ramuseco.com
>
> Find great Windows Forms articles in Windows Forms Tips and Trickshttp://www.bobpowell.net/tipstricks.htm
>
> Answer those GDI+ questions with the GDI+ FAQhttp://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.
>
> lwhitb1 wrote:
> > Does anyone have any input on setting up my CAB application so that the
> > application is thread safe, and cached appropiately? I read that this
> > can be managed through Services, and dynamic injection. On the
> > contrary, I was told that this can be handled using Enterprise Library
> > cached application block. Last, but not least, i read you can implement
> > this at the class level, creating immutable classes, and caching them
> > accordingly. Any suggestions would be greatly appreciated?