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: installation.md
+34-48Lines changed: 34 additions & 48 deletions
Original file line number
Diff line number
Diff line change
@@ -10,60 +10,59 @@ position: 3
10
10
11
11
# Installation
12
12
13
-
Telerik Reporting supports several approaches for installing the product.
13
+
Telerik Reporting supports several approaches for installing the product.
14
14
15
-
*[Downloading Telerik Control Panel](http://www.telerik.com/blogs/optimizing-use-of-the-telerik-control-panel) − To download and install the Control Panel, log into your[Telerik account](https://www.telerik.com/account/). Telerik Control Panel uses the product MSI file.
15
+
*[Downloading Telerik Control Panel](http://www.telerik.com/blogs/optimizing-use-of-the-telerik-control-panel) − To download and install the Control Panel, log into your[Telerik account](https://www.telerik.com/account/). Telerik Control Panel uses the product MSI file.
16
16
17
-
*[Using the Telerik NuGet private feed](https://nuget.telerik.com/v3/index.json) −The Telerik Reporting NuGet packages contain the libraries for.NET Core projects, the Reporting Engine, and the implementation of the[Reporting REST WebAPI-based service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-web-api-implementation/overview%}) where you can use the packages with the standard.NET 4.6.1 framework. The NuGet packages do not include design-time support. To install the Telerik Reporting NuGet packages, log into your [Telerik account](https://www.telerik.com/account/).
17
+
*[Using the Telerik NuGet private feed](https://nuget.telerik.com/v3/index.json) −The Telerik Reporting NuGet packages contain the libraries for.NET Core projects, the Reporting Engine, and the implementation of the[Reporting REST WebAPI-based service]({%slug telerikreporting/using-reports-in-applications/host-the-report-engine-remotely/telerik-reporting-rest-services/asp.net-web-api-implementation/overview%}) where you can use the packages with the standard.NET 4.6.1 framework. The NuGet packages do not include design-time support. To install the Telerik Reporting NuGet packages, log into your [Telerik account](https://www.telerik.com/account/).
18
18
19
-
>note The legacy https://nuget.telerik.com/nuget server will be deprecated. Make sure to switch to the new https://nuget.telerik.com/v3/index.json server, which is faster, lighter, and reduces the number of requests from your NuGet client. For more information on how to add a NuGet feed, refer to the [official Microsoft documentation](https://www.visualstudio.com/en-us/docs/package/nuget/consume).
19
+
>note The legacy https://nuget.telerik.com/nuget server will be deprecated. Make sure to switch to the new https://nuget.telerik.com/v3/index.json server, which is faster, lighter, and reduces the number of requests from your NuGet client. For more information on how to add a NuGet feed, refer to the [official Microsoft documentation](https://www.visualstudio.com/en-us/docs/package/nuget/consume).
20
20
21
-
* Using the MSI installer−MSI files handle the automatic local installation of the product and its storing into a __Program Files__> __Progress__folder. They also create the necessary virtual folders and projects, and provide all required files for developing with Telerik Reporting.
21
+
* Using the MSI installer−MSI files handle the automatic local installation of the product and its storing into a __Program Files__ > __Progress__ folder. They also create the necessary virtual folders and projects, and provide all required files for developing with Telerik Reporting.
To install Telerik Reporting through the MSI automatic installer file:
29
+
To install Telerik Reporting through the MSI automatic installer file:
30
30
31
-
1. Log into your [Telerik account](https://www.telerik.com/account).
31
+
1. Log into your [Telerik account](https://www.telerik.com/account).
32
32
33
-
1. Click the __Downloads__ tab to view the available trial and commercial products.
33
+
1. Click the __Downloads__ tab to view the available trial and commercial products.
34
34
35
-
1. Select the __Telerik Reporting__product.
35
+
1. Select the __Telerik Reporting__ product.
36
36
37
-
1. From the next page, download the MSI installation and the documentation files. The source code is available for download only for commercial-license holders.
37
+
1. From the next page, download the MSI installation and the documentation files. The source code is available for download only for commercial-license holders.
38
38
39
39
1. Download the automatic installation MSI file.
40
40
41
-
1. When the download completes, run `Telerik_Reporting_[suiteversion].msi` and follow the instructions of the Wizzard.
41
+
1. When the download completes, run `Telerik_Reporting_[suiteversion].msi` and follow the instructions of the Wizzard.
42
42
43
-
To access internal builds:
43
+
To access internal builds:
44
44
45
-
1. Log into your [Telerik account](https://www.telerik.com/account).
45
+
1. Log into your [Telerik account](https://www.telerik.com/account).
46
46
47
-
1. For the latest internal builds, navigate to __Latest Internal Build__ under __Downloads__. For internal builds from earlier releases, select the respective Telerik Reporting version.
48
-
49
-
>note The __Downloads__ page lists previously downloaded products. For any missing products or product versions, contact the Sales team through the support ticketing system by submitting a [__General Feedback__](https://www.telerik.com/account/support-tickets/general-feedback) thread.
47
+
1. For the latest internal builds, navigate to __Latest Internal Build__ under __Downloads__. For internal builds from earlier releases, select the respective Telerik Reporting version.
50
48
49
+
>note The __Downloads__ page lists previously downloaded products. For any missing products or product versions, contact the Sales team through the support ticketing system by submitting a [__General Feedback__](https://www.telerik.com/account/support-tickets/general-feedback) thread.
51
50
52
51
## Installing Telerik Reporting
53
52
54
-
1. In the dialog which appears after you execute the MSI file, confirm that you have read and accepted the License Agreement.
53
+
1. In the dialog which appears after you execute the MSI file, confirm that you have read and accepted the License Agreement.
55
54
56
55
57
56
58
-
1. In the next customization dialog, select the desired features.
57
+
1. In the next customization dialog, select the desired features.
59
58
60
-
+ If Telerik Reporting does not locate a local SQL server instance on your machine or if your SQL browser service is stopped, the examples from the __Examples__dialog option will be installed but the configuration files for the application will not have valid connection strings. However, you can still access the working demos on the [Telerik Reporting Demos page](http://demos.telerik.com/reporting).
59
+
+ If Telerik Reporting does not locate a local SQL server instance on your machine or if your SQL browser service is stopped, the examples from the __Examples__ dialog option will be installed but the configuration files for the application will not have valid connection strings. However, you can still access the working demos on the [Telerik Reporting Demos page](http://demos.telerik.com/reporting).
61
60
62
-
+ To set up the examples and the used connection string, select __Examples Setup__. All local SQL Server 2005+ instances are supported.
61
+
+ To set up the examples and the used connection string, select __Examples Setup__. All local SQL Server 2005+ instances are supported.
63
62
64
-
+ The examples use the MS SQL Server [AdventureWorks database](http://msdn.microsoft.com/en-us/library/ms124659%28SQL.100%29.aspx). Unless already available on your machine, the AdventureWorks database will also be deployed locally.
63
+
+ The examples use the MS SQL Server [AdventureWorks database](http://msdn.microsoft.com/en-us/library/ms124659%28SQL.100%29.aspx). Unless already available on your machine, the AdventureWorks database will also be deployed locally.
65
64
66
-
+ Alternatively, you can install AdventureWorks by manually executing the SQL script from the installer. To use this option, navigate to __[InstallDir]/Examples/Data/AdventureWorks OLTP__. For the script to run correctly, uncomment the `SET @data_path = 'C:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks OLTP\';` statement and specify the correct path to the CVS data files which are in the same folder as the SQL script file.
65
+
+ Alternatively, you can install AdventureWorks by manually executing the SQL script from the installer. To use this option, navigate to __[InstallDir]/Examples/Data/AdventureWorks OLTP__. For the script to run correctly, uncomment the `SET @data_path = 'C:\Program Files\Microsoft SQL Server\90\Tools\Samples\AdventureWorks OLTP\';` statement and specify the correct path to the CVS data files which are in the same folder as the SQL script file.
67
66
68
67
69
68
@@ -75,30 +74,26 @@ To access internal builds:
75
74
76
75
## Directories and Assemblies
77
76
78
-
By default, the Wizard installs Telerik Reporting in the following locations:
79
-
80
-
* For 64-bit machines, in ` C:\Program Files\Progress\Telerik Reporting {{site.suiteversion}}`.
77
+
By default, the Wizard installs Telerik Reporting in the following locations:
81
78
82
-
* For 32-bit machines, in ` C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}`.
79
+
* For 64-bit machines, in ` C:\Program Files\Progress\Telerik Reporting {{site.suiteversion}}`.
83
80
84
-
The assemblies targeting different versions of.NET are placed in separate folders, as shown in the list below:
81
+
* For 32-bit machines, in ` C:\Program Files (x86)\Progress\Telerik Reporting {{site.suiteversion}}`.
85
82
86
-
*.NET Framework - *\Bin*
83
+
The assemblies targeting different versions of .NET are placed in separate folders, as shown in the list below:
87
84
88
-
*.NET Standard - *\Bin\netstandard2.0*
85
+
*.NET Framework - *\Bin*
89
86
90
-
*.NET Core - *\Bin\netcoreapp3.1*
87
+
*.NET Standard - *\Bin\netstandard2.0*
91
88
92
-
*.NET 5 - *\Bin\net5.0* and *\Bin\net5.0-windows*
89
+
*.NET Core - *\Bin\netcoreapp3.1*
93
90
94
-
*.NET 6 - *\Bin\net6.0* and *\Bin\net6.0-windows*
95
-
96
-
>important Since.NET 6 is currently available as a Preview, compiling a.NET 6 application requires installing the latest [.NET 6 SDK](https://dotnet.microsoft.com/download/dotnet/6.0) and using [Visual Studio 2019 Preview](https://visualstudio.microsoft.com/vs/preview/), or allowing to use the previews of the.NET SDK in the __Tools/Environment/Preview Features__ in Visual Studio 2019.
91
+
* .NET 5 - *\Bin\net5.0* and *\Bin\net5.0-windows*
97
92
93
+
* .NET 6 - *\Bin\net6.0* and *\Bin\net6.0-windows*
98
94
99
95
The following tables describe the folder structure for the redistributable assemblies.
0 commit comments