This post discuss about using WebSockets in ASP.NET 4.5. You can read this post to get an understanding about WebSockets. This post shows piece of code which uses WebSockets in ASP.NET 4.5 and the code is related to simple chat application.

The HTML of Web Form chat application looks as below



It contains a text box where you can type your text message and button where it sends a message to the server. You can notice there is <ul> element which shows the list of other messages which are arriving from the server.

Instantiate a W3C WebSocket JavaScript object and pointed to url to establish a connection to WebSockets Server.



The url starts with ws which runs on HTTP and pointing to .ashx handler which runs on ASP.NET server.

The Chat Handler code looks as below, The handler code checks whether sender is looking for WebSockets connection.





AcceptWebSocketRequest is a new method on Context object in ASP.NET 4.5.

ChatHandler is a wrapper API which implements lower level of WebSockets Handler.

The ChatHandler code looks as below



Override the OnOpen method in ChatHandler Class as below



We are modifying the OnOpen method code by adding the set WebSockets collection variable which contains the set of connection objects.





chatapp exposes a method BroadCast which accepts string or binary payload and send the message to all the objects in the collection. The payload in this piece of code is a JSON object.



Now To handle the messages that coming from the server, we are adding below piece of code in JavaScript by implementing a handler for OnMessage.

<image>

In above code we are actually parsing the JSON object that coming from server using JSON.parse method.

To send a message from client to server you can use the below code



Once this message comes to the server, you can check the type of message and can write the code as below



There is a OnClose method which you can override to close your WebSockets connection. For example when user closes the browser this method will fire and closes the connection.



When you run the application then output is as below

This post discuss about using WebSockets in ASP.NET 4.5. You can read this post to get an understanding about WebSockets. This post shows piece of code which uses WebSockets in ASP.NET 4.5 and the code is related to simple chat application.

The HTML of Web Form chat application looks as below



It contains a text box where you can type your text message and button where it sends a message to the server. You can notice there is <ul> element which shows the list of other messages which are arriving from the server.

Instantiate a W3C WebSocket JavaScript object and pointed to url to establish a connection to WebSockets Server.



The url starts with ws which runs on HTTP and pointing to .ashx handler which runs on ASP.NET server.

The Chat Handler code looks as below, The handler code checks whether sender is looking for WebSockets connection.





AcceptWebSocketRequest is a new method on Context object in ASP.NET 4.5.

ChatHandler is a wrapper API which implements lower level of WebSockets Handler.

The ChatHandler code looks as below



Override the OnOpen method in ChatHandler Class as below



We are modifying the OnOpen method code by adding the set WebSockets collection variable which contains the set of connection objects.





chatapp exposes a method BroadCast which accepts string or binary payload and send the message to all the objects in the collection. The payload in this piece of code is a JSON object.



Now To handle the messages that coming from the server, we are adding below piece of code in JavaScript by implementing a handler for OnMessage.

<image>

In above code we are actually parsing the JSON object that coming from server using JSON.parse method.

To send a message from client to server you can use the below code



Once this message comes to the server, you can check the type of message and can write the code as below



There is a OnClose method which you can override to close your WebSockets connection. For example when user closes the browser this method will fire and closes the connection.



When you run the application then output is as below

WebSockets are required to develop the rich and real time web applications. WebSockets can securely enable the real-time web. Before explaining the need of WebSockets we see what current Web is and it’s limitations.

What is Current Web?



We have rich web applications in current web which does the bi-directional communication. HTTP is a request-reply protocol and it is hard to PUSH on top of this protocol. Current programming model use different techniques to get connect with server, one of them is Periodic Polling.



example: Browser uses XmlHttpRequest to periodically query the server.



In Long Polling Server holds the HTTP request until there is a data to return. Client Sends the data as soon as previous request completes.

The limitations with current programming model

- Periodic polling technique uses high-latency.
- Long polling programming model is unintuitive.

Many scale out and Bandwidth issues with current programming model and limited cross domain support too.

What All WebSockets about is?

WebSockets is a new interoperable technology still undergoing standardization.

- It is full duplex bidirectional socket.
- You can program against using a browser and JavaScript API.
- WebSockets runs over SSL
- Designed for high performance – it is a light weight messaging protocol, it requires low bandwidth and latency.
- Important thing is it is designed to broad reach.
- WebSockets also has the built-in capability to make cross-domain calls.

What Applications can get benefit from WebSockets?

It supports

- Rich web applications
- Real-time applications and services(stock tickers and monitoring systems)
- Beyond browser – Windows 8 and mobile
- Online games

WebSockets are in

- Windows 8
- Internet Explorer 10
- .NET 4.5

How it works?

The secret source for WebSockets protocol is HTTP handshake which enables the socket connection. When a client sends an HTTP request to WebSockets server, it contains the some information in header which tells the server to establish connection over WebSockets. If Server is happy to accepts the request and it then sends the HTTP response back to client and switches the protocol and starts the communication.

Once the handshake is complete client and server communicates over WebSockets using HTTP connection. The Message communication is in either binary or UTF8 format.

The next version of Microsoft’s ASP.Net framework is currently in Beta and there are some pretty cool changes to how Request Validation works in version 4.5. Up until now, there were two ways to enable or disable request validation:

1. Globally – This controls request validation for the entire application.
2. Per Page – This controls request validation on a per-page basis.

In 4.5, the idea is to allow disabling request validation at the field level. This is a huge improvement, because it allows request validation to be enabled on a much larger scale and only be disabled for specific functionality. The first step in taking advantage of this is to make sure that the request validation mode is set to 4.5 in the web.config (shown below).

<system.web>
  <compilation debug="true" targetFramework="4.5" />
  <httpRuntime requestValidationMode="4.5" targetFramework="4.5"
               encoderType="System.Web.Security.AntiXss.AntiXssEncoder,
               System.Web, Version=4.0.0.0, Culture=neutral,
               PublicKeyToken=b03f5f7f11d50a3a" />

Now that the application is set up for the new validation mode, we can start taking advantage of this.

There are two ways to disable request validation on a specific control, a textbox for example. The first way, and probably the easiest, is to set the validation request mode to “disabled” in the html markup. The code below shows how this would look.

<asp:TextBox ID="txtASPNet" ValidateRequestMode="Disabled" runat="server" />

The second way is to set the validation request mode programmatically. This must be done in one of the earlier events for it to be effective. During my testing, it worked in the Page_Init event, but not in the Page_Load event. The code below shows how to do this in the Page_Init event.

protected void Page_Init(object sender, EventArgs e)
{
    txtASPNet.ValidateRequestMode = System.Web.UI.ValidateRequestMode.Disabled;
}

Web controls are not the only way to have such granular control over retrieving data without having it run the request validation. A new collection that was added to the request object is called “Unvalidated”. This collection allows accessing specific parameters, form variables for example, without checking the value against request validation. This is possible because Request validation has been modified to run when a variable is used, not when the request is made. It is important to note that web controls are always used, because the framework populates the controls automatically. Lets take a look at accessing an html input field without triggering request validation.

protected void cmdTest_Click(object sender, EventArgs e)
{
    // Access directly from the Unvalidated collection.
    Response.Write(Request.Unvalidated["txtHtml"].ToString());

    // Specify which Unvalidated collection to access.
    Response.Write(Request.Unvalidated.Form["txtHtml"].ToString());
}

As you can see, there are two ways to access the Unvalidated collections. You can pass the index to the collection directly, or specify exactly which collection you want to retrieve this data from. In this case, it was the forms collection.

Through my testing, I have not yet been able to access Unvalidated.Querystring values because the URL gets run against Request Validation so an exception is thrown before I get a chance to access the unvalidated version. I have not tried the other collections yet.

It is important to remember that manual validation should be performed in addition to using Request Validation. This is especially true for the unvalidated fields, but should also be practiced for fields that are validated. Request Validation is a very limited input validation and does not perform enough validation to be appropriate on its own.

You may receive the following error message while browsing an asp.net application

"Server Error in '/application name' Application
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off". "

This error might occur due to two scenarios.

1. There is an error in the application's logic with the inputformat, Type etc., and you have set the Custom Error Mode in the web.config to "On" and not specified a default redirect error page.

2. The web.config file is not well formed or having invalid characters and the application is not able to pick up the settings from the same.

Solution

1. Set the custom error mode to "Off" to view the error. After rectifying it and before deployment, change it to "On" and specify a default error page, as follows:-

<customErrors defaultRedirect="ErrorPage.aspx" mode="On">
</customErrors>

such that your users will not be able to see the actual error and get your friendly error page where you can politely say "An error has occured! Sorry for the inconvenience ..." .

2. If the above solution is not working (i.e. even after setting the custom error mode to On, the same "Server Error" occurs, then the likely chance is that your web.config file is not well formed and has invalid characters etc.,

To resolve, it copy paste the contents of the file to a notepad, save it as an xml file and try to browse the xml file in the browser. If the xml file is unable to be rendered by the browser and throws error, then you can find the place where the tags are not well formed or invalid character(s) exist and rectify them.

Things worth noting is Web.config is case sensitive and even trailing / leading spaces can cause the above error.

This article applies to .NET - ASP.NET 1.0, 1.1 Versions. Hope it help

HostForLIFE.eu was established to cater to an under served market in the hosting industry; web hosting for customers who want excellent service. HostForLIFE.eu – a cheap, constant uptime, excellent customer service, quality, and also reliable hosting provider in advanced Windows and ASP.NET technology. We proudly announces new FREE ASP.NET 4.5 beta hosting in our entire servers environment.

You can start hosting your ASP.NET 4.5 beta site on our environment for FREE. For more information about our new product, please visit our site at http://www.hostforlife.eu/ASPNET-45-Beta-European-Hosting.aspx

"This is limited program offered as an open beta for developers on a first come first serve basis. Our .NET 4.5 beta hosting account comes with 50 MB disk space and 50 MB SQL 2008 database space. With this .NET 4.5 beta release, we prove our existence in this hosting world and also we want the developers to give it try with the newest .net 4.5 in our hosting environment." said John Curtis, VP Marketing and Business Development at HostForLIFE.eu

So, why wait longer? Please visit http://www.hostforlife.eu/ASPNET-45-Beta-European-Hosting.aspx to register new account.

About us

We are European Windows Hosting Provider which FOCUS in Windows Platform ONLY. We support Microsoft technology, such as the latest ASP.NET 4, ASP.NET MVC 3, SQL 2008/2008 R2, and much more.

Our number one goal is constant uptime. Our data center uses cutting edge technology, processes, and equipment. We have one of the best up time reputations in the industry.

Our second goal is providing excellent customer service. Our technical management structure is headed by professionals who have been in the industry since it's inception. We have customers from around the globe, spread across every continent. We serve the hosting needs of the business and professional, government and nonprofit, entertainment and personal use market segments.

Sometime when you try to setup a application for your website on IIS7 you get following error when you load your website.



This happens when ASP.NET modules and handlers should be specified in the IIS and configuration sections in Integrated mode. This problem can be fixed using following workaround

1) Change application configuration: First way to fix this issue is to migrate the application configuration to work properly in Integrated mode. You can use “ AppCmd“ command to migrate the application configuration:

%windir%/system32/inetsrv/>Appcmd migrate config “<AppPath>

Where “ <AppPath>“ is the virtual path of the application, such as “Default Web Site/virtualapp1“.

2) Modify web.config: You have to manually move the customer entries in the <system.web>/<httpModules> and configuration to the <system.web>/<httpHandlers><system.webServer>/<handlers> and <system.webServer>/<modules> configuration sections, and either remove the <httpHandlers> and <httpModules> configuration OR add the following to your application’s or websites web.config:

<system.webServer>
<validation validateIntegratedModeConfiguration=”false”/>
</system.webServer>

3) Switch to Classic ASP.NET: Switch the website or application to an application pool that is configured to run in Classic ASP.NET mode. To move back to classic mode go to IIS7 Manager >> Select the site (which you want to switch) >> edit settings and you will get following screen



Press “ Select” button which will open a window “Select Application Pool” (check below image); Select “Classic .NET AppPool” from the drop-down and press OK.



Now try to Access your website/application.