arterySignalIr/Ping - What is causing this error?

Asked

Viewed 91 times

2

The project MVC in C# here the company is with a very bizarre bug, to say the least. From time to time a random error bursts:

The controller for path ...arterySignalIr/Ping was not found or does not implement Icontroller, see image below:

The controller for path ...arterySignalIr/Ping was not found or does not implement IController.

Currently in the module I am working it keeps popping error randomly every more or less 3 minutes. The strange thing is that it doesn’t drop the session or break anything, it just keeps popping error.

My question is whether you know what mistake this is?

Is a DLL causing this? Which?

How to fix this?

c# asp.net-mvc visual-studio signalr
  • 1

    Dlls are contairners of codes, so in a certain way it is, and it’s not. This is of no importance. You need to know where in the code it’s causing this. Only with this information can not know. Have printed the stack trace of the exception. Things cannot happen so randomly. And the worst thing you can do and it seems you are doing is trying to hide the mistake. And if you weren’t doing this, it would be easier to identify what’s causing it.Today, the exception is the most poorly used resource in languages.It’s causing more harm than good.They release what they shouldn’t and capture what they can’t.

  • as soon as I pop the bug again I edit and send, I’m really lost in understanding this this mistake.....

  • 3

    No, this is programming by coincidence. You have to find out where you are generating the error now!. You have to use a scientific method. If it’s hard to find the mistake it’s because it’s more serious than it looks.

  • 1

    no one has been able to figure out what is causing the error, nor has the programmer with a million certifications found what is happening.

  • 1

    Have you at least tried to look at the stacktrace and see where the bug is popping? Already a start

  • I came to the stack overflow to see if anyone knew this problem exactly because of the difficulty of tracking the problem, but anyway, whatever. Felipe there has already solved my problem

  • I chose to reopen the question since it was possible to answer it objectively only with the information provided by its author.

Show 2 more comments

1 answer

6


This error only happens in Debug mode because of the feature Browser Linkfrom Visual Studio, you can choose the following options to solve your problem:

Disable the Browser Link: (Recommended if you do not make use of the resource) To do so simply add the following key in the appSettings block of your webconfig

<add key="vs:EnableBrowserLink" value="false" />

If you really care about the appeal but do not want to suffer with Missing controller exceptions, just ignore the routes of Browser Link editing your route settings as per the example below:

public static void RegisterRoutes(RouteCollection routes)
{
    routes.IgnoreRoute("{resource}.axd/{*pathInfo}");

#if DEBUG
    routes.IgnoreRoute("{*browserlink}", new { browserlink = @".*/arterySignalR/ping" });
    routes.IgnoreRoute("{*browserlink}", new { browserlink = @".*__browserLink.*" });
#endif

    //...Outras rotas
}

Note: as the ignore block is within a pragma debug this treatment will only occur when you are debugging which is exactly when the Browser Link feature is active.

  • Thanks for the help partner!

  • 1

    Nothing needing the community is there to help.

Browser other questions tagged c# asp.net-mvc visual-studio signalr

You are not signed in. Login or sign up in order to post.