CODEWITHSUNDEEP
c#asp.net-mvcsignalr
James
James

Reputation: 35

Using SignalR to communicate between Server(asp mvc framework 4.5) and client (console app with framework 3.5))

I have an ASP MVC application that runs in 4.5 framework this application should communicate in real time with an other console application that using 4.5 framework also for this reason I use SignalR in the server(mvc application) I installed Microsoft.AspNet.SignalR" version 2.1.2 In the client (Console App ) I installed Microsoft.AspNet.SignalR.Client version="2.2.1" this runs well But problems start when My Customer required that the console application should run in .Net Framework 3.5 not in 4.5

when I tried to migrate console application to 3.5 framework , the communcation between server and client does not work

I have create a new console app with 3.5 framework and I use "Nivot.SignalR.Client.Net35" version="2.0.0" and Microsoft.AspNet.SignalR -Version 1.2.2 in server but I have this Message=You are using a version of the client that isn't compatible with the server. Client version 1.3, server version 1.2. Source=Nivot.SignalR.Client.Net35 when I Use Package Microsoft.AspNet.SignalR -Version 2.0.1 in server I have this message :An unhandled exception of type 'System.AggregateException' occurred in System.Threading.dll More information: TaskExceptionHolder_UnhandledException

How to resolve this problems? Is there an example that use signalR with my configuration?

Upvotes: 1

Views: 743

Answers (1)

Pawel
Pawel

Reputation: 31620

SignalR requires at least .NET Framework 4. It relies heavily on async/await and Tasks which are not supported on .NET Framework 3.5. It should be possible to write a SignalR client for .NET Framework 3.5 but it is quite a task (especially that you would have to manage threads on your own).

Upvotes: 1

Related Questions