Asp.net and c#

If you have been following my articles, you would have realised how easy it is to implement partial page refreshing in ASP.NET AJAX where we explored a single UpdatePanel and multiple Update Panel examples. Let us now consider a more complex scenario where we want to nest Update Panels. Page UpdatePanel 1 (Parent) UpdatePanel 2 (Child) The thumb rule with nested update panels is as follows:- Parent Update Panel refreshes all the contents including Child Update Panel's contents even if the Child Update Panel's update mode is set to Conditional Child Update Panel refreshes only its contents and doesnt refresh that of the Parent Update Panel unless, the update mode for the parent update panel is not set to Conditional Kind of confusing eh? Let us see it in action. Copy paste the following HTML and the subsequent source code to see it in action. see full detail: http://geekswithblogs.net/ranganh/archive/2007/05/16/112525.aspx

If you have been following my articles, you would have realised how easy it is to implement partial page refreshing in ASP.NET AJAX where we explored a single UpdatePanel and multiple Update Panel examples. Let us now consider a more complex scenario where we want to nest Update Panels. Page UpdatePanel 1 (Parent) UpdatePanel 2 (Child) The thumb rule with nested update panels is as follows:- Parent Update Panel refreshes all the contents including Child Update Panel's contents even if the Child Update Panel's update mode is set to Conditional Child Update Panel refreshes only its contents and doesnt refresh that of the Parent Update Panel unless, the update mode for the parent update panel is not set to Conditional Kind of confusing eh? Let us see it in action. Copy paste the following HTML and the subsequent source code to see it in action. see full detail: http://geekswithblogs.net/ranganh/archive/2007/05/16/112525.aspx

ADO .NET Most applications need data access at one point of time making it a crucial component when working with applications. Data access is making the application interact with a database, where all the data is stored. Different applications have different requirements for database access. VB .NET uses ADO .NET (Active X Data Object) as it's data access and manipulation protocol which also enables us to work with data on the Internet. Let's take a look why ADO .NET came into picture replacing ADO. Evolution of ADO.NET The first data access model, DAO (data access model) was created for local databases with the built-in Jet engine which had performance and functionality issues. Next came RDO (Remote Data Object) and ADO (Active Data Object) which were designed for Client Server architectures but soon ADO took over RDO. ADO was a good architecture but as the language changes so is the technology. With ADO, all the data is contained in a recordset object which had problems when

The .NET Architecture .NET security is not an island of technology, but a slice of a larger entity called the .NET Framework. Basic understanding of the .NET Framework is required before attempting .NET security programming. This chapter presents the basic concepts of the .NET Framework architecture and programming. This is an overview and is not intended to replace the independent study required for a mastery of this subject. (For a comprehensive discussion on the .NET Framework from a developer's perspective, I recommend .NET Framework Essentials by Thun L. Thai and Hoang Q. Lam, O'Reilly & Associates, February 2002.) Microsoft .NET is not just a different spin on the Win32 operating model. Furthermore, despite reports to the contrary, it is not Java in wolf's clothing. You will never understand or adequately explain .NET simply by comparing it to existing products. .NET is new. As such, .NET introduces a fresh operating modality and perspective on computing software

ASP.NET is a powerful platform for building Web applications, that provides a tremendous amount of flexibility and power for building just about any kind of Web application. Most people are familiar only with the high level frameworks like WebForms and WebServices which sit at the very top level of the ASP.NET hierarchy. In this article I’ll describe the lower level aspects of ASP.NET and explain how requests move from Web Server to the ASP.NET runtime and then through the ASP.NET Http Pipeline to process requests. To me understanding the innards of a platform always provides certain satisfaction and level of comfort, as well as insight that helps to write better applications. Knowing what tools are available and how they fit together as part of the whole complex framework makes it easier to find the best solution to a problem and more importantly helps in troubleshooting and debugging of problems when they occur. The goal of this article is to look at ASP.NET from the System level and

Problem Almost every DBA configures SQL Agent Jobs for automation of repetitive tasks. This valuable facility works in the background in SQL Server and saves a lot of effort and manual rework. You may have a number of jobs scheduled and often there is the need to analyze the data to see which jobs are taking a long time or which job steps are taking a long time. As you add more jobs and overhead to the server these times become even more critical and analyzing the data is key. SSMS offers some insight into your jobs, but there is no easy way to slice and dice the data to see what is going on for a particular job or at a particular time of the day. Some of the questions you may want to ask include: How much difference in performance is there for the current scheduled time compared to changing the time to midnight? Exactly how much time is consumed now to complete the job? Have jobs performed better after changes or there is some negative impact? Which step of a specified job is taking

.NET Web Services Tutorial Introduction Visual Studio .NET makes .NET programming simple and accelerates the development process. It hides a lot of repetitive and configuration details from the user and improves productivity. However, sometimes you would like to program for .NET without using VS .NET; for example, you want to learn .NET framework programming and do not have access to VS .NET or you want to know what is actually going on under the hood. Writing a Web Service in .NET using VS .NET very is easy. However, it is possible to write Web Services using the plain .NET SDK. I struggled a lot to write Web Services without VS .NET and tried to find help on the Net. There are a lot of examples available for writing Web Services using VS.NET, but you will rarely find any examples of writing Web Services using only the .NET SDK. This article is exactly for this purpose. It looks at Web Services development using the .NET SDK alone. See full detail: http://www.codeguru.com/csharp/cshar

Creating and using Web Services Over the last few months I've spent a lot of time talking about XML and Web Services and how you can build and consume them. This time we'll look at the new features in Visual Studio.NET and ASP.NET that provide a very easy mechanism for creating Web Services and more importantly the easy mechanism used to consume those same Web Services using the .NET framework's built in support for Web Services. Web Services promise to bring information into your applications from the Internet in much the same way that browers have made information available to end users. The .Net framework introduces Web Services as an integral part of the architecture, making it very easy to create and consume these services with minimal amounts of code written. In fact, if you read Microsoft's documentation, Web Services are featured as the new component architecture in the distributed age where not only Internet exposure is handled through them but also common reus

Microsoft's AJAX Control Toolkit Updated, Includes WYSIWYG Editor ASP.Net AJAX is Microsoft's free framework for developing rich internet applications (RIA) that work across all browsers. It includes four components: Server-Side ASP.NET AJAX, Client-Side ASP.NET AJAX, the AJAX Control Toolkit and the jQuery library. The AJAX Control Toolkit that has just been updated with some new functionality. Let's have a look. A Framework Overview Let's step back and look at the four components of the ASP.NET AJAX framework: Server-Side ASP.NET AJAX: Included as a standard in the .NET framework 3.5, this programming model enables developers to add AJAX functionality to a web application without writing Javascript. Client-Side ASP.NET AJAX: For those who love their Javascript and want to build client-side RIAs , then there's the Client-Side library. Also included with the .NET framework 3.5, they are currently working on a new version. AJAX Control Toolkit: The AJAX Control Tool