-
Notifications
You must be signed in to change notification settings - Fork 80
docs: introduced vs integration upgrade wizard article #1268
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
08d79a6
docs: introduced vs integration upgrade wizard article
yanisslav e94b2a5
apply suggested changes
yanisslav 3fafa2b
Update getting-started/vs-integration/upgrade-wizard.md
ntacheva d2ee680
Update getting-started/vs-integration/upgrade-wizard.md
ntacheva 043cbb5
Update getting-started/vs-integration/upgrade-wizard.md
ntacheva File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+61.1 KB
getting-started/vs-integration/images/upgrade-wizard-localization-file-invalid.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file added
BIN
+78.5 KB
getting-started/vs-integration/images/upgrade-wizard-localization-file.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,87 @@ | ||
| --- | ||
| title: Upgrading Projects | ||
| page_title: Upgrade Project - Visual Studio Integration | ||
| description: Learn how to upgrade a Telerik UI for Blazor project with our Visual Studio Extension. | ||
| slug: getting-started-vs-integration-upgrade-project | ||
| position: 5 | ||
| --- | ||
|
|
||
| # Upgrading Projects | ||
|
|
||
| This article demonstrates how to use the [Telerik Visual Studio Extension]({% slug getting-started-vs-integration-overview %}) to upgrade a project that is pre-configured for the Progress® Telerik® UI for Blazor components. | ||
|
|
||
| ## Basics | ||
|
|
||
| The **Upgrade Project Wizard** upgrades the version of existing Telerik UI for Blazor applications. To open the wizard, right-click on the **Project in the Solution Explorer -> Telerik UI for Blazor -> Upgrade Wizard**. | ||
|
|
||
|  | ||
|
|
||
| ## Files for Upgrade | ||
|
|
||
| The **Upgrade Information** step of the Upgrade Project Wizard describes the files and assemblies that will be upgraded. | ||
|
|
||
|  | ||
|
|
||
| The Telerik Blazor Upgrade Wizard will do the following: | ||
|
|
||
| * Update the version of the referenced Blazor NuGet package. It will also update the package source in the solution-based NuGet config file. | ||
| * It will update the version of the theme references (If CDN is used, it will be also updated). | ||
| * It will update all local script and style and NuGet package references in case client upgrades from Trial to Dev version. | ||
| * It will add the new keys in the default (English) localization file. | ||
|
|
||
| ## Projects for Upgrade | ||
|
|
||
| The next page of the Upgrade Wizard lists all projects from the solution that use Telerik UI for Blazor. Choose the projects that you want to upgrade and the version to which they will be upgraded. | ||
|
|
||
| >tip We recommend selecting all projects that reference UI for Blazor and upgrading them to the same product version. | ||
|
|
||
|  | ||
|
|
||
| ## Upgrade Localization File | ||
|
|
||
| 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. | ||
|
|
||
| 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. | ||
|
|
||
|  | ||
|
|
||
| ## Create Backup | ||
|
|
||
| You can create a backup before running the upgrade wizard by selecting the **Create a backup before upgrading** option. | ||
|
|
||
| >When the project and solution are placed in the same directory, the default backup location is set to the **%USERPROFILE%\Documents** folder. | ||
|
|
||
|  | ||
|
|
||
|
|
||
| ## Upgrade Log | ||
|
|
||
| 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. | ||
|
|
||
|  | ||
|
|
||
| ## Troubleshooting | ||
|
|
||
| The following common problems might occur when upgrading a project: | ||
|
|
||
| * The [localization file is read-only or does not exists](#missing-localization-file). | ||
| * The [**Finish** button is disabled](#finish-button-is-disabled). | ||
|
|
||
| ### Missing Localization file | ||
|
|
||
| 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. | ||
|
|
||
|  | ||
|
|
||
| ### Finish Button is Disabled | ||
|
|
||
| If **Create a backup before upgrading** option is selected, and the **Backup location** is empty, the **Finish** button is disabled. | ||
|
|
||
| ## See Also | ||
|
|
||
| * [Visual Studio Extensions Overview]({% slug getting-started-vs-integration-overview %}) | ||
| * [Downloading the Latest Telerik UI for Blazor Versions]({% slug getting-started-vs-integration-latest-version %}) | ||
| * [Getting Started with Client-Side Apps]({%slug getting-started/client-side%}) | ||
| * [Getting Started with Server-Side Apps]({%slug getting-started/server-side%}) | ||
| * [Workflow for Using the UI Components for Blazor]({%slug getting-started/what-you-need%}) | ||
|
|
||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.