配置ASP.NET Core应用程序的正确顺序是什么？

Question

I've got an ASP.NET Core application with several Web Api controllers. I can't tell if there is some connection, but the application was created with VS2015 update 2, and now I'm working with VS2015 update 3. So I created another Web Api controller, and when there is a query to that controller I'm having this exception:

System.NotSupportedException: The given path's format is not supported.
   at System.Security.Permissions.FileIOPermission.QuickDemand(FileIOPermissionAccess access, String fullPath, Boolean checkForDuplicates, Boolean needFullPath)
   at System.IO.Path.GetFullPath(String path)
   at Microsoft.AspNet.FileProviders.PhysicalFileProvider.GetFullPath(String path)
   at Microsoft.AspNet.FileProviders.PhysicalFileProvider.GetFileInfo(String subpath)
   at Microsoft.AspNet.StaticFiles.StaticFileContext.LookupFileInfo()
   at Microsoft.AspNet.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNet.Cors.Infrastructure.CorsMiddleware.<Invoke>d__7.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNet.Diagnostics.Entity.MigrationsEndPointMiddleware.<Invoke>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNet.Diagnostics.Entity.DatabaseErrorPageMiddleware.<Invoke>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNet.Diagnostics.Entity.DatabaseErrorPageMiddleware.<Invoke>d__6.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNet.Diagnostics.DeveloperExceptionPageMiddleware.<Invoke>d__7.MoveNext()

The funny thing is that somehow StaticFileMiddleware is involved in processing a simple request to controller. While I can fix the problem by changing the order of configuring the application by calling

app.UseMvc(...

before

app.UseStaticFiles()

I still want to know how this happened and what's the correct order of configuring the application.

Keep in mind that all previously added controllers are working just fine with both ways of configuring, but the new one can work only with the latter.

The new controller do not operate with static files.

EDITED Routing: In controller:

[Route("api/[controller]")]
    public class ViewsController : Controller
    {
        [HttpGet("{path}", Name = "Views")]
        public async Task<IActionResult> Get(string path)
        {
            return Json("bla");
        }
    }

In Startup.cs:

app.UseMvc(routes =>
        {
            routes.MapRoute(
                name: "angular2app",
                template: "ng/{*.}",
                defaults: new { controller = "Home", action = "Index" });

            routes.MapRoute(
                name: "api",
                template: "api/{controller}/{action}/{id?}");

            routes.MapRoute(
                name: "default",
                template: "{controller=Home}/{action=Index}/{id?}");
        });

The troubled request:

http://localhost:5000/api/Views/blablapath

Answer 1

If you use Core2 preview mixed with release nugets, you have to add the static file nuget to your project. (Core2 already include it but you still have to add it to solve some issues)

Microsoft.AspNetCore.StaticFiles