New features: TickerQ discovers and registers functions across assemblies.

[neozhu]

Based on the code excerpts, I can see the root cause of this issue. The problem lies in how TickerQ discovers and registers functions across assemblies.

Looking at src\TickerQ.Utilities\TickerFunctionProvider.cs, TickerQ uses a static registry to store functions:

public static class TickerFunctionProvider
{
    public static IReadOnlyDictionary<string, (string cronExpression, TickerTaskPriority Priority,
            TickerFunctionDelegate Delegate)>
        TickerFunctions
    { get; private set; }

    public static void RegisterFunctions(
        IDictionary<string, (string, TickerTaskPriority, TickerFunctionDelegate)> functions)
    {
        TickerFunctions =
            new ReadOnlyDictionary<string, (string, TickerTaskPriority, TickerFunctionDelegate)>(functions);
    }
}

The issue is that TickerQ relies on source generators (as mentioned in the README) to discover and register [TickerFunction] methods. Source generators typically run at compile time and generate code within the same assembly where the attributes are found.

When you split your [TickerFunction] methods across different assemblies:

1. Setup A & B fail because the source generator in the application layer assembly generates registration code, but the web project (where UseTickerQ() is called) doesn't have access to that generated registration code.

2. Setup C works because both the [TickerFunction] methods and UseTickerQ() are in the same assembly, so the source generator can properly register the functions in the same context where they're being used.

Potential Solutions:

1. Manual Registration: You might need to manually call registration methods from your application layer in the startup project.

2. Assembly Scanning: TickerQ might need to implement assembly scanning to discover functions across referenced assemblies.

3. Explicit Registration: There might be an API to explicitly register functions from other assemblies that isn't documented in the provided excerpts.

To confirm this diagnosis, you could check if there are any registration methods or assembly scanning options in the TickerQ configuration that would allow cross-assembly function discovery.

[cgoudieemi]

Has this been logged as a bug? Seems like a HUGE oversight?

[arcenox]

there is on new version support for assembly scanning, and is documented on docs.