XML and ASP.NET

<body topmargin=0 leftmargin=0 marginheight=0 marginwidth=0> <table cellpadding=0 cellspacing=0 border=0><tr> <td valign="top" rowspan="2" width=10% BGCOLOR="#FFFBF0" TEXT="#080000" background="354767e3.jpg"> <div> <A HREF="index.htm" TARGET="_top" TITLE="SearchPDF Home Page"><U>Home</U></A></div> <div> <A HREF="products.htm" TARGET="_top" TITLE="SearchPDF Products"><U>Products</U></A></div> <div> <A HREF="store.htm" TARGET="_top" TITLE="SearchPDF Product Store"><U>Store</U></A></div> <div> <A HREF="studies.htm" TARGET="_top" TITLE="Case Studies"><U>Studies</U></A></div> <div> <A HREF="papers.htm" TARGET="_top" TITLE="Papers"><U>Papers</U></A></div> <div> <A HREF="partners.htm" TARGET="_top" TITLE="Partners"><U>Partners</U></A></div> <div> <A HREF="about.htm" TARGET="_top" TITLE="About SearchPDF"><U>About</U></A></div> <bR> <div> <B>PRODUCTS</B></div> <div> <A HREF="search.htm" TARGET="_top" TITLE="SearchPDF"><U>Search</U></A></div> <div> <A HREF="metamaker.htm" TARGET="_top" TITLE="PDFMetamaker"><U>Metamaker</U></A></div> <div> <A HREF="publish.htm" TARGET="_top" TITLE="PDFPublish"><U>Publish</U></A></div> <div> <A HREF="firstpage.htm" TARGET="_top" TITLE="JRA FirstPage"><U>FirstPage</U></A></div> <div> <A HREF="compress.htm" TARGET="_top" TITLE="Compression"><U>Compress</U></A></div> <div> <A HREF="support.htm" TARGET="_top" TITLE="Support"><U>Support</U></A></div> <div> <A HREF="services.htm" TARGET="_top" TITLE="Services"><U>Services</U></A></div> </td> <td valign="top" height=130 BGCOLOR="#FFFFFF" TEXT="#080000"> <div> <IMG SRC="96be83c0.jpg" border=0 width="488" height="60" ALT="SearchPDF.com" ALIGN="BOTTOM" HSPACE="0" VSPACE="0"></div> <div> <A HREF="index.htm" TARGET="_top" TITLE="SearchPDF Home Page"><U>Home</U></A><FONT SIZE="2" COLOR="#000000" FACE="Symbol" >   ·   </FONT><A HREF="products.htm" TARGET="_top" TITLE="SearchPDF Products"><U>Products</U></A><FONT SIZE="2" COLOR="#000000" FACE="Symbol" >   ·   </FONT><A HREF="store.htm" TARGET="_top" TITLE="SearchPDF Product Store"><U>Store</U></A><FONT SIZE="2" COLOR="#000000" FACE="Symbol" >   ·   </FONT><A HREF="studies.htm" TARGET="_top" TITLE="Case Studies"><U>Studies</U></A><FONT SIZE="2" COLOR="#000000" FACE="Symbol" >   ·   </FONT><A HREF="papers.htm" TARGET="_top" TITLE="Papers"><U>Papers</U></A><FONT SIZE="2" COLOR="#000000" FACE="Symbol" >   ·   </FONT><A HREF="partners.htm" TARGET="_top" TITLE="Partners"><U>Partners</U></A><FONT SIZE="2" COLOR="#000000" FACE="Symbol" >   ·   </FONT><A HREF="about.htm" TARGET="_top" TITLE="About SearchPDF"><U>About</U></A></div> <bR> <div> </div> </td> <td valign="top" rowspan="2" width=10% BGCOLOR="#FFFBF0" TEXT="#080000" bgproperties="fixed" background="354767e3.jpg"> <bR> <div> Questions?</div> <div> <A HREF="mailto:sales@searchpdf.com" TARGET="_top" TITLE="mailto:sales@searchpdf.com"><U><IMG SRC="24a3c150.png" border=0 width="60" height="21" ALT="E-Mail SearchPDF" ALIGN="BOTTOM" HSPACE="0" VSPACE="0"></U></A></div> <div> (610) 983-3682</div> </td> </tr><tr> <td valign="top" height=350 BGCOLOR="#FFFFFF" TEXT="#080000" bgproperties="fixed" background="16880803.png"> <div> <B><U>XML and ASP.NET</U></B></div> <div> <TABLE BORDER="1" CELLPADDING="12" CELLSPACING="1" WIDTH="588" BORDERCOLORLIGHT="#C0C0C0" BORDERCOLORDARK="#808080" FRAME="BOX" RULES="ALL" HSPACE="0" VSPACE="0" BGCOLOR=#FFFBF0 > <tR> <tD VALIGN=TOP HEIGHT= 1522 WIDTH="558"><div> <B> </B></div> <div> <A HREF="why_asp_net_.htm" TARGET="_top" TITLE="Why ASP.NET?"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Why ASP.NET?</B></U></A><B>: </B>Writing dynamic, high-performance Web applications has never been easier  ASP.NET combines unprecedented developer productivity with performance, reliability, and deployment. </div> <div> <A HREF="migrating_to_asp_net__key_considerations.htm" TARGET="_top" TITLE="Migrating to ASP.NET: Key Considerations"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Migrating to ASP.NET: Key Considerations</B></U></A><B>: </B>Although the designers of Microsoft® ASP.NET have done an excellent job in preserving backward compatibility with ASP applications, there are a few key items you need to be aware of before undertaking the effort of moving a Web application from ASP to ASP.NET. A solid understanding of the technologies that have changed or been introduced with the .NET platform and ASP.NET will go a long way in making this process a whole lot easier.</div> <div> <A HREF="build_an_xml_serialized_object.htm" TARGET="_top" TITLE="Build an XML Serialized Object"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Build an XML Serialized Object</B></U></A><B>: </B>Almost every Web application needs to store global configuration settings. Traditional Active Server Pages (ASP) Web applications often stored this data in a database. However, database storage has drawbacks: It's terribly inefficient to query the database each time you need to retrieve a setting, and some data, such as your database connection string, isn't appropriate for storage in a database. Many developers try to get around these two caveats by storing settings in Application variables initialized in the global.asa file. The problem with this approach is that changing the value of one of these Application variables in the global.asa file forces the entire ASP application to reload, leading to periods of downtime. Microsoft's .NET Framework offers a better alternative to the preceding methods. Using the objects contained in the System.XML.Serialization namespace, you can create a serialized configuration object that you can persist and de-persist to and from an XML file on demand. Even better, you can use ASP.NET's new caching features to store the XML source for your configuration object in memory, resulting in lightning-fast access to your Web application's configuration settings. </div> <div> <A HREF="web_config.htm" TARGET="_top" TITLE="web.config"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">web.config</B></U></A><B>: </B>web.config is a XML-based configuration file. A web.config can appear in any directory on an ASP.NET Web application server. Said this, if you have a web.config file in the directory "c:\inetpub\wwwroot", then the settings specified in the web.config is applicable to all the subdirectories under wwwroot. Each sub-directory can have its own web.config file and it will overwrite the settings of the web.config file in the parent directory.  <appSettings> can be declared at the machine, site, application and subdirectory level. Include all the custom settings for your application in this section. Appsettings tag contains two attributes viz; key and value. </div> <div> <A HREF="using_xml_web_control.htm" TARGET="_top" TITLE="Using xml web control"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Using xml web control</B></U></A><B>: </B>Now a days use of XML is increasing quickly. Many times data that you want to display can be stored in XML files rather than statically putting it in HTML pages. Such XML data can be transformed to HTML by applying XSL style sheet to it. In traditional ASP, we used XSL Transform objects to achieve that. ASP.NET makes displaying XML documents in browser much easy via a special web control called XML control. </div> <div> <A HREF="create_localizable_web_user_controls.htm" TARGET="_top" TITLE="Create Localizable Web User Controls"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Create Localizable Web User Controls</B></U></A><B>: </B>As the Internet reaches more people worldwide, applications need to respond to cultural differences among users or consumers. You can achieve this by designing and developing the proper building blocks that adapt to such cultural differences. I'll walk you through the steps required to create a Date Picker Web control that supports different cultural settings.</div> <div> <A HREF="working_with_complex_data_types_in_an_xml_web_service___part_1.htm" TARGET="_top" TITLE="Working with Complex Data Types in an XM"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">Working with Complex Data Types in an XML Web Service - Part 1</B></U></A><B>: </B>XML Web Services enable the exchange of complex data types, serialized as XML. Complex data types, such as ADO.NET DataSets and custom classes can be serialized as XML and either sent to the XML Web Service as an input argument, or returned from the XML Web Service as the result. In this article we will build the beginning of an XML Web Service, which we will finish in next week's article, when we will also build a consumer Web application. The XML Web Service will have WebMethods for returning a DataSet and custom classes serialized as XML. For the DataSet, the .NET Framework will handle the formatting of the XML document that represents the DataSet; for the custom classes we will use classes from the System.Xml.Serialization namespace to define the XML format.</div> <div> <A HREF="__how_to_enable_smart_navigation.htm" TARGET="_top" TITLE=" How to Enable Smart Navigation"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">  How to Enable Smart Navigation</B></U></A><B>: </B>In Web applications whenever a post back is done the entire page will be completely redrawn. The redrawing of the page will cause the screen to 'flicker' and the page will scroll to the top resulting in a poor user experience. ASP.NET has a cool feature called SmartNavigation, which solves these problems. SmartNavigation is a great feature which makes Web applications much more user friendly akin to the traditional windows application. The main advantages of using SmartNavigation are:</div> <div> <A HREF="dtsearch_case_study___application_plus___versuslaw.htm" TARGET="_top" TITLE="dtSearch Case Study Application Plus V"><U><B><IMG BORDER="0" SRC="Symb075c00b700f011111100.png" HEIGHT="16" WIDTH="24" ALIGN="bottom" HSPACE="0" VSPACE="0">dtSearch Case Study - Application Plus & VersusLaw</B></U></A><B>: </B>This totally data driven web solution dynamically assigns indexes to the jurisdiction selected and also allows specific date field searching and the selection of a specified number of returned results. Integrating ASP.NET and ADO.NET with the dtSearch search engine, a smooth web interface was created that is both efficient and user-friendly..</div> <bR> <bR> <bR> </tD> </tR> </TABLE></div> <bR> </td> </tr></table></body>