Designing and Developing ASP.NET 4 Web Apps (Exam 70-519) Tutorials
Client Side ASP.NET / Client Side Options
Visitors to VTC.com will be able to view all introductory videos for each training course.
Free Trial Members will gain access to first three chapters for each training course.
Full Access Members have full access to VTC.com�s entire library of video tutorials.
Learn More
Subtitles of the Movie (Designing and Developing ASP.NET 4 Web Apps (Exam 70-519) / Client Side ASP.NET / Client Side Options)
When you're designing and developing an ASP.NET website, one of the things that is going to come into play and a very important question you're going to have to answer very early in the design process is, how am I going to handle any Client Side functionality? Because if you'll think about just a little history here, as the worldwide web grew up, user interaction quickly became a driving force on what was considered good websites and bad websites. So as a result a lot of different Client Side functionality solutions exploded because as websites started to find Client Side solutions then the web started to feel more like these desktop applications and we started to see things like JavaScript started to show up on the browser side and it started to do some cool things in the browser. Then we saw Microsoft release technologies like ActiveX, it got a lot of attention, some people really loved it, some people hated it as hackers began to exploit it, it became considered a very high security risk and most people wouldn't allow it to happen. Then came Java with lots of Java based Client Side solutions and then of course everybody's favorite thing to both love and hate on the Internet and that is Flash. Flash can do some really, really cool websites, it also has a lot of limitations and it can be slow to load so you're going to have to look at this myriad of options and decide exactly how you want to design your web application. Now some of the best aspects of any of these technologies is going to be that the web applications don't involve setup or installation like desktop apps. If I want to put some Client Side functionality out there, I just simply write it, test it across multiple browsers and put it out there. It's not like a desktop application where I have to issue a new version, an updated version and the end user has to load it. No, this they get every time they make a new request to a website. They automatically get the new functionality that's coming to them, it's coded in, it runs in the browser, everything is cool usually. Now as this happens, the web apps begin to work and feel like what we used to know as desktop applications, these box things that we loaded off, of disks and installed on our local machine. It ran in the local memory processes and it was very quick and efficient and cool. Now these Client Side Options as they matured and as the browsers matured, they can be embedded into the browsers and provide even cooler functionality but there was a dark side to these technologies. The worst aspects of them was this one and it's still plagues us today, is not all browsers treat various options the same way. You can write some very simple JavaScript, run it in three different browsers and you get three slightly different renditions of how it actually shows up in the browser. Some browsers don't use the same objects and just all kind of things to start to really drive you nuts as a developer to try to support all these things with all the different browsers your users maybe connecting to your website with. Client code is isolated from the server so if I've got a functionality out there that's running in the browser that needs to contact the server, guess what? We've got to give them that ugly pause why we connect to the server, run that particular functionality and then return it back out to the client once again. And then of course, the worst aspect of any Client Side technology is security. Trust me there's a 13 year old in your neighborhood right now who readily knows how to thwart JavaScript and use it to his or her advantage to create a security issue on a web server somewhere. Now in Microsoft's ASP.NET 4 they've introduced or they continue to mature something called ASP.NET AJAX. Now it deals with the best aspects of these technologies and it starts to answer some of the questions on the worst aspects of these technologies and so over the next few videos we are going to take a look at ASP.NET AJAX and look at probably the Client Side Option that you want to consider and the one that you really want to be up to speed on as you go to take this exam. So in the next few videos now, we're going to take a closer look at AJAX in ASP.NET.
Tutorial Information
| Course: | Designing and Developing ASP.NET 4 Web Apps (Exam 70-519) |
| Author: | Mark Long |
| SKU: | 34292 |
| ISBN: | 978-1-61866-029-9 |
| Release Date: | 2011-12-31 |
| Duration: | 8.5 hrs / 108 lessons |
| Work Files: |
Yes |
| Captions: | No |
| Compatibility: |
Vista/XP/2000, OS X, Linux QuickTime 7, Flash 8 |
VTC Sign up & Benefits
- Unlimited Access
- 81,350 Video Tutorials (14,200 free)
- Video Available as Flash or QuickTime
- Over 715 Courses
- $30 for One Month Access
- Multi-User Discounts Available
