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: getting-started/vs-integration/configure-project-wizard.md
+3-4Lines changed: 3 additions & 4 deletions
Original file line number
Diff line number
Diff line change
@@ -24,15 +24,14 @@ The configuration wizard handles the following tasks:
24
24
25
25
The **Theme Selection** page enables you to change the [CSS theme]({%slug themes-built-in%}) of your Telerik UI for Blazor application.
26
26
27
-

28
-
29
27
After selecting the desired theme, click **Next** to navigate to the [Project Settings](#project-settings) page.
30
28
31
29
## Project Settings
32
30
33
-
The **Project Settings** page allows you to enable or disable the [Telerik UI CDN support]({%slug common-features-cdn%}). Note that this can affect the future [upgrade process of the theme]({%slug getting-started-vs-integration-new-project%}#step-3-configure-additional-project-settings).
31
+
The **Project Settings** page allows you to enable or disable:
34
32
35
-

33
+
* The [Telerik UI CDN support]({%slug common-features-cdn%}). Note that this can affect the future [upgrade process of the theme]({%slug upgrade-tutorial%}#upgrade-process).
34
+
* The [Font Icons]({%slug common-features-icons%}) in the project.
* Choose a particular version to add to the project.
74
+
* Configure additional project settings like:
75
+
* Load the required Telerik UI stylesheet and JS Interop file as [static assets]({%slug getting-started/what-you-need%}#css-theme-and-javascript-files) or from the [Telerik CDN]({%slug common-features-cdn%}).
* Use [font icons]({%slug common-features-icons%}) instead of the default SVG icons.
78
+
79
+
### Step 2: Select Theme
80
+
81
+
In this step, you can apply one of the available [themes]({%slug themes-built-in%}) to your project.
82
+
83
+
### Step 3: Create a Backup
84
+
85
+
You can choose to back up the project state before the conversion (in a folder called `<ProjectName>_Backup>_<timestamp>`).
72
86
73
87
## Troubleshooting
74
88
@@ -80,14 +94,10 @@ When converting a project, you may encounter the following most common issues:
80
94
81
95
### Error Screen
82
96
83
-
If you see an error screen similar to the one below, make sure that the actual Blazor application is selected in the Solution Explorer. This is most common with WebAssembly types of applications as they consist of a server and shared projects by default, and only the client project is the actual Blazor app that needs the Telerik components.
97
+
If you see an error screen in the wizard, make sure that you have selected the UI project in the Solution Explorer. For example, the Issue can occur in WebAssembly apps as they can include a Server and Shared projects, and only the Client project is the actual Blazor UI app that needs the Telerik components.
84
98
85
99
Some specific project settings can also cause an exception during conversion. The fastest solution is to [manually configure the project for the Telerik components]({%slug getting-started/what-you-need%}).
86
100
87
-
>caption Error screen when the project can't be converted
Copy file name to clipboardExpand all lines: getting-started/vs-integration/latest-version-retrieval.md
+1-7Lines changed: 1 addition & 7 deletions
Original file line number
Diff line number
Diff line change
@@ -24,19 +24,13 @@ Clicking the **Get Latest** button in the [Create New Project]({% slug getting-s
24
24
25
25
1. Click on the LOG IN button. This will open a browser window with a login form on the telerik.com website.
26
26
27
-

28
-
29
27
>tip For more information on the latest available versions, see the [Telerik UI for Blazor release notes](https://www.telerik.com/support/whats-new/blazor-ui/release-history).
30
28
31
29
1. Enter your Telerik credentials in the browser. If you do not have a [www.telerik.com](https://www.telerik.com) account, then create a new one.
32
30
1. Return to Visual Studio and confirm any privacy-related requests.
33
31
1. In the next dialog that appears, click the **Download** button.
34
32
35
-

36
-
37
-
1. Return to the [Create New Project]({% slug getting-started-vs-integration-new-project %}) wizard and select the newly downloaded version from the drop-down menu.
38
-
39
-

33
+
1. Return to the [Create New Project]({% slug getting-started-vs-integration-new-project %}) wizard and select the newly downloaded version.
40
34
41
35
The Latest Version Acquirer tool downloads a `.zip` file that contains the latest Telerik UI for Blazor packages. By default, the file is saved in the `%APPDATA%\Telerik\Updates` folder. If the list with the offered packages gets too long and you do not need the prior versions, close VS and use the Windows Explorer to delete these distributions.
* Hosting model—the options vary depending on the selected target framework.
71
+
* Configure additional project settings like:
72
+
* Load the required Telerik UI stylesheet and JS Interop file as [static assets]({%slug getting-started/what-you-need%}#css-theme-and-javascript-files) or from the [Telerik CDN]({%slug common-features-cdn%}). Note that this can affect the future [upgrade process of the theme]({%slug upgrade-tutorial%}#upgrade-process).
* Use [font icons]({%slug common-features-icons%}) instead of the default SVG icons.
67
75
* Location from where the application will get the Telerik UI for Blazor package—[remote NuGet feed]({%slug installation/nuget%}) or local files.
68
76
* Telerik UI for Blazor version.
69
77
@@ -82,19 +90,7 @@ The **Create New Project** wizard provides the following project templates:
82
90
***Dashboard**—A basic dashboard layout that uses the TileLayout component for customizable dashboards, and showcases several ways individual blocks (tiles) can fetch data.
83
91
***Admin**—A small app that shows a dashboard for admin. The app uses some of the main Telerik UI components like the [Data Grid]({%slug grid-overview%}), [Chart]({%slug components/chart/overview%}), [TileLayout]({%slug tilelayout-overview%}), [Form]({%slug form-overview%}), and more.
84
92
85
-
### Step 3: Configure Additional Project Settings
86
-
87
-
This screen lets you choose:
88
-
89
-
* Whether to import the required Telerik UI stylesheet and JS Interop file by using the [static assets]({%slug getting-started/what-you-need%}#css-theme-and-javascript-files) or the [CDN method]({%slug common-features-cdn%}).
90
-
* Whether to use [localization]({%slug globalization-localization%}) in the project or not.
91
-
* Whether to use [Font Icons]({%slug common-features-icons%}) in the project or the default SVG icons.
92
-
93
-
#### Using Local Theme
94
-
95
-
When using a local theme, the CSS file is saved locally in the `wwwroot/lib/blazor-ui/styles` folder of the application. With this configuration, upgrading UI for Blazor requires you to [replace this CSS file manually]({%slug upgrade-tutorial%}).
96
-
97
-
### Step 4: Select Theme
93
+
### Step 3: Select Theme
98
94
99
95
Finally, you can apply one of the available [themes]({%slug themes-built-in%}) to your project.
If localization is enabled in the application, you can select the **Upgrade the localization file** option. The Upgrade Wizard will add new localization keys from the default (English) localization file that UI for Blazor distributes.
43
39
44
-
The option is selected by default if there is a **Resources\TelerikMessages.resx** file in the current project. In this case, **Resources\TelerikMessages.resx** file is selected in the file browser.
The option is selected by default if there is a `Resources\TelerikMessages.resx` file in the current project. In this case, `Resources\TelerikMessages.resx` file is selected in the file browser.
47
41
48
42
## Create Backup
49
43
50
44
You can create a backup before running the upgrade wizard by selecting the **Create a backup before upgrading** option.
51
45
52
-
>When the project and solution are placed in the same directory, the default backup location is set to the **%USERPROFILE%\Documents** folder.
>When the project and solution are placed in the same directory, the default backup location is set to the `%USERPROFILE%\Documents` folder.
56
47
57
48
## Upgrade Log
58
49
59
-
In case one of the options ([Create a backup before upgrading](#create-backup) or [Upgrade the localization file](#upgrade-localization-file)) is selected, an **Upgrade Log** will be opened in your default browser at the end of the upgrade. The log can show the backup location, an entry for each localization key added or a localization upgrade error. Each upgrade log file is in HTML format. The file name contains the date and time of the upgrade.
In case one of the options ([Create a backup before upgrading](#create-backup) or [Upgrade the localization file](#upgrade-localization-file)) is selected, an **Upgrade Log** will open at the end of the upgrade. The log can show the backup location, an entry for each localization key added or a localization upgrade error. Each upgrade log file is in HTML format. The file name contains the date and time of the upgrade.
62
51
63
52
## Troubleshooting
64
53
65
-
The following common problems might occur when upgrading a project:
66
-
67
-
* The [localization file is read-only or does not exists](#missing-localization-file).
68
-
* The [**Finish** button is disabled](#finish-button-is-disabled).
69
-
70
-
### Missing Localization file
71
-
72
-
If the selected localization file in the pointed directory is missing or read-only, the page state is not valid. In this case, the **Finish** button will display a tooltip when clicked, indicating a page error.
0 commit comments