I wonder can I host SignalR application in IIS without OWIN. If not what is the reason? Cant't IIS fit SignalR hosting recommendations? Why when I install Microsoft.AspNet.SignalR package to Web Application project, Microsoft.Owin packages automatically install?
No, you can't use SignalR 2.x without OWIN. OWIN abstracts the host/server and prevents from leaking server specific concepts into SignalR code. This allows using SignalR in IIS but also self host it in a command line app.
Related
I get 404 error when I host .Net Core 5 Web API on IIS.
I can host Web Application with no issues, though.
Any idea why?
What kind of web application runs successfully? Make sure all of the required modules is installed. IIS 7 is pretty old version, make sure all of the required steps are performed.
Microsoft's guide on hosting on IIS
Thank you all for answering/commenting on my question.
I realized that I was using wrong url for testing my api endpoints. So, hosted the web api as a website in IIS, and it worked successfully.
Im a beginner in microsoft architecture.
For a project I am asked to host a net core web application on an IIS server by removing the use of the kestrel server (http.sys too).
The net core application must only run via IIS.
But according to my research via Microsoft documentation, blogs and forums. It seems to me that a net core application must implement Kestrel or http.sys because it runs in an independent process. And that IIS allows to complete the features of the Kestrel server.
Is there a way to host a net core microservices application on IIS without Kestrel and Http.sys?
Thank you in advance
No, IIS serves as a reverse proxy only. Kestrel is absolutely required. HTTP.sys is an alternative to using IIS, but either way Kestrel is what runs the Core app.
I want to host a ASP.NET Core application on shared windows host. I read the documentation and as far as I understood it can depend directly on the .NET framework, but other tutorials says that it cannot be done without the .NET Core (also my windows hosting provider said that it cannot be done).
Does the ASP.NET Core application can be host on windows shared hosting machine or additional configurations need to be done ?
Thanks.
Yes, you can. But your host needs the .NET Core Windows Server Hosting. Once your host has this installed, you can run your .net core app (full .net or .net core).
You can find more info here.
Yes, I have deployed ASP.NET core web apps to two different Windows shared hosting services successfully. I've had success with both framework-dependent and self-contained deployments. You can my instructions for doing a self-contained deployment here: https://birdsbits.blog/2019/02/18/publishing-an-asp-net-core-web-app-to-a-cheap-windows-hosting-service/
I've inherited an application that uses AppFabric hosted on an Win2K8R2 application server. I added the IIS feature to the server and I'm trying to get the IIS UI extensions installed. Can anyone advise on how to do that?
Thanks
Paul
Just install AppFabric on your server (download here)
For IIS Extension, you only need to install Hosting Administration.
Note, if you server is hosting a WCF/WF services, you will also need Hosting Services : without this feature, your service will not use Appfabric event if it's enabled in the config.
I'm using signalr to do some real-time events in my web application. I'm trying to force signalr to use the new websocket protocol but it won't, even if I specify it.
$.connection.hub.start({ transport: 'webSockets' })
I definitely have the web socket protocol installed and I am running Windows 8 with IIS 8.
What else do I need to do to enable web sockets support in signalr?
Ensure that your app is using the .NET 4.5 assembly from the SignalR package. If the project is targeting 4.0, or it started that way, then nuget would have added a reference to the 4.0 SignalR assembly which doesn't support websockets. If that's the case, then just uninstall and re-install the signalr packages into your project.
Web Sockets requires .NET 4.5.
If you try running it on Windows Server 8 in the future be sure to activate the Web Sockets feature.
If you are already using framework 4.5 but still no luck, add an HTTPS binding to your IIS website and access the website over HTTPS.