##[error]Error: The process 'E:_Agents\WIN_work_tool\dotnet\dotnet.exe' failed with exit code 1
##[warning].NET 5 has some compatibility issues with older Nuget versions(<=5.7), so if you are using an older Nuget version(and not dotnet cli) to restore, then the dotnet cli commands (e.g. dotnet build) which rely on such restored packages might fail. To mitigate such error, you can either: (1) - Use dotnet cli to restore, (2) - Use Nuget version 5.8 to restore, (3) - Use global.json using an older sdk version(<=3) to build
Info: Azure Pipelines hosted agents have been updated and now contain .Net 5.x SDK/Runtime along with the older .Net Core version which are currently lts. Unless you have locked down a SDK version for your project(s), 5.x SDK might be picked up which might have breaking behavior as compared to previous versions. You can learn more about the breaking changes here: https://docs.microsoft.com/en-us/dotnet/core/tools/ and https://docs.microsoft.com/en-us/dotnet/core/compatibility/ . To learn about more such changes and troubleshoot, refer here: https://docs.microsoft.com/en-us/azure/devops/pipelines/tasks/build/dotnet-core-cli?view=azure-devops#troubleshooting
##[error]Dotnet command failed with non-zero exit code on the following projects : E:_Agents\WIN_work\52\s\aspnet-core\src\TestAppName.HttpApi.Host\TestAppName.HttpApi.Host.csproj
To resolve this error in our Build/Publish process in Azure DevOps we added this line to the TestAppName.HttpApi.Host.csproj PropertyGroup: <ErrorOnDuplicatePublishOutputFiles>false</ErrorOnDuplicatePublishOutputFiles>
We found this solution in Microsoft documentation, here: https://docs.microsoft.com/en-us/dotnet/core/compatibility/sdk/6.0/duplicate-files-in-output, because we found out that that TestAppName.HttpApi.Host project was depending on the Volo.Abp.AspNetCore.Mvc.UI.ThemeLepton project, and they had conflicts with the two project's project.json files.
What we are trying to accomplish is quickly build out multi-tenant applications that support UI modifications including changing color schemes, layouts, login screens, and more using ABP.IO and Angular. Is the above process correct, or is there a better way to go about doing this? Or, is there a limitation on what Angular UI can modify in ABP.IO?
We have also tried to use the command line tools for ABP to add in the modules to the angular project, but that did not give us the customization abilities we fully needed, and that is why we started using the ABP Suite.