I'd like to integrate chat into my site and am open to a solution like this site's, but am open to others if they exist.
What chat sites do you know of that can integrate into an MVC site?
I have used both the WebSync JavaScript and Silverlight API's.
In your case you could use the JavaScript API from an MVC app.
Creating chat with WebSync is really easy and works very well. WebSync is a highly scalable HTTP Comet/Reverse Ajax server. They even offer a offer a hosted service. It has a cost if you need to support more than 10 concurrent users.
Here's one project on CodePlex you might take a look at.
Related
I use ASP.Net MVC 5 and kendo-ui in my project and i want to create a feature that enable me to send a notification to all users from server so can anyone tell me an architecture, pattern or technology should i use ?
or any recommendation for tutorial
It seems that you want something like broadcast to available clients.
You can use SignalR.
Nice tutorial is available at SignalR with asp.net mvc
you can use for more info about SignalR
you have google for more info on signalr.
I hope this helps.
I am trying to create an ASP.NET MVC web application,I'm trying to understand what is the use of the check mark "WebAPI" ,I don't seem to find any different selecting or unselecting this while creating the project,can anyone throw some light?
ASP.NET Web API is a framework that makes it easy to build HTTP services that reach a broad range of clients, including browsers and mobile devices. ASP.NET Web API is an ideal platform for building RESTful applications on the .NET Framework. Web API: Guidance.
You can take knowledge from this video. Thanks
I build web apps using ASP MVC and I am looking at using ReactJS. I have seen a few examples of React integrated into an ASP.NET MVC project and I don't really see the value over SignalR, which is what I use now for all real-time updates and communications.
I am hoping someone can go over the benefits of using React vs SignalR or even why I should be using React. Its popularity makes me think there is more to it that I'm just not seeing and I would hate to fall behind if it is more powerful and can help me do more.
Thank you for your responses!
React is used to build a single page apps or SPA, this will give you a desktop like UI, if you want it to be more interactive, then you can use it with SignalR to receive real time updates from the back end.
Facebook site alone is the idea of React, ex: responsive, no page refresh.
Integrating it with something like SignalR, adds the real time notifications about comments and posts
You should'nt compare apples and oranges.
React is a JS Library for building User Interfaces and SignalR is an abstraction, which will help you to send messages from server to client (also the other side).
I developed a website in ASP.NET MVC 4 using NHibernate, now I need to perform an integration with the site using Windows Forms.
How can I perform authentication system using the same users?
What technology should I use? Web API, SOAP or Rest?
Thanks!
Small clarification of terms : REST is an architectural style, SOAP is a protocol for exchanging information, and Web API is a framework to build HTTP Services.
The stock answer for questions like this is "It depends"
Before you continue with a technology selection, currently is your method for authenticating users separated properly from your business/presentation logic?
If that is the case, being that you are using MVC 4, Web API may be the path of least resistance, you can put all of the functionality that requires authentication behind Web API calls. And your controllers will call them. Once that is done, a Windows forms app can consume the data in a similar way.
What is the best way to use live id authentication with azure based asp.net mvc project?
I find the options
1) With in Live SDK, there are options like REST, JavaScript, C# etc.
2) Since my project will be hosted in azure, there is another way "Securing Web Applications with ACS" http://msdn.microsoft.com/en-us/library/gg185928.aspx
Please suggest the design and also support with pros when an particular approach is good.
You definitely want to work with ACS. Not only is it intended for this purpose, there's a fully worked up example at
http://msdn.microsoft.com/en-us/library/gg185975.aspx
which will give you a flying start.
ACS, and Windows Identity Foundation in general, lets you take the approach of separating identity verification from your application altogether. This saves a ton of code and means that you have much less "plumbing" to support.