.NET Legacy App migration to Azure Cloud

Migrating from.NET legacy application from on-premise to Cloud environment is not a very easy going task every time. Complexity depends upon from which version to which version it is getting migrated.


Generally the migration executed in four phases - Reviewing, Planning, Migration, and Testing. Below are the five migration oriented links you can visit before you get your hands dirty.


Get free compatibility report - https://azure.microsoft.com/en-us/products/app-service/migration-tools/?WT.mc_id=dotnet-35129-website

Review wiki for migrating to App Service - https://github.com/Azure/App-Service-Migration-Assistant/wiki

Readiness Checkpoint - https://github.com/Azure/App-Service-Migration-Assistant/wiki/Readiness-Checks

Migration guide, .NET upgrade assistant - https://learn.microsoft.com/en-us/dotnet/core/porting/upgrade-assistant-overview

.NET portability Analyzer - https://learn.microsoft.com/en-us/dotnet/standard/analyzers/portability-analyzer


And the final note here is must review Scott Hunter YouTube Video - https://www.youtube.com/watch?v=NBbI52liUR4&list=PLdo4fOcmZ0oVlqu_V8EXUDDnPsYwemxjn&t=504s


Let's tag this as 4th July special!

Comments

Post a Comment

Popular posts from this blog

How to fix Azure DevOps error MSB4126

Image
Setting up build and release pipeline always tedious and we face many build related issues. Here is one common error I face couple of times while setting app Web or windows apps in Azure DevOps After placing the code in repos, and creating the build pipeline and run it, you can face the following error ##[error]D:\a\8\s\<your solution file>.sln.metaproj(0,0): Error MSB4126: The specified solution configuration "release|$(BuildPlatform)" is invalid. Please specify a valid solution configuration using the Configuration and Platform properties (e.g. MSBuild.exe Solution.sln /p:Configuration=Debug /p:Platform="Any CPU") or leave those properties blank to use the default solution configuration. To understand what is target platform defined in your project you need to visit or open the solution(.sln) file and review the following sections. In my case, this has been defined as x86 as target platform.                   GlobalSecti
Read more

How to create Custom Visuals in Power BI – Initial few Steps

Image
This post will help you to know the steps to create custom visuals in PowerBI. Microsoft defined them as well at https://docs.microsoft.com/en-us/power-bi/service-custom-visuals-getting-started-with-developer-tools . First things first, and you need to download and install NodeJS , in case if you do not have npm setup in your machine.  Second step is to run couple of npm commands to install Power BI Visual Tools and create & publish the cert. Finally, create your own package and upload with the help of npm. 1.       npm install -g powerbi-visuals-tools 2.       pbiviz --create-cert pbiviz --install-cert 3.       pbiviz new My Visual name – This will create the file under the name of your visual file. 4.      pbiviz start – You need to go to the folder where your custom visual  resides, and run this command. You can change a few things in your pbiviz.json file, like author, display name, icon, style etc. Finally, package your
Read more

How to fix Azure DevOps Error CS0579

Image
During build process of one ASP.NET web application in Azure DevOps environment, I face the error  CS0579 multiple times. Everything looks great to me, but continuous crappy error keep saying issues in AssemblyInfo.cs file. Below are few red error I have face during setup this project. "SharePointServicesWebApp\Properties\AssemblyInfo.cs(8,12): Error CS0579: Duplicate 'AssemblyTitle' attribute" ##[error]SharePointServicesWebApp\Properties\AssemblyInfo.cs(9,12): Error CS0579: Duplicate 'AssemblyDescription' attribute ##[error]SharePointServicesWebApp\Properties\AssemblyInfo.cs(10,12): Error CS0579: Duplicate 'AssemblyConfiguration' attribute ##[error]SharePointServicesWebApp\Properties\AssemblyInfo.cs(11,12): Error CS0579: Duplicate 'AssemblyCompany' attribute I was quite sure there is something coming up during build process and make this as duplicate. Because this build process also provides assembly information other way rou
Read more