Skip to content

Commit be6a1b6

Browse files
Update how-to-use-vs-designer-in-dotnet-core.md (#433)
1 parent 3e297f0 commit be6a1b6

File tree

1 file changed

+12
-17
lines changed

1 file changed

+12
-17
lines changed

knowledge-base/how-to-use-vs-designer-in-dotnet-core.md

Lines changed: 12 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -30,43 +30,38 @@ res_type: kb
3030

3131

3232
## 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.
3533

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.
3835

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.
3937

4038
## 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.
4441

4542
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:
4643

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_.
4845

4946
2. Add references to the following assemblies/NuGet packages in the project:
5047

5148
* __Telerik.Reporting__ - defines the needed report definition elements
5249
* __System.Resources.Extensions__ - needed to resolve the resources from the RESX file
5350

5451
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.
55-
![alt text](https://www.telerik.com/docs/default-source/knowledgebasearticleattachments/reporting/addexistingitem.png?sfvrsn=a3ec3f95_2 "Add Existing Item")
5652

57-
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.
53+
![alt text](https://www.telerik.com/docs/default-source/knowledgebasearticleattachments/reporting/addexistingitem.png?sfvrsn=a3ec3f95_2 "Add Existing Item")
54+
55+
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.
5856

59-
![alt text](https://www.telerik.com/docs/default-source/knowledgebasearticleattachments/reporting/addaslink.png?sfvrsn=b5e4fd9f_2 "Add As Link")
57+
![alt text](https://www.telerik.com/docs/default-source/knowledgebasearticleattachments/reporting/addaslink.png?sfvrsn=b5e4fd9f_2 "Add As Link")
6058

6159
4. Add in the same way also the RESX file of the report definition.
6260

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.
6662

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)
6964

7065
## See Also
66+
7167
[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)
72-

0 commit comments

Comments
 (0)