Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

253
Views
Is there a defined strategy for versioning SignalR hubs, so that old JS code can continue to work?

I want to be able to make changes to the method signatures, names, etc on existing SignalR hubs. Is there a defined strategy for versioning SignalR hubs, so that old JS code can continue to work, without having to create a fresh newly named hub for the new calls?

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

I'd say the short answer is no. Signalr does not have any versioning strategy like that.

The question is a little light on details, but signalr has for instance the option to use an attribute on a class to define the hubname. You could also create a new hub class by deriving from the original Hub in order to help you reuse existing code. Whatever you do new clientside js will need to be written.

over 4 years ago · Santiago Trujillo Report

0

You can't change the method name and expect Javascript to understand that you changed its name. As for method signatures, Javascript is not a strongly typed programming language, so you can pass different types of variables to the hub (as long as the number of variables stays the same).

However, you can create new methods, if you want to continue to support the old ones.

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!