With the release of ASP.NET MVC 4 one of the exciting features packed in the release was ASP.NET Web API. In a nutshell, ASP.NET Web API is a new framework for creating HTTP services that can reach a broad range of clients including browsers and mobile devices. ASP.NET Web API is also an ideal platform for building RESTful services.

Microsoft shipped “ASP.NET and Web Tools 2012.2” update sometime in February 2013. This included updated ASP.NET MVC Templates, ASP.NET Web API, SignalR and Friendly URLs. So if you take the latest you get all the latest bits ASP.NET has to offer so far. Rest of this post assumes that you have installed the 2012.2 bits. I assume you know the Web API fundamentals like API Controller,  Action and Route configuration as I wont get into discussing those.

In this post, we will see how Web API can be created in a Web Form application or project. I will be using Visual Studio Express 2012 for Web as my IDE for this post.

Create ASP.NET Web Form Project:

To start out with, create a empty “ASP.NET Empty Web Application” or “ASP.NET Web Forms Application”. Both of these templates are Web Forms based. So doesn’t matter which one you choose. For the sake of the demo I will choose ASP.NET Empty Web Application. Fire up a Visual Studio Express 2012 for Web, File > New Project > ASP.NET Empty Web Application and give a name to the project.

Fig 1: New Project Dialog

Visual Studio will create the project and you should have the infrastructure ready. And here is how the solution will look like:

Fig 2: Solution Explorer

Adding a Web API Controller:

Since Web API is kind of API we are building lets bring in some best practice here. It is good to have a folder created with the name “Api” and store all your Web API controllers here. With the latest release of ASP.NET, you can create Controllers in any folder you like. So go ahead and create a new folder and name it API. Here is how the Solution Explorer will look like:

Fig 3: Api Folder

Now lets add a Web API Controller. Right click on Api folder, select Add > New Item. You will find a new Item Template called “Web API Controller Class”. Select Web API Controller Class Item. Note that Visual Studio names the class as ValuesController1.cs – you can rename it to ValuesController. Make the changes and click Add.

Fig 4: Adding Web API Controller Class

Here is the glimpse of the code inside ValuesController class provided by default:

 
Fig 5: Values Controller Class

There is one magic Visual Studio does under the hood when you add a Web API Controller class. It adds the following packages which is required for making the Web API work:

• Microsoft.AspNet.WebApi
• Microsoft.AspNet.WebApi.Client
• Microsoft.AspNet.WebApi.Core
• Microsoft.AspNet.WebApi.WebHost
• Microsoft.Net.Http
• Newtonsoft.Json

You can see that there is a packages.config file added to the solution and it is used by Nuget package manager to keep track of the packages. The above packages make it possible for Web API to be hosted within the Web Forms application or project. So, is this all to make the Web API run – well not yet. Web API works with the routes and we have not yet configured the routing engine to grab the request and see if it is web api request. Lets do that in next section.

Setting up Web API Routes:

One thing you will notice in the solution is – it does not contain a Global.asax file. Well that’s why the name of the template “ASP.NET Empty Web Application” its literally empty and you need to add things needed manually. So first lets go ahead and add a Global.asax. Right click on the project, select Add > New Item > Global Application Class. You will get the blank Global.asax i.e. the class will have all the event handler added up but empty. The event handler which is of importance for us is Application_Start. Lets now configure the Http Routing. As a best practice create a new folder called App_Start at the root of the project. Add a new class, call it WebApiConfig.cs and make it a static class. Idea behind naming the folder as App_Start is that, codes in this folder are the first to be called or executed when the app starts. So here is how the solution explorer looks like now:

Fig 6: Solution Explorer

Now add the following code to WebApiConfig.cs. We are creating a static method called Register and it will register the Http routes for the application:

   1: public static void Register(HttpConfiguration config)

   2: {

   3:     config.Routes.MapHttpRoute(

   4:         name: "DefaultApi",

   5:         routeTemplate: "api/{controller}/{id}",

   6:         defaults: new { id = RouteParameter.Optional }

   7:     );

   8: }

Listing 1: WebApiConfig Register method

What we are doing in Register method is:

• Get the HttpConfiguration object
• Use the Routes table to configure routes
• Map a Http Route to our API by providing a pattern
• Default pattern is to look for “api/{controller}/{id} – where {id} is optional

Here is the complete code of WebApiConfig.cs file:

   1: using System;

   2: using System.Collections.Generic;

   3: using System.Linq;

   4: using System.Web;

   5: using System.Web.Http;

   6:  

   7: namespace WebAPIinWebForms.App_Start

   8: {

   9:     public static class WebApiConfig

  10:     {

  11:         public static void Register(HttpConfiguration config)

  12:         {

  13:             config.Routes.MapHttpRoute(

  14:                 name: "DefaultApi",

  15:                 routeTemplate: "api/{controller}/{id}",

  16:                 defaults: new { id = RouteParameter.Optional }

  17:             );

  18:         }

  19:     }

  20: }

Listing 2: WebApiConfig class

Now, this is just a definition but where do we actually call it. Remember we added a Global.asax file – we will call the Register method from the Application_Start event handler. Here is the code to do that:

   1: protected void Application_Start(object sender, EventArgs e)

   2: {

   3:    WebApiConfig.Register(GlobalConfiguration.Configuration);

   4: }

Listing 3: Global.asax Application_Start event handler

And we have a Web API created in Web Forms project now. Next lets see how to test it out.

Testing Web API:

At this moment if you build and run the project, browser may show you 403 and that is expected as we do not have an Default.aspx or index.html. Don’t worry as we are interested in testing the API controller. Remember the default patterns we set up for API routes – our Web API is available at a URL “http://localhost:<port>/api/Values”. So type the URL and hit enter. IE will show you the response as a JSON value. This is because IE always sends the Accept header as application.json and Web API server implementation will respect the content negotiation and send the appropriate data type to the client.

Fig 7: Testing API Controller in IE

Here is the same response when seen from Firefox:

Fig 8: Testing API Controller in Firefox

Summary:

This was a post intended to show case the fact that Web API are not meant only for ASP.NET MVC project types but it can be hosted even in ASP.NET Web Forms project too. Thanks to the tooling, Visual Studio does all the magic under the hoods when you add a Item template of type “Web API Controller Class”. We saw how easy it is to set up a api controller and test it.  Hope this gives you a jump start on creating web API in web forms project. Do let me know if you have any feedback on this article. It will help me better myself.

Till next time – Happy Coding. Code with Passion, Decode with Patience.

Back again with one more episode of Uncut & Unedited. This is episode number 30. I have a very interesting guest on this episode. He is none other than Gaurav Kapur – Multi Media Mercenary and Bollywood personality. If you are a hard core cricket fan I am pretty sure you wont be missing the Indian Premiere League 2013 that is happening and Gaurav Kapur is one of the anchors – on the field and inside the studio. He was in Bangalore during Windows 8 launch event by Microsoft during Oct 2012. I was fortunate enough to grab him and get his 10 minutes out of the busy schedule he had.

Gaurav Kapur

Being a Bollywood personality, he showed a lot of knowledge on Windows 8. So I just couldn’t let him go and decided to interview him and get his view on Windows 8. You will be amazed to hear him talk technicalities of Windows 8. He shares his experience on his usage of Windows 8 OS. Here are some of the questions I asked to him:

• Who is Gaurav Kapur ?
• Is Gaurav Kapur a tech savvy person ?
• His favorite Gadgets
• His experience with Windows 8
• One feature he likes the most in Windows 8
• His experience with touch devices

Here is the video of the interview;

I had a great time shooting this interview. Gaurav Kapur is really a tech savvy and fun person to talk to. Hope you too will enjoy this episode. Do let me know your feedback if any.

Till next time – Happy Coding.

Last year somewhere around May/June time frame one of my good friend Senthil Kumar passed on an opportunity that came to him. He was approached by Packt Publication to write a book on Windows Phone with F#. He couldn’t take it up and passed on the opportunity to me. June was a period of transition for me and I was leaving my previous job and moving on to a new role at Telerik. I had asked Telerik that I will join from July 1. So I had some time between June 8 to July 1. I took the book writing assignment from Packt and everything was settled and only thing left was to start writing. I have written many blogs but book writing is a completely new experience. So I wanted to experience that and I jumped on.

So my journey on “Windows Phone 7.5 Application Development with F#”. Had to learn a little bit of F# to start writing the book. It was a great experience for me while writing this book. I had to do my first drafts and that went through a technical review by 2 people. After those reviews I had to provide my second drafts. Once that passed the technical editorial team at Packt Publishing was performing digitization and they would come up with questions which I had to take care. So with almost close to 10 months of hard work I could see my words getting closer to be printed as a book.

On April 17, 2013 I was overjoyed to learn from Packt Publication that my book has been printed. I just couldn’t believe that the hard work of 10 months has finally paid off. So here is pic of the printed book:

Here is the link to the book online: http://gnl.me/WPFsharp

In this book you will find the basics of developing Windows Phone 7.5 Application development using F# language. In the book, I walk you through in setting up the environment, using the templates to create apps, controls usage, orientation handling, choosers and launchers and end with a look at the device sensors. At the time I started writing the book the version of Windows Phone available was 7.5 so it focuses completely on 7.5 SDK. But by the time the book was out Microsoft has already released a new version called Windows Phone 8.

I want to take this opportunity to thank my friend Senthil Kumar for passing on the opportunity to me, Packt Publication for the working very patiently with me right from day one to getting printed. Last but not the least my lovely wife Rashmi and my son Adithya – they have been very supportive and patient through out this journey of 10 months.

As of now I can call myself an author and in my slide decks I can start adding a slide with the pic of my book . Hope, you will read the book and let me know where I can improve. This is my first attempt and I have tried my level best to do justice to the book. There is always a scope for improvement and better myself. So do let me know of any feedback you may have.

Till next time, Happy Coding. Code with Passion, Decode with Patience.

I am back with another edition of Uncut & Unedited. This is episode number 29. In this episode I have a very special person as my guest. I have been stalking him for a while to give me his 10 minutes for my show. I have none other than Mr. Glen Block who is currently the Program Manager on Windows Azure team.

In Feb 2013, Microsoft hosted the Global MVP Summit and I was fortunate enough to attend the summit this time. I am an MVP from last 2 years but this has been my first MVP summit. Its here in this summit that I was able to catch Glen in person and ask him for an interview. Before the summit we had a lot of twitter conversation and I wanted to meet him in person desperately and interview him. In spite of his busy schedule, Glen took me to Microsoft Office in downtown Bellevue and got us a empty room. I am grateful to Glen for this.

Here are  the questions I put forth to Glen:

• His roles & responsibilities in Microsoft
• His involvement with MEF & Prism
• His involvement with WCF REST
• His involvement with Azure & Node.js
• His involvement with Azure Mobile Services – ZUMO
• His visit to India in future

I had a great time interacting with Glen and interviewing him. He is one of the great interviewee that I have seen. It was an awesome feeling sitting there and listening to him when he talks about Prism, MEF, WCF REST, Azure, Node.js and ZUMO. Pheww that’s a lot of technologies that he has been playing with. I am really delighted to have him on my show and hope this is one of the good episodes for you guys. I wish we get to see him in India soon.

Here is the video of the interview:

Do sit back and enjoy the episode. Do let me know any feedback you may have. It will help me to better myself.

Till next time, Happy Coding. Code with Passion, Decode with Patience.

Back with one more episode of Uncut & Unedited. This is episode number 28. And I have a a good friend on my show this time.

I was attending Microsoft TechEd India 2013 which was help on Mar 18/19 here at Bengaluru. This is one of the premiere events that we Microsoft Technologies geeks wait for. 2 days of technical fun and information overload is an amazing things and atmosphere is always great. This time too Pluralsight was participating with their booth at TechEd. Aaron Skonnard one of the co founders of Pluralsight was here in Bengaluru. In spite of the fact that he landed 6AM on Mar 18 – he was back at the booth by 11Am to meet the crowd. So I didn’t wanted to disturb him on that day. Caught hold of him on 19 and asked him if I can interview him for my show. He agreed for it readily and we went to the garden in front of Hotel Lalit Ashok. I am grateful to Aaron to give me his 10 minutes in spite of his busy schedule. But it is always so cheerful to talk to Aaron. This is his second presence on my show.

I ask Aaron the following questions:

• Series A funding that Pluralsight raised recently – Aarons perspective on this
• Pluralsight plan for future now that they have funding
• Course areas that Pluralsight is looking out for
• Pluralsight’s India presence and its impacts
• Aaron’s TechEd India 2013 experience

Here is the video of the interview:

Hope you enjoy this episode. If you have any feedback do please leave it in the comments. It will help me to better myself.

Till next time, Happy Coding. Code with Passion, Decode with Patience.

On Mar 30, BDotNet i.e. Bangalore DotNet User Group conducted a UG Meet. This UG meet focus was on .NET Frameowrk 4.5. We had ASP.NET MVP Chaitra Nagaraj present the first session on “.NET 4.5 in a NutSheel”. Chaitra took the audience for a whirlwind tour of 4.5. She covered pretty much everything .NET 4.5 release had in 1 hour.

I spoke in this UG Meet on ASp.NET WebForms. Many think that Microsoft is focusing more on ASP.NET MVC and has forgotten the WebForms technology. But that’s not the case. Microsoft is investing heavily on one of the mature and stable toolset namely WebForms. This is evident from the loads of new feature added to WebForms in 4.5 release. So my session was Part 1 of many more sessions to come. In this first session I gave a glimpse of whats new in WebForms and focused on 3 major things available in the release. They are:

• Strongly Typed Data Binding Expressions
• Model Binding
• Value Providers in Model Binding.

The slide decks from the session are available on SlideShare. Here is the slide deck embedded in this post:

Also, I was supposed to record the presentation for folks who couldn’t attend the session. It was first time I was recording using Camtasia. I did not see that audio was not getting captured as the setting was set to do not record. So I had video but no audio. Later I decided to re record the whole session I gave as a screen cast. Below is the screen cast video hosted on my vimeo channel.

ASp.NET WebForms 4.5 – New Shiny Things – Part 1 from Lohith on Vimeo.

ASp.NET WebForms 4.5 – New Shiny Things – Part 1

I have started a series on new things in WebForms. So keep looking out for my blog.

Till next time, Happy Coding. Code with Passion, Decode with Patience.

Last year I had concentrated completely on Open Data Protocol and had written blog posts pertaining to OData. This year I was looking out for broader areas where I can start contributing to the community. And being an MVP in ASP.NET area I haven’t written much on ASP.NET technologies. So this year I will be writing about ASP.NET technologies i.e. the whole breadth of ASP.NET technologies which include WebForms, MVC, WebPages, WebApi etc.

In August 2012 Microsoft released .NET framework version 4.5 and lot of goodies came along with that. One such area of ASP.NET which got the goodies is WebForms technology. ASP.NET WebForms is one of the stable web technology stack on .NET now. It has seen almost 10 years of adoption now. So as part of 4.5 WebForms has got a lot of improvements. This post is a prelude to series of posts I intend to write to cover all the good things WebForms has now.

ASP.NET WebForms 4.5 has the following shiny things added. They are:

• Model Binders
• Strongly Typed Binding Expressions
• Unobtrusive JavaScript for client side validation
• HTML encoded data binding expression
• Fallback support for CDNs in ScriptManager
• Support for HTML5 form types
• Friendly URLs

As you can see a lot of good stuff getting into ASP.NET WebForms. This year I attended the Global MVP Summit held at Bellevue, Seattle and was able to meet most of the ASP.NET team members like Scot Hanselman, Scot Hunter, Damian Edwards, Eilon Lipton. When asked about the fact about MVC getting a lot of attention and is WebForms losing interest – one point was clear from their answers that Microsoft is bringing lot of MVC goodness back to WedForms. The Model binding concept is already present in MVC and is being brought to WebForms now. So Microsoft will continue to invest in WebForms – the mature and stable web technology stack on .NET platform.

I will start diving into each topic in next blog posts to come. If you are excited and interested in WebForms like me – stay tuned.

Till next time – Happy Coding. Code with Passion, Decode with Patience.

Background:

In my last post “HTML5 Input Types Support in ASP.NET WebForm”, we looked at the HTML5 input types support from the ASP.NET WebForm TextBox control. One of the other cool features of HTML5 specification for a input controls is the placeholder attribute. Currently there is no support for placeholders in ASP.NET Webform TextBox control. In the blog post we will see how we can achieve this by creating a custom control.

What is a Placeholder:

According to the HTML5 Living Standard, the placeholder attribute is defined as follows:

The placeholder attribute represents a short hint (a word or short phrase) intended to aid the user with data entry when the control has no value. A hint could be a sample value or a brief description of the expected format. The attribute if specified, must have a value that contains no LINE FEED or CARRIAGE RETURN characters.

Here is the link to the living standard: http://www.whatwg.org/specs/web-apps/current-work/multipage/common-input-element-attributes.html#the-placeholder-attribute

Supporting Placeholder attribute in a TextBox – the Idea:

If we talk from a plain HTML perspective, in order to support the placeholder attribute, all we need to do is to add a attribute named “placeholder” and provide a value to that attribute on a INPUT control of type text. So here is how the HTML will look like:

<input  type=â

Now, we know that the ASP.NET WebForm TextBox control does not contain any property to support this. And all we have to do is to add an extra attribute on the input type control. So the idea to achieve this is as follows:


Create a custom web control which inherits from TextBox class


Add a public property of string type and name it “Placeholder”


Add attribute called placeholder during rendering of the control


We will look at the above steps one by one:
Creating Custom Web Control:
Open  visual studio and create a new project of type ASP.NET Server Control. I am selecting C# as the language.

By default, the project will contain a ServerControl1 class when the project is created. We will use the same class and modify the class name to suit to our needs. First, rename the class to lets say “HTML5TextBox”. Currently the class inherits from WebControl. Instead we will inherit the class from TextBox. This is because, we just want to subclass the TextBox and add an attribute just before rendering the user control. By doing this we get to use all the plumbing the TextBox control already provides in the control rendering. So now we have a HTML5TextBix control which inherits from TextBox. The code will look like below:

Remove all other contents of the textbox for now. Lets get on with the next step which is creating a placeholder attribute.
Placeholder public property on the control:
Now that we have the class created, we will now expose a public property to set the placeholder text. This property will be set with a value in the page where this control will be consumed. If no placeholder value is set, the control will have a default value to set. Here is the property definition:



As you can see, we have created a backing field and a public property to expose the Placeholder attribute. Next we will see how to add the attribute to the TextBox rendering.
Add Placeholder attribute while rendering TextBox control:
Now we have pretty much set up all the infrastructure needed to finish this. One thing we need to understand now is the rendering mechanism of a custom control. I suggest you read the following MSDN article to understand this: http://msdn.microsoft.com/en-us/library/aa338806(v=VS.71).aspx. So I will not be digging deep in to the rendering mechanism as that is out of this blog post scope.
As said in the idea section, we just want to include a custom attribute during the controls output rendering. The custom control infrastructure provides us with a hook for this. It is known as AddAttributesToRender method. Here is the official definition of this method:

The AddAttributesToRender() method gets a HtmlTextWriter and all we need to do is to use the AddAttribute() method on the writer to insert our custom attributes. Here is the code to perform this action:

As you can see we use the AddAttribute(string key, string value) overload to insert our custom attribute. the attribute name is “placeholder” and the value is what has been set in a page where the control is consumed.
Here is the complete code of the control:
    [DefaultProperty("Text")]
    [ToolboxData("<{0}:Html5TextBox runat=server></{0}:Html5TextBox>")]
    public class Html5TextBox : TextBox
    {
        string _placeholder = "enter value";

        [Bindable(true)]
        [Category("Appearance")]
        [DefaultValue("enter value")]
        [Localizable(true)]
        public string Placeholder
        {
            get
            {
                return _placeholder;
            }
 
            set
            {
                _placeholder = value;
            }
        }

        protected override void AddAttributesToRender(HtmlTextWriter writer)
        {
            writer.AddAttribute("placeholder", _placeholder);
            base.AddAttributesToRender(writer);
        } 
    }

Consuming the Custom Control:
In any ASP.NET WebForm project, add reference to the Custom Web Control library. Then in any webform i.e. lets say in Default.aspx, use the register tag to register the control first. Here is the register tag code:

Next, just create the textbox control as usual. Here is the code to consume the custom control we just created:

And here is the output of how the control will behave when rendered:

You can see that we now have the HTML5 placeholder as part of ASP.NET WebForm TextBox control. Similarly any other attributes which is not supported currently can be customized as we did for placeholder attribute.
Summary:
Being a stable platform, ASP.NET WebForm technology has a lot of hooks to quickly customize the controls according to our needs. We just saw how easy it is to customize a TextBox to add a HTML5 attribute named placeholder. In this way, even being in ASP.NET WebForm platform, we can start making our code HTML5 compliant.
PS: If anybody from Microsoft ASP.NET does come across this article, I would request them to see if the HTML5 attributes can be pushed into the TextBox control itself. That would void the above effort to support just an attribute and the TextBox will be able to support out of the box the HTML5 attributes. We will wait and watch .


          
]]>
			http://www.kashyapas.com/2013/02/03/html5-placeholder-support-for-asp-net-webform-textbox/feed/
		1
		http://www.kashyapas.com/2013/02/03/html5-placeholder-support-for-asp-net-webform-textbox/
		
		
		http://feedproxy.google.com/~r/KashyapasnetRumbles/~3/4c7CT1gYP6E/
		http://www.kashyapas.com/2013/02/01/html5-input-types-support-in-asp-net-webform/#comments
		Thu, 31 Jan 2013 18:49:00 +0000
		kashyapa
				
		
		
		
		

		http://www.kashyapas.com/?p=1324
		Continue reading →]]>
				
Background:
HTML5 is the talk of the town. Everyone is talking about HTML5 everywhere. One of the cool features of HTML5 is the introduction of new input types for forms. These new input types allow better input control and validation.
ASP.NET 4.5 which was released in Aug 2012 did have enhancements with respect to the input types support. The input types i.e. TextBox in ASP.NET WebForms now support all of the new HTML5 input types. We will take a look at the input types from WebForms perspective in this blog post.

HTML5 Input Types:
HTML5 has introduced several new input types for forms. These types improve the form input and provide better input control and validation.  Following table depicts input types, their description and browser support:



Input Type
Description
Supported Browser


color
fields that should contain a color
Chrome, Opera


date
fields that should contain date
Chrome, Safari, Opera


datettime
fields that should contain date time (with time zone)
Safari, Opera


datetime-local
fields that should contain date time (with time zone)
Safari, Opera


email
fields that should contain email address
FF, Chrome, Opera


month
fields that should contain month and year
Chrome, Safari, Opera


number
fields that should contain number
Chrome, Safari, Opera


range
fields that should contain value from a range of numbers
Chrome, Safari, Opera


search
used for search fields (a search field behaves like a regular text field)
Chrome, Safari


tel
fields that should telephone number
NONE


time
fields that should contain time
Chrome, Safari, Opera


url
fields that should contain URL address
FF, Chrome, Opera


week
fields that should contain week and year
Chrome, Safari, Opera



Creating ASP.NET WebForm Project:
Fire up a Visual Studio 2012 and create a new ASP.NET WebForm project. Select File > New Project and in the New Project dialog select “ASP.NET Web Forms Application” template. Below is a screenshot of the new project dialog:

Give it a name and click Ok. Visual Studio will go ahead and create the project.
Add TextBox to a WebForm:
Open the Default.aspx that gets generated by default. Remove all the content from the content place holder named “BodyContent”. Just add a TextBox – either drag and drop from the toolbox or type it out. If you are in the designer mode, select the TextBox or if you are in source code mode place the cursor in the TextBox tag. Next press F4 to open the properties window. In the Properties window, select TextMode and click on the value field. It will now show up a drop down list with all the supported text modes. Till now, TextMode supported 3 values namely – SingleLine, MultiLine and Password. With ASP.NET 4.5 this property now supports all the newly defined HTML5 input types. Here is a screen shot of the same:


Examining the output:
As we all know, a TextBox gets rendered as a HTML <input> type when the pages gets to the client. For the sake of testing, I had set the TextoBox TextMode to “color”. Here is the TextBox control definition:
<asp:TextBox ID=”txtName” runat=”server” TextMode=”Color” Width=”300px”></asp:TextBox>
Here is the generayed HTML for the above TextBox:
<input name=”ctl00$MainContent$txtName” type=”color” id=”MainContent_txtName” style=”width:300px;” />
Here is a screenshot of how this looks in different browsers:



Chrome Output
Opera Output








As you can see different browsers have implemented in different way but what matters is the value that the field will contain. I clicked on the submit button and put a break point in the button click event handler. When I looked at the text box value, it contained the hex code of the color that we select as part of the color picker. Here is a screen shot which depicts the scenario:

So play around with other input types also and see how browser implement them. Not far are the days when all browser will support these input types and user experience for input and validation can be standardized.
Summary:
HTML5 is becoming so mainstream that ASP.NET WebForm is also trying to catch up in the race. I see that it’s a good move to support the html5 input types. People who are developing in WebForms technology can move their application towards HTML5 compliance slowly and be ready for the the full embrace when it happens.


          
]]>
			http://www.kashyapas.com/2013/02/01/html5-input-types-support-in-asp-net-webform/feed/
		1
		http://www.kashyapas.com/2013/02/01/html5-input-types-support-in-asp-net-webform/
		
		
		http://feedproxy.google.com/~r/KashyapasnetRumbles/~3/7hLl_5oLUjc/
		http://www.kashyapas.com/2013/01/07/roshan-abbasndashbollywood-personalityndashuncut-amp-unedited/#comments
		Mon, 07 Jan 2013 05:19:00 +0000
		kashyapa
				
		

		http://www.kashyapas.com/?p=1307
		Continue reading →]]>
				
I am back with one more episode of Uncut & Unedited. This is episode number 27. My guest in this episode  is Mr. Roshan Abbas. 

Roshan Abbas is a Bollywood or Indian Film Industry personality. He is multi faceted person with his experience in Indian Radio, Indian Television, India Film Industry and Media. Currently he runs his own company called Encompass which takes care of the event management of big companies in India. You can know more about Roshan Abbas here: http://roshanabbas.com/.
Roshan was in Bangalore for Windows 8 launch that happened on Oct 31 2012. I had bloggers invite to be part of the launch in Bangalore. Roshan Abbas was part of the team which enacted a small skit depicting how Windows 8 can change one’s life. He did an excellent job in explaining some of the features of Windows 8. I hesitantly approached Roshan for his 10 minutes for my show. I must say he was so down to earth and instantly obliged my request and we had the interview done in a corner. Here are the questions that I ask Roshan:



Roshan Abbas and his background
How has technology played a role in his life
Windows 8 and his experience
His experience with windows 8 hardware
One thing he liked the most in Windows 8 

Here is the video of the interview:

Roshan Abbas–Bollywood Personality–Uncut & Unedited

Hope you enjoy this episode and stay tuned for more. Do leave your feedback or comments if you have any.
Till next time – Happy Coding.


          
]]>
			http://www.kashyapas.com/2013/01/07/roshan-abbasndashbollywood-personalityndashuncut-amp-unedited/feed/
		1
		http://www.kashyapas.com/2013/01/07/roshan-abbasndashbollywood-personalityndashuncut-amp-unedited/