Does SignalR support .NET 4.0. Or is it support only from .NET 4.5 upwards. Is there any link which provides with minimum requirements for SignalR.
This is not the case any more, and the 2.x releases require .NET 4.5.
https://github.com/SignalR/SignalR/issues/1723
The last .NET 4.0 support for SignalR is version 1.2.2. Version 2 only works with .NET 4.5
Open the NuGet Package Manager Console and type:
Install-Package Microsoft.AspNet.SignalR.Client -Version 1.2.2
Install-Package Microsoft.AspNet.SignalR -Version 1.2.2
This will install the SignalR (Client and Server) in your selected project (web project) automatically.
Yes .NET 4.0 supports SignalR. The minimum requirements:
*Visual Studio 2010 SP1
*Since template installer is not available in VS2010 you need to install SignalR NuGet package
One thing to watch here is client/server .Net versions.
Most people know (but it's worth repeating) signalR can be hosted on Windows 2008R2 upwards. Windows 2008R2 has IIS7 and thus when hosted on IIS7 signalR cannot use WebSockets (as the old Windows http stack has no support for WebSockets). So that's ServerSentEvents or LongPolling. Not great for performance.
Windows 2012 upwards (and thus at least IIS8) offers support for WebSockets, which gets the amaziong C10K perf we're all after.
Now the interesting bit.
.NET clients.
If you only care about the browser skip this bit.
Any .Net clients that connect to a signalR back-end MUST use
Windows8 upwards to use WebSockets The Microsoft networking stack (for
.Net) in Windows7 does not contain WebSockets.
So don't use signalR with WebSockets if your client is Windows7.
OR... like us you'll need to use a custom WebSocket stack coupled with WebClient to handle the http handshake.
Hopefully this will help someone else!
You can download entire web stack from codeplex and SignalR from github and compile it under .net4.0
There is one sample project at http://www.bluelemoncode.com/2013/02/default.aspx
It is good SignalR sample and working vs 2010 sp1 and .net framework 4.0. working properly.
http://www.bluelemoncode.com/file.axd?file=2013%2f3%2fSignalR_OneOneChat.zip
The minimum requirements for SignalR is described here,
Which means your client can be WinForm/WPF application running on Windows XP.
Related
This is a very hard question to Google because there are different versions of ASP.NET out there. What I want to know is the versions of Windows Server that support ASP.NET 2.0 (no MVC, no CORE) just the original version that was released back in 2006 (See: https://en.wikipedia.org/wiki/.NET_Framework_version_history#.NET_Framework_2.0)
Thanks!
First, only Windows Server 2012 and above are supported now.
Second, you have to manually enable ASP.NET 3.5 there, which supports ASP.NET 2.0 web apps,
https://learn.microsoft.com/en-us/iis/get-started/whats-new-in-iis-8/iis-80-using-aspnet-35-and-aspnet-45
However, keep in mind that such ASP.NET 2.0 apps are ancient. Upgrade if you can.
The .NET (Standard) framework receives automatic updates via the Windows Update service. Does .NET Core Runtime have the same/similar functionality? If I install a .NET Core Runtime and .NET Core application on a server should I be the one taking care to apply the latest minor patch?
My question is primarily focused on potential security issues which are then remedied by subsequent minor version update.
On Windows, the currently supported versions of .NET 5, .NET Core 3.x and .NET Core 2.x can now receive automatic updates. See the .NET Blog post announcing this for more information.
It is in an opt-in service, so on a client OS you would need to enable Receive updates for other Microsoft products when you update Windows.
On server OS the updates are managed via Windows Server Update Services (WSUS) or System Center Configuration Manager (SCCM). See the section for IT administrators on the MS blog for detailed instructions.
I start working on new Web App and still doing the research about the framework to pick. One of the requirements: the app will be deployed to IIS on Windows Server 2008 that has SSL3 certificate. Also the app will be deployed to newer Windows Server with TLS certificate. So the issue I'm facing is similar to this question.
Will .Net Core ASP.Net MVC support both SSL3 and TLS* or Should I go with standard .Net Framework?
If not, What version of .Net Framework to pick?
I could be wrong here, but SSL3 is very old and has succeeded by replaced by TLS 1.2.
If the server is running Windows Server 2008 R2 SP1 (release 2, service pack 1) or greater then I would recommending going with .NET Core.
However, if the server is Windows Server 2008 without R2 then you will need to use an older version of the .NET Framework say 4.6.1.
Before jumping in you should sit down with the decision makers point out that developing a solution on legacy infrastructure holds serious security and business risks.
I consider to use ASP.NET for developing a real-time appication that will be shown on a browser (IE, FF, Chrome etc.).
I'm wondering what are the system requirements for the server side where the application will be deployed?
Do I have to use IIS or I'm free to choose any web server I want? If IIS only - does it part of any Windows installation (so users do not have to pay extra charge for that?)
Do I have to install .NET Framework?
anything else?
Thank you!
You don't have to use IIS, you could use Apache, nginx, or xsp, but doing so means you have to use mono which is an open source version of the .NET framework, it's a couple of versions behind the real thing, you can find out more info here: http://www.mono-project.com/ASP.NET
If you choose to use Windows/IIS, then IIS is a feature of Windows that can be installed free of charge. You will need to install the .NET framework in order to host an ASP.NET web application, like IIS, the .NET framework and ASP.NET are features of Windows Server 2008 and above that can be installed/uninstalled whenever you like, for free.
Does Server Core 2008 support asp.net? I see references online saying that it isn't supported, but they are all old references from CTPs.
Server Core 2008 does not support ASP.NET. However, Windows 2008 R2 Server Core supports .NET up to 3.5 out of the box, and since 2011-02-21 it can also run .NET 4.0 apps. To enable .NET 4.0 support, you need to install Service Pack 1 and the .NET 4.0 Standalone Installer for Server Core.
No.
Answer here:
http://www.microsoft.com/windowsserver2008/en/us/compare-core-installation.aspx
"ASP.NET is not available with Server Core installation option in any edition"
The short answer, as others have said: no.
The longer answer: IIS is there, classic ASP is there, and other server-side languages such as PHP will work, too. What's missing is .NET Framework, and adding it to Server Core is in the works.
Currenly the .NET Framework is not on Server Core, which means ASP.NET is currently not available. This is something the .NET team wants to add and we're working on adding it as soon as possible.
No
With the new Server Core 2008 R2 you can run asp.net in IIS, but only up to version 3.5. 4.0 is not supported since you cant install .Net 4.0 on Server Core 2008 R2 at all.