My Latest Book – Professional ASP.NET 3.5 AJAX

I just got back from a business trip and sitting there on the counter was a copy of my latest book from Wrox! This book (my 20th) is titled Professional ASP.NET 3.5 AJAX. This was a fun book and I wrote this with some great co-authors including Matt Gibbs, Dan Wahlin, and Dave Reed. Amazon says that the book will be available on February 3rd (not too far away). Here is some of the introduction I wrote for the book:

-----------------------------

ASP.NET revolutionized Web application development. The platform handles many of the complexities of creating Web applications. Now ASP.NET AJAX takes the development platform even further. The lines between rich client applications and traditionally less interactive browser-based applications are being further blurred with the use of this technology.

The ASP.NET AJAX Library brings object-oriented programming to JavaScript development for modern browsers, and ASP.NET AJAX makes it easy to write rich Web applications that communicate with the Web server asynchronously. Again, the complexities are made easy by using ASP.NET.

The new server controls that are part of ASP.NET AJAX make it simple to designate parts of the page to be updated automatically without making the user pause and wait while the data is refreshed. You can have partial page updates without writing a single line of code. Other new controls let you alert the user that background work is happening and designate regular intervals at which updates occur. In addition, the ASP.NET AJAX Control Toolkit makes it easy to make your user interface really come to life with animations, modal dialogs, transition effects, and more.

Ajax is definitely the hot buzzword in the Web application world at the moment. Ajax is an acronym for Asynchronous JavaScript and XML and, in Web application development, it signifies the capability to build applications that make use of the XMLHttpRequest object.

The creation and the inclusion of the XMLHttpRequest object in JavaScript and the fact that most upper-level browsers support the use of this object led to creation of the Ajax model. Ajax applications, although they have been around for a few years, gained greater popularity after Google released a number of notable, Ajax-enabled applications such as Google Maps and Google Suggest. These applications demonstrated the value of Ajax.

Shortly thereafter, Microsoft released a beta for a new toolkit that enabled developers to incorporate Ajax features in their Web applications. This toolkit, code-named Atlas and later renamed ASP.NET AJAX, makes it extremely simple to start using Ajax features in applications today.

Prior to Visual Studio 2008, the ASP.NET AJAX product used to be a separate application that developers were required to install on their machine and the Web server that they were working with. This release gained in popularity quite rapidly and has now been made a part of the Visual Studio 2008 offering. Not only is it a part of the Visual Studio 2008 IDE, the ASP.NET AJAX product is also baked into the .NET Framework 3.5. This means that in order to use ASP.NET AJAX, developers are not going to need to install anything if they are working with ASP.NET 3.5.

Overall, Microsoft has fully integrated the entire ASP.NET AJAX experience in that developers can easily use Visual Studio and its visual designers to work with your Ajax-enabled pages and even have the full debugging story that they would want to have with their applications. Using Visual Studio 2008, developers are now able to debug straight into the JavaScript that they are using in the pages.

In addition, it is important to note that Microsoft focused a lot of attention on cross-platform compatibility with ASP.NET AJAX. Developers will find that the Ajax-enabled applications that they build upon the .NET Framework 3.5 are able to work within all the major up-level browsers out there (e.g., FireFox and Opera).

This book is aimed at experienced ASP.NET developers looking to add AJAX to their applications, and experienced Web developers who want to move to using ASP.NET and AJAX together.

In this book, I assume that you already have an understanding of how ASP.NET works. For an in-depth discussion of ASP.NET, I recommend Professional ASP.NET 3.5 by Bill Evjen, et al. (Wrox, 2008). The focus here is on how you can extend ASP.NET applications to update portions of the page asynchronously and to add richer UI elements to a page. ASP.NET AJAX makes it easy to enrich your existing application or to design a new application to provide a better experience for users. The differences among modern browsers have been abstracted, allowing you to write to a common set of APIs and trust that the user will get the correct behavior whether they are using Internet Explorer, Firefox, or Safari.

If you know how to author ASP.NET pages, you can easily start using the Microsoft AJAX library to manipulate the browser’s Document Object Model and communicate with the server to update the user’s view of data without forcing them to wait for the entire page to be refreshed.

This book covers ASP.NET 3.5 AJAX. It does not cover ASP.NET 3.5, on which ASP.NET AJAX is built. The examples lead you from the core of what is included in the ASP.NET AJAX Library through the core controls you would first start using. You build on that using the core JavaScript library and the ASP.NET AJAX Toolkit before covering debugging, deployment, and custom control development.

The ASP.NET 3.5 release includes the Microsoft AJAX Library as well as the server controls that can be used in ASP.NET pages to extend applications, making them more rich and interactive. It does so by leveraging the ASP.NET AJAX Library, which is JavaScript that runs in the browser. The server controls and JavaScript Library work together to let you update HTML with data obtained asynchronously from the server. The ASP.NET application services are exposed to JavaScript classes in the ASP.NET AJAX Library, making authentication and personalization accessible from the browser.

UPDATE: This book is now available on Amazon [Feb 10 2009].

Google Chrome Updates and Running on Windows 7

imageI’ve been playing around a bit with Google Chrome lately. I switched back to Microsoft’s Internet Explorer 8 as it answered a lot of the frustrations that I was having with Google Chrome (some key pages I like not rendering correctly). Though, when I switched  one of my computer’s operating system to Windows 7 Beta 1, I was even more frustrated. The IE that came installed on Windows 7 was a less than superior IE than what I could download off of the Microsoft site. I tried to install the latest IE 8 version from the Microsoft site onto Windows 7, but the installer would not allow that install to occur as it didn’t recognize the operating system of all things (see http://geekswithblogs.net/evjen/archive/2009/01/15/128669.aspx for more information on that).

It really got to a point where I couldn’t use this IE8 on Windows 7 – so I downloaded Google Chrome to the OS instead. I was still having some of the same issues rendering some key sites as before and it seemed that Google Chrome hadn’t updated its version since it was released. I did find out that you can opt to take the dev build of Google Chrome (or the Beta builds) by changing you updater using this Google Chrome Channel Changer (from this site: http://dev.chromium.org/getting-involved/dev-channel/). I opted for the Dev version and once you switch to this version, you can click on the Wrench in the toolbar and select About Google Chrome. From here, you can then check to see if you have the latest version (you won’t in the first case) and from here update your Google Chrome version.

image

After you Google Chrome is updated (you will have to close all Chrome instances and then reopen them), you will notice (if you are running on Windows 7) that it just doesn't work. To make Google Chrome work on Windows 7, right click on Google Chrome icon from your desktop and select Properties. From the first tab, the General tab, you will need to change the value of the text in the Target textbox to:

C:\Users\user\AppData\Local\Google\Chrome\Application\chrome.exe --in-process-plugins

The bold part is the part that you are adding. Once you have done this, it will work in Windows 7 just fine.

Technorati Tags: ,,,,
«January»
SunMonTueWedThuFriSat
28293031123
45678910
11121314151617
18192021222324
25262728293031
1234567