How does the ExecuteAttribute work

[StefanOssendorf]

Hi.

How exactly is the ExecuteAttribute supposed to be used?
I know the following works:

class FooCommand : CommandBase<FooCommand> {
    [Create]
    private void Create(...) { ... }
    [Execute]
    private void Execute() { .... }
}

According to the new CSLA8 eBook it should also be possible (this works with CommandBase<> and the current pre-release)

[Serializable]
public class Bar : ReadOnlyBase<Bar> {
    [Execute]
    private void Execute(string name) {
        Console.WriteLine(name);
    }
}

But with this I alway get an exception like:

Csla.DataPortalException
  HResult=0x80131500
  Message=DataPortal.Fetch failed (Csla.ReadOnlyBase`1[[Krznbf.Bar, CslaDataPortalExtGenAnalyzerTestConsole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]].[Fetch](String))
  Source=Csla
  StackTrace:

  This exception was originally thrown at this call stack:
    Csla.Reflection.ServiceProviderMethodCaller.FindDataPortalMethod<T>(System.Type, object[], bool) in ServiceProviderMethodCaller.cs
    Csla.Reflection.ServiceProviderMethodCaller.FindDataPortalMethod<T>(System.Type, object[], bool) in ServiceProviderMethodCaller.cs

Inner Exception 1:
TargetParameterCountException: Krznbf.Bar.[Fetch](String)

Inner Exception 2:
TargetParameterCountException: Csla.ReadOnlyBase`1[[Krznbf.Bar, CslaDataPortalExtGenAnalyzerTestConsole, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null]].[Fetch](String)

Inner Exception 3:
TargetParameterCountException: Csla.Core.BindableBase.[Fetch](String)

Inner Exception 4:
TargetParameterCountException: Csla.Core.MobileObject.[Fetch](String)

Inner Exception 5:
TargetParameterCountException: System.Object.[Fetch](String)

Do I misuse the ExecuteAttribute here?
If so, wouldn't be an Analyzer who reports those usages be helpful?

Cheers
Stefan

[rockfordlhotka]

The Execute attribute only works with CommandBase types.

You can use it the original way, by creating a command object and then executing it, or you can use it the new way by calling execute to create the command (like a fetch basically).

[StefanOssendorf]

That sounds like it would be awesome to have an analyzer which triggers a warning/error when declaring an ExecuteAttribute within a non CommandBase<T> (or ICommandBase/Object?).