-
Notifications
You must be signed in to change notification settings - Fork 767
v4.0.0 Migration Guide
With the release of v4.0.0, the Azure Naming Tool has been migrated to a .NET 8 Blazor Web App. This change modernizes the tool's architecture and ensures long-term support for the codebase. Due to the upgrade to .NET 8, the hosting environment will need to be updated to ensure proper functionality and the site configuration will need to be BACKED UP / RESTORED.
NOTE:
- After deployment, you will be prompted to set the Admin Password. Enter your desired password and confirm the site is running properly, then complete the configuration RESTORE process
1. BACKUP your current Azure Naming Tool installation
3. Review the Installation process for your environment
5. Deploy the tool using your desired Installation process
7. RESTORE your configuration
For v4.0.0, you are required to create a BACKUP of your configuration prior to the migration. Because the site will be running in .NET 8 framework, all previous configuration updates will need to be re-applied.
The v4.0.0 migration process requires a re-deployment of the code and an update to underlying hosting configuration to .NET 8.
To prepare for these changes, it is recommended that you create a backup of any customizations you have made to codebase for the tool (if any). These changes will need to be manually migrated to the your repository once it is updated.
It is recommended that users review the Installation process for their desired environment prior to the migration.
You will need to install/configure the .NET version in your hosting environment to ensure the Azure Naming Tool functions properly.
- If hosting in an Azure App Service, this setting can be changed in the App Service / Configuration / General Settings utility.
After selecting an Installation process, deploy the tool to your desired environment.
After deployment, you will be prompted to set the Admin Password. Enter your desired password and confirm the site is running properly.
After confirming the site is functioning properly, Restore your configuration.
- If hosting in a container with a volume attached, the configuration should be loaded automatically. If not, RESTORE your configuration.