ApplicationException should not be used http://blogs.msdn.com/kcwalina/archive/2006/06/23/644822.aspx http://www.codinghorror.com/blog/archives/000112.html
but it is used in several places in IOC \Castle.MicroKernel\ComponentActivator\ComponentActivatorException.cs \Castle.MicroKernel\Exceptions\ComponentNotFoundException.cs \Castle.MicroKernel\Exceptions\ComponentRegistrationException.cs \Castle.MicroKernel\Exceptions\KernelException.cs \Castle.MicroKernel\Facilities\FacilityException.cs \Castle.MicroKernel\Handlers\HandlerException.cs \Castle.MicroKernel\Lifestyle\Pool\PoolException.cs \Castle.MicroKernel\Resolvers\DependencyResolverException.cs \Castle.MicroKernel\SubSystems\Conversion\ConverterException.cs \Castle.Windsor\Proxy\AbstractProxyFactory.cs \Castle.Windsor\Proxy\AbstractProxyFactory.cs The reason I am looking at this is that there is no ApplicationException in silverlight This is an easy change to get rid of it but it is a breaking change because it changes the exception hierachy. there are two options 1. remove all usages of ApplicationException 2. remove uages of ApplicationException from silverlight and use compiler directives my vote is for 1. Thoughts? -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
