Hello Frantisek,

I am sorry to hear that you are still experiencing issues with using the functions.

May I ask which framework the project targets? Also, the project that contains the logic for the functions? Please, make sure that the dependent assemblies don't have their own dependent assemblies. You may also test the approach from Assembly Used in ObjectDataSource is Not Loaded by the Standalone Report Designer KB article.

When it comes to "I still don't understand why some reports, that no use aggregate functions - shotdown very often and some don't shutdown any time.", in such situations if you have attached Trace Listener, the generated log file should provide more information. 

Regards,

Neli
Progress Telerik

Hi Frantisek,

Thank you for the logs.

I noticed that the assemblies Mn_Settings and ValidationSupport cannot be loaded for some reason. They seem to be dependencies for the functions GetReport in type Mn_Mirror.Reporting.ReportExtensions and IsCorrespondingVatRate in type Mn_Mirror.Reporting.ReportFeatures, correspondingly. Mn_Mirror.Reporting seems to be the namespace/assembly with the aggregate functions you sent previously.

Note that the log specifies where the Visual Studio has attempted to find the dlls. I suggest adding the assemblies in one of these paths and checking whether the issue would be resolved.

Regards,
Todor
Progress Telerik

Hello Frantisek,

The error message states that there is a problem while loading the aggregate functions. It is not necessary for the report to use an aggregate function. Our code tries to load the functions from the available assemblies in order to use them if they occur in an Expression. Here is the code of the function:

public static IList<AggregateFunctionInfo> GetAggregateFunctions(IServiceProvider provider)
{
    var list = new List<AggregateFunctionInfo>();
    var loader = new AggregateFunctionLoader(list)
        .LoadFrom(AppDomain.CurrentDomain.GetAssemblies());

    if(null != provider)
    {
        loader.LoadFrom(((AssemblyRefManager)provider.GetService(typeof(AssemblyRefManager))).GetAssemblies());
        var discoSvc = (ITypeDiscoveryService)provider.GetService(typeof(ITypeDiscoveryService));
        ICollection types = null;
        try
        {
            types = discoSvc?.GetTypes(typeof(IAggregateFunction), true);
            if (null != types)
            {
                loader.LoadFrom(types.Cast<Type>());
            }
            else
            {
                Trace.WriteLine("TypeDiscoveryService.GetTypes returns null.");
            }
        }
        catch (Exception ex)
        {
            Trace.WriteLine("Exception occur while resolving the aggregates:");
            Trace.WriteLine(ex);
        }
    }

    
    // Design time uses only the Visible aggregates
    return list.FindAll(info => info.IsVisible);
}

I cannot see a potential source for the unhandled null reference exception.

To troubleshoot further, can you attach a trace listener to the Visual Studio application? Please, see the article section Visual Studio Crashes for more details. I hope the trace log will give more information on what exactly fails and why.

Regards,
Todor
Progress Telerik

Hello Frantisek,

Thank you for the provided resources. I modified the code of WeekDayAgregate.cs and MonthDayAgregate.cs to compensate for the lack of two custom assemblies and created the IDatePrint interface. I added the functions to our demo ReportLibrary project. They were recognized by the designer - see the linked screenshot. I modified one of our demo reports multiple times using the custom aggregates. I didn't experience any issues.

Do you observe the problem when previewing a report using the custom aggregates from Visual Studio Report Designer? If so, please, note that custom aggregates are not supported when you preview the report in Visual Studio. To see the aggregate output, use a ReportViewer control. See Extending Reporting Engine with User Functions article section for more details.

Regards,
Todor
Progress Telerik

Hi Frantisek,

I'm afraid the attached archive is empty - see the linked screenshot for reference. Note that the GUID before the archive name is attached automatically by our system.

Regards,
Todor
Progress Telerik

Hi Frantisek,

Indeed, the Stack trace of the error indicates that the designer cannot find the Aggregate Functions. Do you use any custom aggregate functions? Or other custom types that need to be resolved by the designer? If so, can you send us the custom types to test locally?

We are aware of an issue where Visual Studio cannot resolve some types. Note that we don't guarantee this as the designer utilizes the ITypeDiscoveryService Interface to discover available types at design time and we cannot control it. A similar error is discussed in the ITypeDiscoveryService.GetTypes is throwing exceptions thread started by one of our developers.

Regards,
Todor
Progress Telerik