Issues upgrading from 4.6.1. to 4.7.1 with a dependency on System.Web.Http RRS feed

  • Question

  • I previously asked this question on stackoverflow and tweeted it at the ASP.NET team.  I have yet to hear anything, so I am following up here to see if I can get details.  https://stackoverflow.com/questions/47799050/issues-upgrading-from-4-6-1-to-4-7-1-with-a-dependency-on-system-web-http

    I have a class that implements System.Web.Http.Dispatcher.IHttpControllerActivator (from System.Web.Http in the Microsoft.AspNet.WebApi.Core package). When I upgrade from the .Net framework version 4.6.1 to 4.7.1, the following a runtime exception is thrown:

    Method 'Create' in type 'MyType' from assembly 'MyAssembly, Version=, Culture=neutral, PublicKeyToken=null' does not have an implementation.

    In addition, some of my tests assert System.Web.Http.HttpResponseException are thrown. This class has a property called Response with a type of System.Net.Http.HttpResponseMessage. These are now throwing the following at runtime:

    System.MissingMethodException: Method not found: 'System.Net.Http.HttpRequestMessage System.Web.Http.ApiController.get_Request()'.

    Assuming this was a change in System.Net.Http between 4.6.1 and 4.7.1, is there a path to upgrade to 4.7.1 while relying on System.Web.Http?

    Tuesday, February 27, 2018 6:54 PM

All replies

  • Hi jbourdon2,

    Thank you for posting here.

    For your question is more related to ASP.NET, you could post a new thread in ASP.NET forum for suitable support.

    The CLR Forum discuss and ask questions about .NET Framework Base Classes (BCL) such as Collections, I/O, Regigistry, Globalization, Reflection. Also discuss all the other Microsoft libraries that are built on or extend the .NET Framework, including Managed Extensibility Framework (MEF), Charting Controls, CardSpace, Windows Identity Foundation (WIF), Point of Sale (POS), Transactions. 

    Best Regards,


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Wednesday, February 28, 2018 6:23 AM