Swagger UI page does not show when using Swashbuckle.AspNetCore for .net core web api stateless service in Azure Service Fabric

OS: Windows 10 (Version 1703; OS Build 16281.1000) Visual Studio Version: 15.3.3 (VS 2017) Swashbuckle.AspNetCore Nuget Version: 1.0.0 Service Fabric Version: 5.7.198.9494 Service Fabric Version SDK: 2.7.198.9494

1. Create a service fabric application and choose ‘Stateless ASP.NET Core’ service template
2. Select ‘Web API’ ASP.NET Code 2.0.
3. This creates a service fab app project along with ‘Web1’ web api project.
4. Notice that Web1 project’s target environment is set to .net framework 4.7 (even though we selected asp.net core 2.0).
5. Run the app and a browser is launched with ‘localhost:port/api/values’ and the response ([“value1”, “value2”]) is shown. Good so far.
6. Next add a nuget package Swashbuckle.AspNetCore Nuget Version: 1.0.0
7. In ConfigureServices method of Startup.cs file, change the code to:

            services.AddMvc();
            services.AddSwaggerGen(options =>
            {
                options.SwaggerDoc("v1", new Info { Title = "My API", Version = "v1" });
            });

1. In Configure method of Startup.cs file, change the code to:

            if (env.IsDevelopment())
            {
                app.UseDeveloperExceptionPage();
            }

            app.UseMvc();
            app.UseSwagger();
            app.UseSwaggerUI(options =>
            {
                options.SwaggerEndpoint("/swagger/v1/swagger.json", "My API");
            });

1. Run the code. The endpoint (localhost:port/api/values) works as expected.
2. The endpoint (http://localhost:port/swagger/v1/swagger.json) works as expected.
3. The endpoint (http://localhost:port/swagger) causes 500 internal server error.
4. The endpoint (http://localhost:port/swagger/ui) causes 404 resource not found error.

[rudeGit]

I found that I needed to install nuget package Microsoft.AspNetCore.StaticFiles 2.0.0 (which will replace 1.0.0). Once I did that, the swagger page came up.

[iparimal]

I’ve fixed this using NSwag. I’ve removed “Swashbuckle.AspNetCore” and using “NSwag.AspNetCore” now. It works without any issue.