ASP.NET MVC Legacy Route Hell
So I have a very old API that was originally written in MVC.
this api manages projects where each project has an ID + user-friendly slug, and then has a bunch of files that each have file name + file ID.
now I have an MVC route mapping that I will need to know how it resolves, so I can then extract those properties from the URL back to my own application.
this api manages projects where each project has an ID + user-friendly slug, and then has a bunch of files that each have file name + file ID.
now I have an MVC route mapping that I will need to know how it resolves, so I can then extract those properties from the URL back to my own application.
