Is it feasible to use Signalr.Net and Signal Core together?
up vote
0
down vote
favorite
Can a JS client (Angular JS 1.X) connect to, two different servers. First one is: Signalr.Net (old version) and second is: Signalr Core (.Net core version) simultaneously.
In other words, can both SignalR Js client libraries co-exist, in same
JS application.
On server side we have two different servers hosting both versions separately.
Are there any performance disadvantages?
c# angularjs .net-core signalr asp.net-core-signalr
add a comment |
up vote
0
down vote
favorite
Can a JS client (Angular JS 1.X) connect to, two different servers. First one is: Signalr.Net (old version) and second is: Signalr Core (.Net core version) simultaneously.
In other words, can both SignalR Js client libraries co-exist, in same
JS application.
On server side we have two different servers hosting both versions separately.
Are there any performance disadvantages?
c# angularjs .net-core signalr asp.net-core-signalr
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
Can a JS client (Angular JS 1.X) connect to, two different servers. First one is: Signalr.Net (old version) and second is: Signalr Core (.Net core version) simultaneously.
In other words, can both SignalR Js client libraries co-exist, in same
JS application.
On server side we have two different servers hosting both versions separately.
Are there any performance disadvantages?
c# angularjs .net-core signalr asp.net-core-signalr
Can a JS client (Angular JS 1.X) connect to, two different servers. First one is: Signalr.Net (old version) and second is: Signalr Core (.Net core version) simultaneously.
In other words, can both SignalR Js client libraries co-exist, in same
JS application.
On server side we have two different servers hosting both versions separately.
Are there any performance disadvantages?
c# angularjs .net-core signalr asp.net-core-signalr
c# angularjs .net-core signalr asp.net-core-signalr
edited Nov 11 at 6:58
asked Nov 10 at 5:59
Abhijeet
3,9731552110
3,9731552110
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
No you cannot use those together. Check my answer here for why and links to the documentation that state the same.
SignalR version compatability (StatusCode: 405 'Method Not Allowed')
You can't mix the .NET Core 1.x with the older client (1.x or 2.x). You will need to decide which is the best option for you but you need to implement the same compatible version across CLIENT and SERVER.
Check the link for more details but essentially:
What’s Changed?
We added a number of new features to SignalR for ASP.NET Core but we also decided to remove support for some of the existing features or change how they work. One of the consequences of this is that SignalR for ASP.NET Core is not compatible with previous versions of SignalR. This means that you cannot use the old server with the new clients or the old clients with the new server.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
No you cannot use those together. Check my answer here for why and links to the documentation that state the same.
SignalR version compatability (StatusCode: 405 'Method Not Allowed')
You can't mix the .NET Core 1.x with the older client (1.x or 2.x). You will need to decide which is the best option for you but you need to implement the same compatible version across CLIENT and SERVER.
Check the link for more details but essentially:
What’s Changed?
We added a number of new features to SignalR for ASP.NET Core but we also decided to remove support for some of the existing features or change how they work. One of the consequences of this is that SignalR for ASP.NET Core is not compatible with previous versions of SignalR. This means that you cannot use the old server with the new clients or the old clients with the new server.
add a comment |
up vote
1
down vote
accepted
No you cannot use those together. Check my answer here for why and links to the documentation that state the same.
SignalR version compatability (StatusCode: 405 'Method Not Allowed')
You can't mix the .NET Core 1.x with the older client (1.x or 2.x). You will need to decide which is the best option for you but you need to implement the same compatible version across CLIENT and SERVER.
Check the link for more details but essentially:
What’s Changed?
We added a number of new features to SignalR for ASP.NET Core but we also decided to remove support for some of the existing features or change how they work. One of the consequences of this is that SignalR for ASP.NET Core is not compatible with previous versions of SignalR. This means that you cannot use the old server with the new clients or the old clients with the new server.
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
No you cannot use those together. Check my answer here for why and links to the documentation that state the same.
SignalR version compatability (StatusCode: 405 'Method Not Allowed')
You can't mix the .NET Core 1.x with the older client (1.x or 2.x). You will need to decide which is the best option for you but you need to implement the same compatible version across CLIENT and SERVER.
Check the link for more details but essentially:
What’s Changed?
We added a number of new features to SignalR for ASP.NET Core but we also decided to remove support for some of the existing features or change how they work. One of the consequences of this is that SignalR for ASP.NET Core is not compatible with previous versions of SignalR. This means that you cannot use the old server with the new clients or the old clients with the new server.
No you cannot use those together. Check my answer here for why and links to the documentation that state the same.
SignalR version compatability (StatusCode: 405 'Method Not Allowed')
You can't mix the .NET Core 1.x with the older client (1.x or 2.x). You will need to decide which is the best option for you but you need to implement the same compatible version across CLIENT and SERVER.
Check the link for more details but essentially:
What’s Changed?
We added a number of new features to SignalR for ASP.NET Core but we also decided to remove support for some of the existing features or change how they work. One of the consequences of this is that SignalR for ASP.NET Core is not compatible with previous versions of SignalR. This means that you cannot use the old server with the new clients or the old clients with the new server.
edited Nov 13 at 9:40
Abhijeet
3,9731552110
3,9731552110
answered Nov 12 at 13:32
Frank M
36519
36519
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53236395%2fis-it-feasible-to-use-signalr-net-and-signal-core-together%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown