Azure, AI, SP, .NET, Microsoft - Knowledge Base

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...

SharePoint migration is a continuous process in this business platform. Organization who are using SharePoint for a while need to start thinking at some day for migrating their data from lower version to upper version of SharePoint. Migration is one of the evitable project of most of the Organization. Migrating from On-Premises to On-Premises like MOSS 2007 to SP2020, or SP2010 to SP2013/2016/2019 is one path, and there is another path which is from SP2010/2013/2016/2019 to SPO (SharePoint Online). Content migration is the simple one rather than migrating content with custom application. Migration approach and the plan needs to be perfect for a successful migration. Considering SP2010 or SP2013 or SP2016 environment, there must be workflow presence and it could be integrated with document library, or list or might be site itself. These workflows might be SharePoint Designer Workflow, or Out-Of the-Box workflow or workflow created by any tool like Nintex.  Converting existing workfl...