Hi,

>Coming from VFP my tendency is to want to subclass the Application object in my libraries.
>
>Library:
>

>public abstract class MYApplication : System.Windows.Application
>

>
>Application:
>

>public partial class myApp : MYApplication
>

>
>But I have a few questions...
>
>Is this an unusual way to do this?
>
>Any downside?

Can't think of any....

>Any upside? <g>

IMO: the ability to override the methods (and handle the events) of the base S.W.Application class. Essentially the same arguments as in VFP I guess - if you want to add global functionality later the plumbing is in place.

>In looking at it I think it may actually make application setup more complex than the way I am doing it now. (Creating a separate class to the side that contains my application wide static properties and methods.) Was just curious as to what is the common way to do this.

Probably no harm in mixing both approachs ?
Regards,
Viv