【问题标题】:ASP.NET Core WebAPI crashes because I don't have StaticFileMiddleware?ASP.NET Core WebAPI 崩溃是因为我没有 StaticFileMiddleware?
【发布时间】:2020-04-22 17:27:12
【问题描述】:

我正在尝试构建一个简单的 WebAPI,将 JSON 数据提供给 Web 应用程序,但由于某种原因,每次调用都以找不到任何内容而结束,而是崩溃。

我有一个带有路由的控制器:

[Produces("application/json")]
[Route("api/Players")]
public class PlayersController : Controller
{
    [HttpGet("{name}", Name = "GetPlayer")]
    public Player Get(string name)
    {
        return playerService.GetPlayer(name);
    }

playerservice 方法只返回一个 dto。不幸的是,这个端点甚至没有被调用。
请求管道被调用,然后与System.MissingMethodException: 'Method not found: 'Void Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware..ctor 崩溃,尽管我什至没有尝试获取任何静态文件,只是/api/players/dummy/swagger,没有工作。这里的调用栈就是 Program.Main 然后是外部代码。

ConfigureServices 去

services.AddMvcCore().AddApiExplorer();
services.AddSwaggerGen(c => c.SwaggerDoc("v1", new Info { Title = "API", Version = "v1" }));

services.AddControllers();

配置去

app.UseSwagger()
    .UseSwaggerUI(c => c.SwaggerEndpoint("/swagger/v1/swagger.json", "API v1"))
    .UseRouting()
    .UseEndpoints(endpoints => endpoints.MapControllers());

我的管道是否配置不正确?尽管我什至不提供静态文件,但我是否需要一些静态文件中间件?我做错了什么?

编辑:异常截图:

这是异常的堆栈跟踪,似乎它发生在大摇大摆的情况下:

at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.CreateStaticFileMiddleware(RequestDelegate next, IHostingEnvironment hostingEnv, ILoggerFactory loggerFactory, SwaggerUIOptions options)
   at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware..ctor(RequestDelegate next, IHostingEnvironment hostingEnv, ILoggerFactory loggerFactory, SwaggerUIOptions options)
   at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor, Boolean wrapExceptions)
   at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
   at Microsoft.Extensions.Internal.ActivatorUtilities.ConstructorMatcher.CreateInstance(IServiceProvider provider)
   at Microsoft.Extensions.Internal.ActivatorUtilities.CreateInstance(IServiceProvider provider, Type instanceType, Object[] parameters)
   at Microsoft.AspNetCore.Builder.UseMiddlewareExtensions.<>c__DisplayClass4_0.<UseMiddleware>b__0(RequestDelegate next)
   at Microsoft.AspNetCore.Builder.ApplicationBuilder.Build()
   at Microsoft.AspNetCore.Hosting.WebHost.BuildApplication()
   at Microsoft.AspNetCore.Hosting.WebHost.<StartAsync>d__27.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.<RunAsync>d__5.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.<RunAsync>d__5.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.<RunAsync>d__4.MoveNext()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Hosting.WebHostExtensions.Run(IWebHost host)
   at Teambuilder_WebAPI.Program.Main(String[] args) in D:\Sources\Teambuilder\Teambuilder WebAPI\Program.cs:line 11

【问题讨论】:

标签: c# asp.net-core asp.net-web-api routing


【解决方案1】:

Swashbuckle.AspNetCore 软件包的第 5 版处于预发布阶段,预计会出现问题。

正如 OP 所确认的,this github issue 与此问题有关,因此解决方案将更新到最新版本。

更新:正如 OP 确认的那样,您可以在 .Net Core v3.1 中使用最新的稳定版 Swashbuckle v4.0.1,一切顺利。

【讨论】:

  • 这解决了问题,因为我从 coreFx 2.2 更新到 3.1,但将 Swashbuckle 保留在 4.0.1 上,因为这是其最新的稳定版本。
  • @Squirrelkiller 感谢您提供信息并帮助其他开发人员,我刚刚更新了答案以添加此信息。
猜你喜欢
  • 2022-01-02
  • 1970-01-01
  • 1970-01-01
  • 2017-04-04
  • 2021-07-24
  • 2010-12-02
  • 1970-01-01
  • 2017-04-15
  • 2011-05-28
相关资源
最近更新 更多