Forum Discussion

joseparra's avatar
joseparra
Brass Contributor
May 06, 2022
Solved

How to use Microsoft.Web.Services2 in Azure App Service??

Hi,

I'm migrating a .Net web service from IIS on-premises to Azure app service.

When I load it in the browser it shows me the following error:

Server Error in '/' Application.


Configuration Error

Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: Could not load file or assembly 'Microsoft.Web.Services2, Version=2.0.2.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

 

Is the "Microsoft.Web.service2" supported by Azure App Services? I have been searching in assembly folder of the "app service host" and it is not included. How can I reference and use it in a \bin\ folder in the app folder?

Thank you in advance.

Jose

  • Hi DavidTex
    I finally was a problem of the version of the assembly. It was very estrange, because in the local server it was working without any change.
    I solved it specifying the version 2.0.3.0 instead of 2.0.2.0.

2 Replies

  • DavidTex's avatar
    DavidTex
    Copper Contributor

    Hi joseparra 

    Did you used Azure App Service migration assistant?

    Did you went to the application settings, web.confit, etc. and cleaned it up?
    https://docs.microsoft.com/en-us/azure/app-service/configure-common?tabs=portal

    Might go check as well: https://docs.microsoft.com/en-us/archive/blogs/asiatech/how-to-resolve-the-could-not-load-file-or-assembly-issues-on-windows-azure-web-sites

    Hope it helped.



    • joseparra's avatar
      joseparra
      Brass Contributor
      Hi DavidTex
      I finally was a problem of the version of the assembly. It was very estrange, because in the local server it was working without any change.
      I solved it specifying the version 2.0.3.0 instead of 2.0.2.0.

Resources