FileUltimate is no longer working in the ASP.NET Development Server
Problem reported by Gary - April 9 at 12:25 AM
Resolved
FileUltimate is no longer working in the ASP.NET Development Server included in Visual Studio 2010.
 
This happened on version 5.21.0.0 (the 5.20.5.0 version still works) and also not working on the latest 5.21.0.0
 
I think this is related to the routing changes. If I look in the Chrome console the following resource files are failing to load and give 404's when I browse to these urls..
 
 
 

2 Replies

Reply to Thread
0
Cem Alacayir Replied
Employee Post
Hi,
We released v5.21.5 two days ago with this fix:
 
  • Fixed: In some cases, ASP.NET’s UrlRoutingModule was still taking over the handlers (HTTP 404) after the new own routing was added in v5.21.0. This is now completely fixed. For reference, it was avoidable with v5.21.0 via adding the below line at the start of RegisterRoutes method in RouteConfig.cs (of MVC project):

    routes.IgnoreRoute("{resource}.ashx/{*pathInfo}")

    Now, this is not required anymore starting with this version.

Probably this should also fix your "ASP.NET Development Server included in Visual Studio 2010" issue.

Let me know.

0
Cem Alacayir Replied
Employee Post
FYI, this is now fixed in Version 3.15.6 - April 11, 2018:
 
  • Improved: Handler routing was not working (HTTP 404) in ASP.NET Development Server included in Visual Studio 2010 due to how it handled Request.PathInfo differently from IIS/IIS Express.

 
 

Reply to Thread