CommandsAdapters, Create vs Reuse

Topics: CAB & Smart Client Software Factory
Jun 5, 2007 at 9:12 AM
Hi all, When you use Command(<CommandName>).AddInvoke, it always creates a new instance of the CommandAdapter rather than re-using an existing adapter and calling CommandAdapter.AddInvoker on that instead. What's the reason behind this? It appears to be perfectly feasable to simpley reuse use the first instance found using FindAdapters and add the new invoker to that. I'm tempted to replace the CommandAdapterMapService so it only creates a single instances. I'm sure there's a valid reason why Commands need contain multiple CommandAdapters of the same type, can someone please enlighten me to what it is.