Using wildcards for assemblyReferences version

[Karl]

Is there any way to use wildcards for the version number of assemblyReferences for the Visual Studio designer? My package versions are updated every time they are compiled to ensure unique version numbers, obviously this means the version numbers that I have manually added to the config are out of date as soon as the project is compiled to run. I saw an old post saying the version can be removed for the sand alone designer, but what about the visual studio designer? Nothing I have tried has worked (removing the version number, using 1.0.*.*, etc).  I am using the newest version of the reporting tools.

[Stef]

Hi Karl,

If you are using Telerik Reports from a signed assembly, you can specify the report by its assembly qualified name like <namespace>.<report_class>, <assembly_name>.

If you are using data objects from a signed assembly, then you need security settings loading the external assemblies for the Reporting Engine. You can specify the version with * e.g.:

<configSections>
    <section name="Telerik.Reporting" type="Telerik.Reporting.Configuration.ReportingConfigurationSection, Telerik.Reporting, Version=11.1.17.614, Culture=neutral, PublicKeyToken=a9d7983dfcc261be" />
</configSections>
<Telerik.Reporting>
    <Cache provider="" />
    <cache provider="" />
    <assemblyReferences>
        <add name="SignedAssemblyTest" version="1.*.*.*" />
    </assemblyReferences>
    <SessionState provider="" />
    <restReportService>
        <storage provider="" />
        <reportResolver provider="" />
    </restReportService>
</Telerik.Reporting>

The above must be in the ClassLibrary holding the reports, and in the project where reports are processed and rendered.


The attached demo projects illustrate the settings. The report displayed by the viewer is Report1 from ClassLibrary1. Report1 in SignedAssemblyTest is used as a sub report in Report1 of ClasLibrary1 to illustrate how it can be specified without the version.


If I am misunderstanding the scenario, please provide steps how to reproduce the issue locally.

Regards,
Stef
Progress Telerik