Activities of "arskapalli"

We were able to resolve the issue by making changes to our CI/CD pipeline to use global.json for the .NET SDK version in both the build and release pipelines and restarting the web job several times.

Thank you for your assistance in troubleshooting, as ruling out issues with the code and release configuration helped us focus on the real issue at hand.

Yes, I was able to publish the application to a local folder (bin/Release/net7.0/publish) and run it from there with no problem. I suppose this points to the issue most likely being in our Azure app service configuration or our Azure DevOps pipeline.

Hello,

I changed the environment variables from Development to Production, but the issue still doesn't occur locally.

The issue started presenting in the production environment shortly after we updated from ABP Framework 5.1.4 to 7.1.1.

I've been pursuing the possibility that the Microsoft.Extensions.FileProviders.Embedded file can't be found due to a possible version mismatch after the build, but the AssemblyVersion does appear to be 7.0.0.0 as required by Volo.Abp.VirtualFileSystem:

[assembly: AssemblyFileVersion("7.0.423.11903")]
[assembly: AssemblyInformationalVersion("7.0.4+e56abc45c4f8adc518abfc11a59849d616431e2c")]
[assembly: AssemblyProduct("Microsoft ASP.NET Core")]
[assembly: AssemblyTitle("Microsoft.Extensions.FileProviders.Embedded")]
[assembly: AssemblyMetadata("RepositoryUrl", "https://github.com/dotnet/aspnetcore")]
[assembly: NeutralResourcesLanguage("en-US")]
[assembly: AssemblyVersion("7.0.0.0")]