将我的ASP.NET 5 API升级到1.0.0-rc1-update1后,我得到如下所示的异常 .

启动运行得很好 . 当我尝试调用API时会记录异常 .

Startup:

我已经删除了 Startup 到了必需品,但问题仍然存在 .

public class Startup
{
    public IConfiguration Configuration { get; private set; }

    public void ConfigureServices(IServiceCollection services)
    {
        services.AddMvc();
    }

    public void Configure(IApplicationBuilder app)
    {
        app.UseMvc();
    }
}

project.json

{
    ...
    "dependencies": {
      "Microsoft.AspNet.IISPlatformHandler": "1.0.0-rc1-final",
      "Microsoft.AspNet.Server.Kestrel": "1.0.0-rc1-final",
      "Microsoft.Extensions.Configuration": "1.0.0-rc1-final",
      "Microsoft.Extensions.Configuration.Json": "1.0.0-rc1-final",
      "Newtonsoft.Json": "6.0.6",
      "Microsoft.Net.Http": "2.2.22",
      "Microsoft.ApplicationInsights.AspNet": "1.0.0-rc1",
      "Microsoft.Extensions.Logging": "1.0.0-rc1-final",
      "Microsoft.Extensions.Logging.Abstractions": "1.0.0-rc1-final",
      "WindowsAzure.Storage": "5.0.2",
      "Microsoft.AspNet.Authorization": "1.0.0-rc1-final",
      "Microsoft.AspNet.Mvc.Core": "6.0.0-rc1-final",
      "Microsoft.AspNet.Mvc.Abstractions": "6.0.0-rc1-final",
      "Microsoft.AspNet.Authentication.JwtBearer": "1.0.0-rc1-final",
      "Microsoft.AspNet.StaticFiles": "1.0.0-rc1-final"
    },
    "commands": {
        "web": "Microsoft.AspNet.Server.Kestrel"
    }
    "frameworks": {
        "dnx451": {
            "frameworkAssemblies": {
            }
        }
    },
}

Exception thrown in Microsoft.AspNet.Server.Kestrel:

应用程序抛出了未处理的异常 . System.NullReferenceException:未将对象引用设置为对象的实例 . 在Microsoft.AspNet.Mvc.ModelBinding.CompositeModelBinder.d__5.MoveNext()---从抛出异常的先前位置的堆栈跟踪结束---在System的System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务) . Microsoft.AspNet.Mvc.Controllers.DefaultControllerActionArgumentBinder.d__6.MoveNext()中的Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)---抛出异常的前一个位置的堆栈跟踪结束---在System.Runtime.CompilerServices上Microsoft.AspNet.Mvc.Controllers.DefaultControllerActionArgumentBinder.d__9.MoveNext()中的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)中的.TaskAwaiter.ThrowForNonSuccess(任务任务)---来自先前位置的堆栈跟踪结束在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(T)的System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)中抛出了---在Microsoft.AspNet.Mvc.Controllers.DefaultControllerActionArgumentBinder.d__5.MoveNext()---从抛出异常的先前位置的堆栈跟踪结束---在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)在Microsoft.AspNet.Mvc.Controllers.FilterActionInvoker.d__52.MoveNext()中的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)---从抛出异常的上一个位置的堆栈跟踪结束---在System . System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)中的Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务),位于Microsoft.AspNet.Mvc.Controllers.FilterActionInvoker.d__51.MoveNext()---来自之前的堆栈跟踪结束抛出异常的位置---在Microsoft.AspNet.Mvc.Controllers.FilterActionInvoker.d__44.MoveNext()---从抛出异常的上一个位置的堆栈跟踪结束---在System.Runtime.Compi位于Microsoft.AspNet.Mvc.Infrastructure.MvcRouteHandler.d__6.MoveNext()的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)中的lerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)---来自先前位置的堆栈跟踪结束异常被抛出---在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处于System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务),位于Microsoft.AspNet.Mvc.Routing.InnerAttributeRoute.d__10.MoveNext() ---在抛出异常的前一个位置的堆栈跟踪结束---在Microsoft.AspNet的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)的System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)中 . Routing.RouteCollection.d__9.MoveNext()---从抛出异常的上一个位置开始的堆栈跟踪结束---在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(T)在Microsoft.AspNet.Builder.RouterMiddleware.d__4.MoveNext()的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)上询问任务---从抛出异常的上一个位置的堆栈跟踪结束---在系统Microsoft.AspNet.Cors.Infrastructure.CorsMiddleware.d__7.MoveNext()中的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)中的.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)---来自堆栈跟踪的结束抛出异常的上一个位置---在Microsoft.ApplicationInsights.AspNet.RequestTrackingMiddleware.d__4.MoveNext的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)的System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)处 . )---从抛出异常的先前位置开始的堆栈跟踪结束--- atSystem.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)在Microsoft.AspNet.IISPlatformHandler.IISPlatformHandlerMiddleware.d__8.MoveNext()---来自之前的堆栈跟踪结束位置,其中的例外是在Microsoft.AspNet.Hosting.Internal.RequestServicesContainerMiddleware.d__3.MoveNext抛出---在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(工作任务)在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务task) ()---从抛出异常的先前位置开始的堆栈跟踪结束---在Microsoft的System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务任务)的System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(任务任务)中 . AspNet.Hosting.Internal.HostingEngine . <> c__DisplayClass32_0 . <b__0> d.MoveNext()---来自之前位置的堆栈跟踪结束n为在Microsoft.AspNet.Server.Kestrel.Http.Frame.d__79.MoveNext抛出---在System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(工作任务)在System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(任务task) ()