You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: knowledge-base/how-to-use-vs-designer-in-dotnet-core.md
+12-17Lines changed: 12 additions & 17 deletions
Original file line number
Diff line number
Diff line change
@@ -30,43 +30,38 @@ res_type: kb
30
30
31
31
32
32
## Description
33
-
Currently, the .NET Core frameworks do not support the design time components we need for the [Visual Studio Report Designer](../ui-report-designer). Without these components
34
-
we cannot provide a quality design-time experience.
35
33
36
-
This KB article describes a workaround for using the Visual Studio Report Designer to edit C Sharp reports hosted in
37
-
a .NET Core ClassLibrary project.
34
+
Currently, the .NET Core frameworks do not support the design time components we need for the [Visual Studio Report Designer]({%slug telerikreporting/designing-reports/report-designer-tools/desktop-designers/visual-studio-report-designer/overview%}). Without these components we cannot provide a quality design-time experience.
38
35
36
+
This KB article describes a workaround for using the Visual Studio Report Designer to edit C Sharp reports hosted in a .NET Core/5/6 ClassLibrary project.
39
37
40
38
## Suggested Workaround
41
-
The CSharp code of a report definition is identical in .NET Framework and in .NET Core. For that reason, it is possible to link the report definition files hosted in
42
-
a .NET Core ClassLibrary project to the corresponding files hosted in a .NET Framework ReportLibrary project. This way, all the changes made with the Visual Studio Report
43
-
Designer to the report in the .NET Framework project will be automatically applied to the .NET Core project.
39
+
40
+
The CSharp code of a report definition is identical in .NET Framework and in .NET Core. For that reason, it is possible to link the report definition files hosted in a .NET Core ClassLibrary project to the corresponding files hosted in a .NET Framework ReportLibrary project. This way, all the changes made with the Visual Studio Report Designer to the report in the .NET Framework project will be automatically applied to the .NET Core project.
44
41
45
42
Lets assume that we already have a ReportLibrary project in .NET Framework. Here are the necessary steps to link it to a .NET Core ClassLibrary project:
46
43
47
-
1. Create a new .NET Core 3.1 ClassLibrary project. You may delete the default CS file usually named _Class1.cs_.
44
+
1. Create a new .NET Core 3.1/5/6 ClassLibrary project. You may delete the default CS file usually named _Class1.cs_.
48
45
49
46
2. Add references to the following assemblies/NuGet packages in the project:
50
47
51
48
*__Telerik.Reporting__ - defines the needed report definition elements
52
49
*__System.Resources.Extensions__ - needed to resolve the resources from the RESX file
53
50
54
51
3. Add the corresponding CS report file from the .NET Framework project to the .NET Core project through the _Add_ -> _Existing Item..._ option of the project context menu.
When selecting the CS file make sure to select __Add As Link__ from the _Add Existing Item_ wizard. The corresponding DESIGNER.CS file will be added automatically.
When selecting the CS file make sure to select __Add As Link__ from the _Add Existing Item_ wizard. The corresponding DESIGNER.CS file will be added automatically.
58
56
59
-

57
+

60
58
61
59
4. Add in the same way also the RESX file of the report definition.
62
60
63
-
5. Reference the .NET Core ClassLibrary project in your .NET Core project hosting the Telerik Reporting engine. Pass the
64
-
[AssemblyQualifiedName](https://docs.microsoft.com/en-us/dotnet/api/system.type.assemblyqualifiedname?view=netcore-3.1) of the report class to the Reporting engine. Use
65
-
[TypeReportSourceResolver](../t-telerik-reporting-services-typereportsourceresolver) for resolving your reports in a Telerik Reporting REST Service.
61
+
5. Reference the .NET Core ClassLibrary project in your .NET Core project hosting the Telerik Reporting engine. Pass the [AssemblyQualifiedName](https://docs.microsoft.com/en-us/dotnet/api/system.type.assemblyqualifiedname?view=netcore-3.1) of the report class to the Reporting engine. Use [TypeReportSourceResolver](/reporting/api/Telerik.Reporting.Services.TypeReportSourceResolver.html) for resolving your reports in a Telerik Reporting REST Service.
66
62
67
-
A demo solution demonstrating the approach may be found in our GitHub repo -
68
-
[VS Designer in .NET Core](https://github.com/telerik/reporting-samples/tree/master/VS%20designer%20Core)
63
+
A demo solution demonstrating the approach may be found in our GitHub repo - [VS Designer in .NET Core](https://github.com/telerik/reporting-samples/tree/master/VS%20designer%20Core)
69
64
70
65
## See Also
66
+
71
67
[Make Visual Studio designer work with .NET Core](https://feedback.telerik.com/reporting/1383925-make-visual-studio-designer-work-with-net-core-a-k-a-sdk-style-projects)
0 commit comments