Hello,
Getting this error when deploying to Azure using App Service.
Application '/LM/W3SVC/518711467/ROOT' with physical root 'C:\home\site\wwwroot\' hit unexpected managed exception, exception code = '0xe0434352'. First 30KB characters of captured stdout and stderr logs:
Unhandled exception. System.Exception: Assembly with same name is already loaded
---> System.IO.FileLoadException: Assembly with same name is already loaded
at System.Runtime.Loader.AssemblyLoadContext.<LoadFromPath>g____PInvoke|5_0(IntPtr ptrNativeAssemblyBinder, UInt16* ilPath, UInt16* niPath, ObjectHandleOnStack retAssembly)
at System.Runtime.Loader.AssemblyLoadContext.LoadFromAssemblyPath(String assemblyPath)
at System.Reflection.Assembly.LoadFrom(String assemblyFile)
at Nop.Web.Framework.Infrastructure.Extensions.ApplicationPartManagerExtensions.AddApplicationParts(ApplicationPartManager applicationPartManager, String assemblyFile, Boolean useUnsafeLoadAssembly) in C:\Users\TravisMyvett\source\repos\nopCommerce_4.60.3\src\Presentation\Nop.Web.Framework\Infrastructure\Extensions\ApplicationPartManagerExtensions.cs:line 146
at Nop.Web.Framework.Infrastructure.Extensions.ApplicationPartManagerExtensions.PerformFileDeploy(ApplicationPartManager applicationPartManager, String assemblyFile, PluginConfig pluginConfig, INopFileProvider fileProvider) in C:\Users\TravisMyvett\source\repos\nopCommerce_4.60.3\src\Presentation\Nop.Web.Framework\Infrastructure\Extensions\ApplicationPartManagerExtensions.cs:line 175
at Nop.Web.Framework.Infrastructure.Extensions.ApplicationPartManagerExtensions.InitializePlugins(ApplicationPartManager applicationPartManager, PluginConfig pluginConfig) in C:\Users\TravisMyvett\source\repos\nopCommerce_4.60.3\src\Presentation\Nop.Web.Framework\Infrastructure\Extensions\ApplicationPartManagerExtensions.cs:line 284
--- End of inner exception stack trace ---
at Nop.Web.Framework.Infrastructure.Extensions.ApplicationPartManagerExtensions.InitializePlugins(ApplicationPartManager applicationPartManager, PluginConfig pluginConfig) in C:\Users\TravisMyvett\source\repos\nopCommerce_4.60.3\src\Presentation\Nop.Web.Framework\Infrastructure\Extensions\ApplicationPartManagerExtensions.cs:line 329
at Nop.Web.Framework.Infrastructure.Extensions.ServiceCollectionExtensions.ConfigureApplicationServices(IServiceCollection services, WebApplicationBuilder builder) in C:\Users\TravisMyvett\source\repos\nopCommerce_4.60.3\src\Presentation\Nop.Web.Framework\Infrastructure\Extensions\ServiceCollectionExtensions.cs:line 96
at Program.<Main>$(String[] args) in C:\Users\TravisMyvett\source\repos\nopCommerce_4.60.3\src\Presentation\Nop.Web\Program.cs:line 38
Process Id: 8948.
File Version: 17.0.23170.8. Description: IIS ASP.NET Core Module V2 Request Handler. Commit: 3c37ef8f5358abb303c05d299f029fca7d867d56
Everything was working fine until I added a dependency to a custom plugin we developed in house.
The dependency is the official Nop Web Api Backend.
https://ibb.co/smg8JLP