Question

The White UI Automation library makes extensive use of the Castle Project’s DynamicProxy 2. From what I understand, DynamicProxy is utilized to “wrap” MS UI Automation objects, and used to retrive objects inside their parent windows.

I need to understand if DynamicProxy is necessary and if it could be replaced with something faster, namely statically built classes instead of proxy classes generated at runtime, which IMO is unnecessary slowdown.

What exactly is DynamicProxy doing in the White library and can it be replaced? Any tips or pointers are appreciated.

Answer 1

I decided not to use White (and instead MS UI Automation directly), but I also use Castle Dynamic Proxy in my code. Here is a decent start at locating where it is used:

C:\Users\xxxx\Desktop\petmongrels-white-54723f8>findstr /s  /c:"ProxyCreator" /c:"CreateClassProxy" /c:"IInterceptor" *.cs
Components\Core\Source\CustomCommands\CustomCommandInterceptor.cs:    public class   CustomCommandInterceptor : IInterceptor
Components\Core\Source\Interceptors\CoreInterceptor.cs:    public class CoreInterceptor : IInterceptor
Components\Core\Source\UIItems\UIItemContainer.cs:            var interceptors = (IInterceptor[]) interceptorField.GetValue(customUIItem);
Components\Repository\Source\Interceptors\ScreenObjectInterceptor.cs:    public class  ScreenObjectInterceptor : IInterceptor
Components\Repository\Source\Interceptors\UIItemInterceptor.cs:    public class UIItemInterceptor : IInterceptor
Components\Repository\Source\Interceptors\WindowInterceptor.cs:    public class WindowInterceptor : IInterceptor
Components\Repository\Source\Services\ServiceInterceptor.cs:    public class ServiceInterceptor : IInterceptor

You can get the source at: https://github.com/petmongrels/white

(Mine is a bit out of date)