FileUltimate is no longer working in the ASP.NET Development Server
Problem reported by Gary - April 9, 2018 at 12:25 AM
Resolved

5 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
Gary Replied
I Cem, I tried a similar things and couldn't get it to work, but in the process I ended up discovering IIS Express which solved the problem and is so much more compatible with IIS. Also UltiDev Web Server worked too, but IIS Express was integrated right into VS2010 so I am sticking with it as the winner.
0
Cem Alacayir Replied
Employee Post
So you say even latest version "Version 5.21.5 - April 7, 2018" did not work on VS2010 ASP.NET Development Server (out of the box, no additional code is required)?

Yes, IIS Express is better actually it's the only one used in VS versions after VS2010
0
Gary Replied
Yes that is correct, I tried both FileUltimate-v5.21.0.0 and FileUltimate-v5.21.5.0 and both are not working in VS2010 ASP.NET Development Server. The previous version that I was using FileUltimate-v5.20.5.0 does work.
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