All geek questions in one place

Migrate your existing DotNetNuke portal to windows azure

Now I am switching from my shared host to azure, and I have migrated my asp.net applications to azure / sql azure. For mvc3 / 4 sites, I had to change the membership providers to the Universal Membership provider to force them to sit on SQL Azure. Now I need to make dnn sites, and I can’t figure out which strategy to use. I tried creating a script database with the For SQL Azure option, but getting a ton of errors, like

The deprecated String Literals as Column Aliases feature is not supported in this version of SQL Server.

In addition, I have no way to install a new dnn portal, because it would be too difficult to configure 30 modules and pages.

So, I think my question is the best strategy to migrate an existing dnn port to windows azure?

+4
source share
1 answer

Migrating an existing site to Windows Azure is pretty straightforward (if a little tedious). If you are not working in webfarm, then only known problems exist at the database level. To simplify the migration, follow these steps:

  • DotNetNuke Update - The latest version of DotNetNuke is already compatible with SQL Azure. This will cover 90% of your problems.
  • Update modules - you must update all modules to the latest versions. Many modules are already compatible with Azure, and we continue to work with module providers to provide even greater updates. You can test a separate module for compatibility using our Extensibility Checker (EVS) service.
  • Use the Azure Migration Wizard to create a db script. At this point, you should not have many remaining SQL issues. Clearing scripts at this point should be fairly simple.
  • Install DotNetNuke - Use the DotNetNuke Azure Accelerator to install a clean version of DotNetNuke on Windows Azure. This will provide you with a wizard that guides you through Azure setup. NOTE If you go to Azure websites, use the DotNetNuke program from the gallery.
  • Database migration. Use the scripts in step 3 to overwrite the db created in step 4. You will also need to add a value in the PortalAlias ​​table for your specific Azure web URL.
  • File Transfer - Use RDP or FTP to move files from an existing DNN installation to an Azure installation. Remember to update Web.config with the new SQL Connection line (you can just copy the line from web.config created in step 4).
  • DNS update. After the site works correctly, you can update your DNS to indicate your domain on the new site.
+7
source

Source: https://habr.com/ru/post/1483363/

More articles:


All Articles